9.1.1 User
The User role can perform cryptographic operations using private keys which are encrypted
and stored in flash. The User role cannot create a user.
9.1.2 Security Officer
The Security Officer role can also perform cryptographic operations using private keys which
are encrypted and stored in flash. Additionally, the Security Officer may create a user, update
the HSM firmware, or command the HSM to "uninitialize."
9.2 Authentication
The HSM uses identity-based authentication to allow subjects to assume one of the two roles.
Usernames are transmitted to the HSM over the PCI interface to identify the user. A
corresponding personal identification number (SOPIN or UserPIN as described in section 8.0)
is input to the HSM from an iKey token over the trusted USB interface. This PIN is hashed and
compared with a hash value which is stored in flash and associated with the user's name on
the HSM. If the two hash values match, the user is authenticated and assigned a role that is
associated with the user's name. To increase security in case the iKey token is compromised,
an iKey ID is used to unlock the plaintext PIN that is stored in the iKey. This plaintext iKey ID
is input into the module in plaintext as part of the Login service. The module provides a SHA-1
of this iKey ID to the iKey token to unlock the PIN. Because the iKey ID does not authenticate
the user to the module, but rather unlocks the plaintext PIN from the iKey, the iKey ID is not
an SRDI.
9.3 Initialization
The HSM is shipped in an un-initialized state. At this point, it contains no private or secret keys.
The Security Officer initializes the board. Performing this function generates an internally
stored master key, and generates a random PIN, which is stored in the Security Officer's iKey
token. Initialization also creates the Security Officer account and associates the SHA-1 hash
of the random PIN with the Security Officer account.
9.4 User Creation
Once the board has been initialized, the Security Officer can create a User account. Creating
the User account generates a random PIN, which is stored in the User's iKey token. The SHA-1
hash of this random PIN is associated with the User account.
HSM Security Policy
228 User Guide
April 2013
Comments? infodev@avaya.com
Summary of Contents for 3050-VM
Page 1: ...User Guide Avaya VPN Gateway Release 9 0 NN46120 104 Issue 04 04 April 2013 ...
Page 4: ...4 User Guide April 2013 Comments infodev avaya com ...
Page 12: ...12 User Guide April 2013 ...
Page 20: ...New in this release 20 User Guide April 2013 Comments infodev avaya com ...
Page 30: ...Introducing the VPN Gateway 30 User Guide April 2013 Comments infodev avaya com ...
Page 36: ...Introducing the ASA 310 FIPS 36 User Guide April 2013 Comments infodev avaya com ...
Page 74: ...Upgrading the AVG Software 74 User Guide April 2013 Comments infodev avaya com ...
Page 86: ...Managing Users and Groups 86 User Guide April 2013 Comments infodev avaya com ...
Page 130: ...The Command Line Interface 130 User Guide April 2013 Comments infodev avaya com ...
Page 162: ...Supported Ciphers 162 User Guide April 2013 Comments infodev avaya com ...
Page 212: ...Syslog Messages 212 User Guide April 2013 Comments infodev avaya com ...
Page 242: ...Definition of Key Codes 242 User Guide April 2013 Comments infodev avaya com ...
Page 259: ...Creating a Port Forwarder Authenticator User Guide April 2013 259 ...
Page 266: ...Using the Port Forwarder API 266 User Guide April 2013 Comments infodev avaya com ...
Page 274: ...X 509 274 User Guide April 2013 Comments infodev avaya com ...