FIPS Operational Environment: Difference between revisions

FIPS Operational Environment (view source)

Revision as of 20:52, 15 September 2006

457 bytes added , 15 September 2006

→‎Auditable Events

Wtchang

canmove, Confirmed users

937

edits

@@ Line 174: / Line 174: @@
 The following events are auditable by the NSS cryptographic module.
-* attempts to provide invalid input for crypto officer functions
+* attempts to provide invalid input for crypto officer functions: We log the use of all crypto officer functions with the return code. The return code tells us whether the operator attempted to provide invalid input.
 ** <code>FC_InitToken(slotID, pPin, ulPinLen, pLabel)</code>
 *** If <code>slotID</code> is invalid, the return code <code>0x00000003 (CKR_SLOT_ID_INVALID)</code> is logged.
 *** The other input arguments are ignored. (The password of the Crypto Officer is not used because the module depends on the OS to authenticate the Crypto Officer and doesn't perform further authentication.)
 ** <code>FC_InitPIN(hSession, pPin, ulPinLen)</code>
-** We log the use of all crypto officer functions (see below) with the return code. The return code tells us whether the operator attempted to provide invalid input.
+*** If <code>hSession</code> is invalid, the return code <code>0x000000B3 (CKR_SESSION_HANDLE_INVALID)</code> is logged.
+*** If the password that <code>pPin</code> points to is not a valid UTF-8 string, the return code <code>0x000000A1 (CKR_PIN_INVALID)</code> is logged.
+*** If the password that <code>pPin</code> points to is too short, too long, or too weak (doesn't have enough character types), the return code <code>0x000000A2 (CKR_PIN_LEN_RANGE)</code> is logged.
 * the addition or deletion of an operator to/from a crypto officer role
 ** N/A. Any authorized operator can assume the crypto officer role.