Device Class 3: Identification And Authentication (organizational Users)

Organizational users include employees or individuals that organizations deem to have equivalent status of employees (e.g.,contractors, guest researchers). This control applies to all accesses other than: (i) accesses that are explicitly identified and documented in AC-14; and (ii) accesses that occur through authorized use of group authenticators without individual authentication. Organizations may require unique identification of individuals in group accounts (e.g., shared privilege accounts) or for detailed accountability of individual activity. Organizations employ passwords, tokens, or biometrics to authenticate user identities, or in the case multifactor authentication, or some combination thereof. Access to organizational information systems is defined as either local access or network access. Local access is any access to organizational information systems by users (or processes acting on behalf of users) where such access is obtained by direct connections without the use of networks. Network access is access to organizational information systems by users (or processes acting on behalf of users) where such access is obtained through network connections (i.e., nonlocal accesses). Remote access is a type of network access that involves communication through external networks (e.g., the Internet). Internal networks include local area networks and wide area networks. In addition, the use of encrypted virtual private networks (VPNs) for network connections between organization-controlled endpoints and non-organization controlled endpoints may be treated as internal networks from the perspective of protecting the confidentiality and integrity of information traversing the network.

Organizations can satisfy the identification and authentication requirements in this control by complying with the requirements in Homeland Security Presidential Directive 12 consistent with the specific organizational implementation plans. Multifactor authentication requires the use of two or more different factors to achieve authentication. The factors are defined as: (i) something you know (e.g., password, personal identification number [PIN]); (ii) something you have (e.g., cryptographic identification device, token); or (iii) something you are (e.g., biometric). Multifactor solutions that require devices separate from information systems gaining access include, for example, hardware tokens providing time-based or challenge-response authenticators and smart cards such as the U.S. Government Personal Identity Verification card and the DoD common access card. In addition to identifying and authenticating users at the information system level (i.e., at logon), organizations also employ identification and authentication mechanisms at the application level, when necessary, to provide increased information security. Identification and authentication requirements for other than organizational users are described in IA-8.

• Device shall require multi-factor authentication for the system management actions defined in Notes on Access Control:
• Install software other than signed software whose signature chains to a verification key whose integrity is protected by hardware on the device.
• Modify the access control policy specified in AC-3.
• Modify the information flow control policy specified in AC-4.
• Define what types of failed authentication attempts are logged for future action as specified in AC-7.
• The list of auditable activities and the audit log specified in AU-2.
• Deletion of audit log data as specified in AU-9, except in the case where the audit log has exceeded the allotted storage space.
• Add or remove root certificates except when this is done via a signed instruction whose signature chains to a verification key whose integrity is protected by hardware on the device.
• Device may require multi-factor authentication for other actions.
• Passwords used in multi-factor authentication shall meet the requirements specified in IA-5 enhancement 1 , authenticator management | password-based authentication.
• Device shall require multi-factor authentication for the system management actions defined in Notes on Access Control. See NETWORK ACCESS TO PRIVILEGED ACCOUNTS.
• Device may require multi-factor authentication for other locally-accessed actions.
• Network access to privileged accounts shall be over SSH, which provides replay resistance.NOTE: SSH shall use RSA keys of length 2048 bits or longer or ECC keys of length 256 bits or longer.
• Device may accept PIV credentials as specified in FIPS 201 and supporting guidance documents .
• The information system implements replay-resistant authentication mechanisms for network access to non-privileged accounts.