Identification and Authentication: SP 800-171 Security Family 3.5

Identification and Authentication: SP 800-171 Security Family 3.5

 For most systems, identification and authentication is often the first line of defense. Identification is the means of verifying the identity of a user, process, or device, typically as a prerequisite for granting access to resources in a system. Identification and authentication is a technical measure that prevents unauthorized individuals or processes from entering a system. Identification and authentication is a critical building block of information security since it is the basis for most types of access control and for establishing user accountability. Access control often requires that the system can identify and differentiate between users. For example, access control is often based on least privilege, which refers to granting users only those accesses required to perform their duties. User accountability requires linking activities on a system to specific individuals and, therefore, requires the system to identify users. Systems recognize individuals based on the authentication data the systems receive. Authentication presents several challenges: collecting authentication data, transmitting the data securely, and knowing whether the individual who was originally authenticated is still the individual using the system. For example, a user may walk away from a terminal while still logged on, and another person may start using it. There are four means of authenticating a user’s identity that can be used alone or in combination.

User identity can be authenticated based on:
      •something you know – e.g., a password or Personal Identification Number (PIN),
      •something you possess (a token) – e.g., a n ATM card or a smart card,
      •something you are (static biometric) – e.g., fingerprint, retina, face, ear, DNA, and/or
      •something you do (dynamic biometrics) – e.g., voice pattern, handwriting, typing rhythm.

While it may appear that any of these individual methods could provide strong authentication, there are problems associated with each. If an individual wanted to impersonate someone else on a system, they could guess or learn another user’s password, or steal or fabricate tokens. Each method also has drawbacks for legitimate users and system administrators: users forget passwords and may lose tokens, and administrative overhead for keeping track of identification and authorization data and tokens can be substantial. Biometric systems have significant technical, user acceptance, and cost problems as well. Examples of identification and authentication requirements include: device identification and authentication, identifier management, authenticator management, authenticator feedback, and re-authentication. Companies should identify system users, processes acting on behalf of users, or devices and authenticate or verify the identities of those users, processes, or devices, as a prerequisite to allowing access to company systems. 
    • Related Articles

    • Security Assessment: SP 800-171 Security Family 3.12

      A security requirement assessment is the testing and/or evaluation of the management, operational, and technical security requirements on a system to determine the extent to which the requirements are implemented correctly, operating as intended, and ...
    • Personnel Security: SP 800-171 Security Family 3.9

      Users play a vital role in protecting a system as many important issues in information security involve users, designers, implementers, and managers. How these individuals interact with the system and the level of access they need to do their jobs ...
    • CMMC IA.3.083 - Use Multifactor Authentication

      Requirement text: IA.3.083: Use multifactor authentication for local and network access to privileged accounts and for network access to non-privileged accounts. DISCUSSION FROM SOURCE: DRAFT NIST SP 800-171 R2 Multifactor authentication requires the ...
    • CMMC IA.3.084 - Employ Replay-Resistant Authentication

      Requirement text: IA.3.084: Employ replay-resistant authentication mechanisms for network access to privileged and non-privileged accounts. DISCUSSION FROM SOURCE: DRAFT NIST SP 800-171 R2 Authentication processes resist replay attacks if it is ...
    • CMMC Level 1 Overview - Basic Cyber Hygiene

      CMMC Level 1 l focuses on Federal Contract Information (FCI), which is defined as “information, not intended for public release, that is provided by or generated for the Government under a contract to develop or deliver a product or service to the ...