IA-05 Authenticator Management
Identification and Authentication
Description
Manage system authenticators by: a. Verifying, as part of the initial authenticator distribution, the identity of the individual, group, role, service, or device receiving the authenticator; b. Establishing initial authenticator content for any authenticators issued by the organization; c. Ensuring that authenticators have sufficient strength of mechanism for their intended use; d. Establishing and implementing administrative procedures for initial authenticator distribution, for lost or compromised or damaged authenticators, and for revoking authenticators; e. Changing default authenticators prior to first use; f. Changing or refreshing authenticators [Assignment: organization-defined time period by authenticator type] or when [Assignment: organization-defined events] occur; g. Protecting authenticator content from unauthorized disclosure and modification; h. Requiring individuals to take, and having devices implement, specific controls to protect authenticators; and i. Changing authenticators for group or role accounts when membership to those accounts changes.
Supplemental Guidance
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-04 or PS-06 for authenticators in the possession of individuals and by controls AC-03, AC-06, and 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.
Changes from Rev 4
Removes requirement to change default content of authenticators prior to information system installation New parameter requires specifying events that require changing or refreshing authenticators Changes 'security safeguards' to 'controls' Discussion includes new examples
Enhancements (15)
What NIST adds to this control. Select one to read its statement.
IA-05(01) Password-based Authentication LowModerateHigh
For password-based authentication: a. Maintain a list of commonly-used, expected, or compromised passwords and update the list [Assignment: organization-defined frequency] and when organizational passwords are suspected to have been compromised directly or indirectly; b. 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); c. Transmit passwords only over cryptographically-protected channels; d. Store passwords using an approved salted key derivation function, preferably using a keyed hash; e. Require immediate selection of a new password upon account recovery; f. Allow user selection of long passwords and passphrases, including spaces and all printable characters; g. Employ automated tools to assist the user in selecting strong password authenticators; and h. Enforce the following composition and complexity rules: [Assignment: organization-defined composition and complexity rules].
IA-05(02) Public Key-based Authentication ModerateHigh
a. For public key-based authentication: 1. Enforce authorized access to the corresponding private key; and 2. Map the authenticated identity to the account of the individual or group; and b. When public key infrastructure (PKI) is used: 1. Validate certificates by constructing and verifying a certification path to an accepted trust anchor, including checking certificate status information; and 2. Implement a local cache of revocation data to support path discovery and validation.
IA-05(05) Change Authenticators Prior to Delivery
Require developers and installers of system components to provide unique authenticators or change default authenticators prior to delivery and installation.
IA-05(06) Protection of Authenticators ModerateHigh
Protect authenticators commensurate with the security category of the information to which use of the authenticator permits access.
IA-05(07) No Embedded Unencrypted Static Authenticators
Ensure that unencrypted static authenticators are not embedded in applications or other forms of static storage.
IA-05(08) Multiple System Accounts
Implement [Assignment: organization-defined security controls] to manage the risk of compromise due to individuals having accounts on multiple systems.
IA-05(09) Federated Credential Management
Use the following external organizations to federate credentials: [Assignment: organization-defined external organizations].
IA-05(10) Dynamic Credential Binding
Bind identities and authenticators dynamically using the following rules: [Assignment: organization-defined binding rules].
IA-05(12) Biometric Authentication Performance
For biometric-based authentication, employ mechanisms that satisfy the following biometric quality requirements [Assignment: organization-defined biometric quality requirements].
IA-05(13) Expiration of Cached Authenticators
Prohibit the use of cached authenticators after [Assignment: organization-defined time period].
IA-05(14) Managing Content of PKI Trust Stores
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.
IA-05(15) GSA-approved Products and Services
Use only General Services Administration-approved products and services for identity, credential, and access management.
IA-05(16) In-person or Trusted External Party Authenticator Issuance
Require that the issuance of [Assignment: organization-defined types of and/or specific authenticators] be conducted [Selection (one): in person; by a trusted external party] before [Assignment: organization-defined registration authority] with authorization by [Assignment: organization-defined personnel or roles].
IA-05(17) Presentation Attack Detection for Biometric Authenticators
Employ presentation attack detection mechanisms for biometric-based authentication.
IA-05(18) Password Managers
a. Employ [Assignment: organization-defined password managers] to generate and manage passwords; and b. Protect the passwords using [Assignment: organization-defined controls].
Patterns that use this control (20)
Grouped by the emphasis each pattern gives it.
Critical (9)
- SP-022 Board of Directors Room
- SP-028 Secure DevOps Pipeline Pattern
- SP-029 Zero Trust Architecture
- SP-030 API Security
- SP-032 Modern Authentication
- SP-033 Passkey Authentication
- SP-037 Privileged User Management
- SP-052 Decentralised Identity & Verifiable Credentials (draft)
- SP-054 CBDC and Digital Currency Infrastructure (draft)
Important (9)
- SP-011 Cloud Computing Pattern
- SP-012 Secure Software Development Lifecycle
- SP-015 Secure Remote Working
- SP-027 Secure LLM Usage
- SP-034 Cyber Resilience
- SP-040 Post-Quantum Cryptography and Quantum Readiness
- SP-044 SaaS Identity Lifecycle Management
- SP-047 Secure Agentic AI Frameworks
- SP-050 Mobile Security Architecture (draft)
MITRE ATT&CK Techniques (72)
ATT&CK v16.1Techniques mitigated by this control, mapped via CTID.