+IA-05 Authenticator Management
---+IA-05(01) Password-based Authentication
---+IA-05(02) Public Key-based Authentication
---+IA-05(05) Change Authenticators Prior to Delivery
---+IA-05(06) Protection of Authenticators
---+IA-05(07) No Embedded Unencrypted Static Authenticators
---+IA-05(08) Multiple System Accounts
---+IA-05(09) Federated Credential Management
---+IA-05(10) Dynamic Credential Binding
---+IA-05(12) Biometric Authentication Performance
---+IA-05(13) Expiration of Cached Authenticators
---+IA-05(14) Managing Content of PKI Trust Stores
---+IA-05(15) GSA-approved Products and Services
---+IA-05(16) In-person or Trusted External Party Authenticator Issuance
---+IA-05(17) Presentation Attack Detection for Biometric Authenticators
---+IA-05(18) Password Managers
|
IA-05 Authenticator Management
Control
Manage system authenticators by:- Verifying, as part of the initial authenticator distribution, the identity of the individual, group, role, service, or device receiving the authenticator;
- Establishing initial authenticator content for any authenticators issued by the organization;
- Ensuring that authenticators have sufficient strength of mechanism for their intended use;
- Establishing and implementing administrative procedures for initial authenticator distribution, for lost or compromised or damaged authenticators, and for revoking authenticators;
- Changing default authenticators prior to first use;
- Changing or refreshing authenticators [Assignement: time period by authenticator type] or when [Assignement: events] occur;
- Protecting authenticator content from unauthorized disclosure and modification;
- Requiring individuals to take, and having devices implement, specific controls to protect authenticators; and
- Changing authenticators for group or role accounts when membership to those accounts changes.
Discussion
Authenticators include passwords, cryptographic devices, biometrics, certificates, one-time password devices, and ID badges. Device authenticators include certificates and passwords. Initial authenticator content is the actual content of the authenticator (e.g., the initial password). In contrast, the requirements for authenticator content contain specific criteria or characteristics (e.g., minimum password length). Developers may deliver system components with factory default authentication credentials (i.e., passwords) to allow for initial installation and configuration. Default authentication credentials are often well known, easily discoverable, and present a significant risk. The requirement to protect individual authenticators may be implemented via control [PL-4](#pl-4) or [PS-6](#ps-6) for authenticators in the possession of individuals and by controls [AC-3](#ac-3), [AC-6](#ac-6) , and [SC-28](#sc-28) for authenticators stored in organizational systems, including passwords stored in hashed or encrypted formats or files containing encrypted or hashed passwords accessible with administrator privileges.
Systems support authenticator management by organization-defined settings and restrictions for various authenticator characteristics (e.g., minimum password length, validation time window for time synchronous one-time tokens, and number of allowed rejections during the verification stage of biometric authentication). Actions can be taken to safeguard individual authenticators, including maintaining possession of authenticators, not sharing authenticators with others, and immediately reporting lost, stolen, or compromised authenticators. Authenticator management includes issuing and revoking authenticators for temporary access when no longer needed.
Assessment Objective
- system authenticators are managed through the verification of the identity of the individual, group, role, service, or device receiving the authenticator as part of the initial authenticator distribution;
- system authenticators are managed through the establishment of initial authenticator content for any authenticators issued by the organization;
- system authenticators are managed to ensure that authenticators have sufficient strength of mechanism for their intended use;
- system authenticators are managed through the establishment and implementation of administrative procedures for initial authenticator distribution; lost, compromised, or damaged authenticators; and the revocation of authenticators;
- system authenticators are managed through the change of default authenticators prior to first use;
- system authenticators are managed through the change or refreshment of authenticators [Assignement: time period by authenticator type] or when [Assignement: events] occur;
- system authenticators are managed through the protection of authenticator content from unauthorized disclosure and modification;
- system authenticators are managed through the requirement for individuals to take specific controls to protect authenticators;
- system authenticators are managed through the requirement for devices to implement specific controls to protect authenticators;
- system authenticators are managed through the change of authenticators for group or role accounts when membership to those accounts changes.
Assessment Method
Examine
Identification and authentication policy
system security plan
addressing authenticator management
system design documentation
system configuration settings and associated documentation
list of system authenticator types
change control records associated with managing system authenticators
system audit records
other relevant documents or records
Interview
Organizational personnel with authenticator management responsibilities
organizational personnel with information security responsibilities
system/network administrators
1. Oversigt
| Titel |
Standard |
|
IA-05(01) Password-based Authentication
|
Control
For password-based authentication:- Maintain a list of commonly-used, expected, or compromised passwords and update the list [Assignement: frequency] and when organizational passwords are suspected to have been compromised directly or indirectly;
- Verify, when users create or update passwords, that the passwords are not found on the list of commonly-used, expected, or compromised passwords in IA-5(1)(a);
- Transmit passwords only over cryptographically-protected channels;
- Store passwords using an approved salted key derivation function, preferably using a keyed hash;
- Require immediate selection of a new password upon account recovery;
- Allow user selection of long passwords and passphrases, including spaces and all printable characters;
- Employ automated tools to assist the user in selecting strong password authenticators; and
- Enforce the following composition and complexity rules: [Assignement: composition and complexity rules].
Discussion
Password-based authentication applies to passwords regardless of whether they are used in single-factor or multi-factor authentication. Long passwords or passphrases are preferable over shorter passwords. Enforced composition rules provide marginal security benefits while decreasing usability. However, organizations may choose to establish certain rules for password generation (e.g., minimum character length for long passwords) under certain circumstances and can enforce this requirement in IA-5(1)(h). Account recovery can occur, for example, in situations when a password is forgotten. Cryptographically protected passwords include salted one-way cryptographic hashes of passwords. The list of commonly used, compromised, or expected passwords includes passwords obtained from previous breach corpuses, dictionary words, and repetitive or sequential characters. The list includes context-specific words, such as the name of the service, username, and derivatives thereof.
Assessment Objective
- for password-based authentication, a list of commonly used, expected, or compromised passwords is maintained and updated [Assignement: frequency] and when organizational passwords are suspected to have been compromised directly or indirectly;
- for password-based authentication when passwords are created or updated by users, the passwords are verified not to be found on the list of commonly used, expected, or compromised passwords in IA-05(01)(a);
- for password-based authentication, passwords are only transmitted over cryptographically protected channels;
- for password-based authentication, passwords are stored using an approved salted key derivation function, preferably using a keyed hash;
- for password-based authentication, immediate selection of a new password is required upon account recovery;
- for password-based authentication, user selection of long passwords and passphrases is allowed, including spaces and all printable characters;
- for password-based authentication, automated tools are employed to assist the user in selecting strong password authenticators;
- for password-based authentication, [Assignement: composition and complexity rules] are enforced.
Assessment Method
Examine
Identification and authentication policy
password policy
procedures addressing authenticator management
system security plan
system design documentation
system configuration settings and associated documentation
password configurations and associated documentation
other relevant documents or records
Interview
Organizational personnel with authenticator management responsibilities
organizational personnel with information security responsibilities
system/network administrators
system developers
|
|
IA-05(02) Public Key-based Authentication
|
Control
- For public key-based authentication:
- Enforce authorized access to the corresponding private key; and
- Map the authenticated identity to the account of the individual or group; and
- When public key infrastructure (PKI) is used:
- Validate certificates by constructing and verifying a certification path to an accepted trust anchor, including checking certificate status information; and
- Implement a local cache of revocation data to support path discovery and validation.
Discussion
Public key cryptography is a valid authentication mechanism for individuals, machines, and devices. For PKI solutions, status information for certification paths includes certificate revocation lists or certificate status protocol responses. For PIV cards, certificate validation involves the construction and verification of a certification path to the Common Policy Root trust anchor, which includes certificate policy processing. Implementing a local cache of revocation data to support path discovery and validation also supports system availability in situations where organizations are unable to access revocation information via the network.
Assessment Objective
- authorized access to the corresponding private key is enforced for public key-based authentication;
- the authenticated identity is mapped to the account of the individual or group for public key-based authentication;
- when public key infrastructure (PKI) is used, certificates are validated by constructing and verifying a certification path to an accepted trust anchor, including checking certificate status information;
- when public key infrastructure (PKI) is used, a local cache of revocation data is implemented to support path discovery and validation.
Assessment Method
Examine
Identification and authentication policy
procedures addressing authenticator management
system security plan
system design documentation
system configuration settings and associated documentation
PKI certification validation records
PKI certification revocation lists
other relevant documents or records
Interview
Organizational personnel with PKI-based, authenticator management responsibilities
organizational personnel with information security responsibilities
system/network administrators
system developers
|
|
IA-05(05) Change Authenticators Prior to Delivery
|
Control
Require developers and installers of system components to provide unique authenticators or change default authenticators prior to delivery and installation.
Discussion
Changing authenticators prior to the delivery and installation of system components extends the requirement for organizations to change default authenticators upon system installation by requiring developers and/or installers to provide unique authenticators or change default authenticators for system components prior to delivery and/or installation. However, it typically does not apply to developers of commercial off-the-shelf information technology products. Requirements for unique authenticators can be included in acquisition documents prepared by organizations when procuring systems or system components.
Assessment Objective
developers and installers of system components are required to provide unique authenticators or change default authenticators prior to delivery and installation.
Assessment Method
Examine
Identification and authentication policy
system security plan
system and services acquisition policy
procedures addressing authenticator management
procedures addressing the integration of security requirements into the acquisition process
acquisition documentation
acquisition contracts for system procurements or services
other relevant documents or records
Interview
Organizational personnel with authenticator management responsibilities
organizational personnel with information security, acquisition, and contracting responsibilities
system developers
|
|
IA-05(06) Protection of Authenticators
|
Control
Protect authenticators commensurate with the security category of the information to which use of the authenticator permits access.
Discussion
For systems that contain multiple security categories of information without reliable physical or logical separation between categories, authenticators used to grant access to the systems are protected commensurate with the highest security category of information on the systems. Security categories of information are determined as part of the security categorization process.
Assessment Objective
authenticators are protected commensurate with the security category of the information to which use of the authenticator permits access.
Assessment Method
Examine
Identification and authentication policy
procedures addressing authenticator management
security categorization documentation for the system
security assessments of authenticator protections
risk assessment results
system security plan
other relevant documents or records
Interview
Organizational personnel with authenticator management responsibilities
organizational personnel implementing and/or maintaining authenticator protections
organizational personnel with information security responsibilities
system/network administrators
|
|
IA-05(07) No Embedded Unencrypted Static Authenticators
|
Control
Ensure that unencrypted static authenticators are not embedded in applications or other forms of static storage.
Discussion
In addition to applications, other forms of static storage include access scripts and function keys. Organizations exercise caution when determining whether embedded or stored authenticators are in encrypted or unencrypted form. If authenticators are used in the manner stored, then those representations are considered unencrypted authenticators.
Assessment Objective
unencrypted static authenticators are not embedded in applications or other forms of static storage.
Assessment Method
Examine
Identification and authentication policy
system security plan
procedures addressing authenticator management
system design documentation
system configuration settings and associated documentation
logical access scripts
application code reviews for detecting unencrypted static authenticators
other relevant documents or records
Interview
Organizational personnel with authenticator management responsibilities
organizational personnel with information security responsibilities
system/network administrators
system developers
|
|
IA-05(08) Multiple System Accounts
|
Control
Implement [Assignement: security controls] to manage the risk of compromise due to individuals having accounts on multiple systems.
Discussion
When individuals have accounts on multiple systems and use the same authenticators such as passwords, there is the risk that a compromise of one account may lead to the compromise of other accounts. Alternative approaches include having different authenticators (passwords) on all systems, employing a single sign-on or federation mechanism, or using some form of one-time passwords on all systems. Organizations can also use rules of behavior (see [PL-4](#pl-4) ) and access agreements (see [PS-6](#ps-6) ) to mitigate the risk of multiple system accounts.
Assessment Objective
[Assignement: security controls] are implemented to manage the risk of compromise due to individuals having accounts on multiple systems.
Assessment Method
Examine
Identification and authentication policy
procedures addressing authenticator management
system security plan
list of individuals having accounts on multiple systems
list of security safeguards intended to manage risk of compromise due to individuals having accounts on multiple systems
other relevant documents or records
Interview
Organizational personnel with authenticator management responsibilities
organizational personnel with information security responsibilities
system/network administrators
|
|
IA-05(09) Federated Credential Management
|
Control
Use the following external organizations to federate credentials: [Assignement: external organizations].
Discussion
Federation provides organizations with the capability to authenticate individuals and devices when conducting cross-organization activities involving the processing, storage, or transmission of information. Using a specific list of approved external organizations for authentication helps to ensure that those organizations are vetted and trusted.
Assessment Objective
[Assignement: external organizations] are used to federate credentials.
Assessment Method
Examine
Identification and authentication policy
procedures addressing authenticator management
procedures addressing account management
system security plan
security agreements
other relevant documents or records
Interview
Organizational personnel with authenticator management responsibilities
organizational personnel with information security responsibilities
system/network administrators
|
|
IA-05(10) Dynamic Credential Binding
|
Control
Bind identities and authenticators dynamically using the following rules: [Assignement: binding rules].
Discussion
Authentication requires some form of binding between an identity and the authenticator that is used to confirm the identity. In conventional approaches, binding is established by pre-provisioning both the identity and the authenticator to the system. For example, the binding between a username (i.e., identity) and a password (i.e., authenticator) is accomplished by provisioning the identity and authenticator as a pair in the system. New authentication techniques allow the binding between the identity and the authenticator to be implemented external to a system. For example, with smartcard credentials, the identity and authenticator are bound together on the smartcard. Using these credentials, systems can authenticate identities that have not been pre-provisioned, dynamically provisioning the identity after authentication. In these situations, organizations can anticipate the dynamic provisioning of identities. Pre-established trust relationships and mechanisms with appropriate authorities to validate identities and related credentials are essential.
Assessment Objective
identities and authenticators are dynamically bound using [Assignement: binding rules].
Assessment Method
Examine
Identification and authentication policy
procedures addressing identifier management
system security plan
system design documentation
automated mechanisms providing dynamic binding of identifiers and authenticators
system configuration settings and associated documentation
system audit records
other relevant documents or records
Interview
Organizational personnel with identifier management responsibilities
organizational personnel with information security responsibilities
system/network administrators
|
|
IA-05(12) Biometric Authentication Performance
|
Control
For biometric-based authentication, employ mechanisms that satisfy the following biometric quality requirements [Assignement: biometric quality requirements].
Discussion
Unlike password-based authentication, which provides exact matches of user-input passwords to stored passwords, biometric authentication does not provide exact matches. Depending on the type of biometric and the type of collection mechanism, there is likely to be some divergence from the presented biometric and the stored biometric that serves as the basis for comparison. Matching performance is the rate at which a biometric algorithm correctly results in a match for a genuine user and rejects other users. Biometric performance requirements include the match rate, which reflects the accuracy of the biometric matching algorithm used by a system.
Assessment Objective
mechanisms that satisfy [Assignement: biometric quality requirements] are employed for biometric-based authentication.
Assessment Method
Examine
Identification and authentication policy
procedures addressing authenticator management
system security plan
system design documentation
mechanisms employing biometric-based authentication for the system
list of biometric quality requirements
system configuration settings and associated documentation
system audit records
other relevant documents or records
Interview
Organizational personnel with authenticator management responsibilities
organizational personnel with information security responsibilities
system/network administrators
system developers
|
|
IA-05(13) Expiration of Cached Authenticators
|
Control
Prohibit the use of cached authenticators after [Assignement: time period].
Discussion
Cached authenticators are used to authenticate to the local machine when the network is not available. If cached authentication information is out of date, the validity of the authentication information may be questionable.
Assessment Objective
the use of cached authenticators is prohibited after [Assignement: time period].
Assessment Method
Examine
Identification and authentication policy
procedures addressing authenticator management
system security plan
system design documentation
system configuration settings and associated documentation
system audit records
other relevant documents or records
Interview
Organizational personnel with authenticator management responsibilities
organizational personnel with information security responsibilities
system/network administrators
system developers
|
|
IA-05(14) Managing Content of PKI Trust Stores
|
Control
For PKI-based authentication, employ an organization-wide methodology for managing the content of PKI trust stores installed across all platforms, including networks, operating systems, browsers, and applications.
Discussion
An organization-wide methodology for managing the content of PKI trust stores helps improve the accuracy and currency of PKI-based authentication credentials across the organization.
Assessment Objective
an organization-wide methodology for managing the content of PKI trust stores is employed across all platforms, including networks, operating systems, browsers, and applications for PKI-based authentication.
Assessment Method
Examine
Identification and authentication policy
procedures addressing authenticator management
system security plan
organizational methodology for managing content of PKI trust stores across installed all platforms
system design documentation
system configuration settings and associated documentation
enterprise security architecture documentation
enterprise architecture documentation
other relevant documents or records
Interview
Organizational personnel with authenticator management responsibilities
organizational personnel with information security responsibilities
system/network administrators
system developers
|
|
IA-05(15) GSA-approved Products and Services
|
Control
Use only General Services Administration-approved products and services for identity, credential, and access management.
Discussion
General Services Administration (GSA)-approved products and services are products and services that have been approved through the GSA conformance program, where applicable, and posted to the GSA Approved Products List. GSA provides guidance for teams to design and build functional and secure systems that comply with Federal Identity, Credential, and Access Management (FICAM) policies, technologies, and implementation patterns.
Assessment Objective
only General Services Administration-approved products and services are used for identity, credential, and access management.
Assessment Method
Examine
Identification and authentication policy
procedures addressing identifier management
system security plan
system design documentation
mechanisms providing dynamic binding of identifiers and authenticators
system configuration settings and associated documentation
system audit records
other relevant documents or records
Interview
Organizational personnel with identification and authentication management responsibilities
organizational personnel with information security responsibilities
system/network administrators
|
|
IA-05(16) In-person or Trusted External Party Authenticator Issuance
|
Control
Require that the issuance of [Assignement: types of and/or specific authenticators] be conducted [Selection: in person; by a trusted external party] before [Assignement: registration authority] with authorization by [Assignement: personnel or roles].
Discussion
Issuing authenticators in person or by a trusted external party enhances and reinforces the trustworthiness of the identity proofing process.
Assessment Objective
the issuance of [Assignement: types of and/or specific authenticators] is required to be conducted [Selection: in person; by a trusted external party] before [Assignement: registration authority] with authorization by [Assignement: personnel or roles].
Assessment Method
Examine
Identification and authentication policy
procedures addressing identifier management
system security plan
system design documentation
mechanisms providing dynamic binding of identifiers and authenticators
system configuration settings and associated documentation
system audit records
other relevant documents or records
Interview
Organizational personnel with identification and authentication management responsibilities
organizational personnel with information security responsibilities
system/network administrators
|
|
IA-05(17) Presentation Attack Detection for Biometric Authenticators
|
Control
Employ presentation attack detection mechanisms for biometric-based authentication.
Discussion
Biometric characteristics do not constitute secrets. Such characteristics can be obtained by online web accesses, taking a picture of someone with a camera phone to obtain facial images with or without their knowledge, lifting from objects that someone has touched (e.g., a latent fingerprint), or capturing a high-resolution image (e.g., an iris pattern). Presentation attack detection technologies including liveness detection, can mitigate the risk of these types of attacks by making it difficult to produce artifacts intended to defeat the biometric sensor.
Assessment Objective
presentation attack detection mechanisms are employed for biometric-based authentication.
Assessment Method
Examine
Identification and authentication policy
procedures addressing identifier management
system security plan
system design documentation
mechanisms providing dynamic binding of identifiers and authenticators
system configuration settings and associated documentation
system audit records
other relevant documents or records
Interview
Organizational personnel with identification and authentication management responsibilities
organizational personnel with information security responsibilities
system/network administrators
|
|
IA-05(18) Password Managers
|
Control
- Employ [Assignement: password managers] to generate and manage passwords; and
- Protect the passwords using [Assignement: controls].
Discussion
For systems where static passwords are employed, it is often a challenge to ensure that the passwords are suitably complex and that the same passwords are not employed on multiple systems. A password manager is a solution to this problem as it automatically generates and stores strong and different passwords for various accounts. A potential risk of using password managers is that adversaries can target the collection of passwords generated by the password manager. Therefore, the collection of passwords requires protection including encrypting the passwords (see [IA-5(1)(d)](#ia-5.1_smt.d) ) and storing the collection offline in a token.
Assessment Objective
- [Assignement: password managers] are employed to generate and manage passwords;
- the passwords are protected using [Assignement: controls].
Assessment Method
Examine
Identification and authentication policy
procedures addressing identifier management
system security plan
system design documentation
mechanisms providing dynamic binding of identifiers and authenticators
system configuration settings and associated documentation
system audit records
other relevant documents or records
Interview
Organizational personnel with identification and authentication management responsibilities
organizational personnel with information security responsibilities
system/network administrators
|
1.1 Referencer
1.2 Identificerede krav
1.3 Relaterede reguleringer
2. Identificerede krav
3. Relaterede reguleringer
Reguleringer
| Kilde |
Regulering |
Linkede sager
|