3.5.3—Identification and Authentication - Derived
>Control Description
>Discussion
Multifactor authentication requires the use of two or more different factors to authenticate. The factors are defined as something you know (e.g., password, personal identification number [PIN]); something you have (e.g., cryptographic identification device, token); or something you are (e.g., biometric). Multifactor authentication solutions that feature physical authenticators include hardware authenticators providing time-based or challenge-response authenticators and smart cards.
In addition to authenticating users at the system level (i.e., at logon), organizations may also employ authentication mechanisms at the application level, when necessary, to provide increased information security. Access to organizational systems is defined as local access or network access. Local access is any access to organizational 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 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. The use of encrypted virtual private networks for connections between organization-controlled and non-organization controlled endpoints may be treated as internal networks with regard to protecting the confidentiality of information. [SP 800-63-3] provides guidance on digital identities. [24] Multifactor authentication requires two or more different factors to achieve authentication.
The factors include: something you know (e.g., password/PIN); something you have (e.g., cryptographic identification device, token); or something you are (e.g., biometric). The requirement for multifactor authentication should not be interpreted as requiring federal Personal Identity Verification (PIV) card or Department of Defense Common Access Card (CAC)-like solutions. A variety of multifactor solutions (including those with replay resistance) using tokens and biometrics are commercially available.
Such solutions may employ hard tokens (e.g., smartcards, key fobs, or dongles) or soft tokens to store user credentials. [25] Local access is any access to a system by a user (or process acting on behalf of a user) communicating through a direct connection without the use of a network. Network access is any access to a system by a user (or a process acting on behalf of a user) communicating through a network (e.g., local area network, wide area network, Internet).
>Cross-Framework Mappings
>Assessment Interview Topics
Questions assessors commonly ask
Process & Governance:
- •What documented policies and procedures address identification and authentication - derived for CUI systems?
- •Who is accountable for implementing and maintaining identification and authentication - derived controls?
- •How frequently are identification and authentication - derived requirements reviewed, and what triggers updates?
- •What process ensures changes to systems maintain compliance with identification and authentication - derived requirements?
- •How are exceptions to identification and authentication - derived requirements documented and approved?
Technical Implementation:
- •What technical controls enforce identification and authentication - derived in your CUI environment?
- •How are identification and authentication - derived controls configured and maintained across all CUI systems?
- •What automated mechanisms support identification and authentication - derived compliance?
- •How do you validate that identification and authentication - derived implementations achieve their intended security outcome?
- •What compensating controls exist if primary identification and authentication - derived controls cannot be fully implemented?
Evidence & Documentation:
- •What documentation proves identification and authentication - derived is implemented and operating effectively?
- •Can you provide configuration evidence showing how identification and authentication - derived is technically enforced?
- •What audit logs or monitoring data demonstrate ongoing identification and authentication - derived compliance?
- •Can you show evidence of a recent review or assessment of identification and authentication - derived controls?
- •What artifacts would you provide to a CMMC assessor to demonstrate identification and authentication - derived compliance?
Ask AI
Configure your API key to use AI features.