Knowledge is Power
BARE METAL CYBERKnowledge is Power

Sitewide Search

Search Bare Metal Cyber

Search courses, individual lessons, wiki entries, books, podcasts, magazine articles, Daily Cyber News, and Darwin.

NIST SP 800-171 CUI Protection Center

03.05.12 — Authenticator Management

Read the official CUI requirement and assessment content, then use the separately labeled Bare Metal Cyber perspective to connect it to implementation, evidence, and sustained operation.

2Parameters
1Source controls
12Assessment objectives
3Assessment methods

03.05 — Identification and Authentication · NIST SP 800-171 Revision 3

Active
Official NIST requirement content

Security requirement

  1. a.Verify the identity of the individual, group, role, service, or device receiving the authenticator as part of the initial authenticator distribution.
  2. b.Establish initial authenticator content for any authenticators issued by the organization.
  3. c.Establish and implement administrative procedures for initial authenticator distribution; for lost, compromised, or damaged authenticators; and for revoking authenticators.
  4. d.Change default authenticators at first use.
  5. e.Change or refresh authenticators [Organization-defined: frequency] or when the following events occur: [Organization-defined: events].
  6. f.Protect authenticator content from unauthorized disclosure and modification.
Official NIST discussion

Discussion

Authenticators include passwords, cryptographic devices, biometrics, certificates, one-time password devices, and ID badges. The initial authenticator content is the actual content of the authenticator (e.g., the initial password). In contrast, requirements for authenticator content contain specific characteristics. Authenticator management is supported by organization-defined settings and restrictions for various authenticator characteristics (e.g., password complexity and composition rules, validation time window for time synchronous one-time tokens, and the number of allowed rejections during the verification stage of biometric authentication). The requirement to protect individual authenticators may be implemented by 03.15.03 for authenticators in the possession of individuals and by 03.01.01, 03.01.02, 03.01.05, and 03.13.08 for authenticators stored in organizational systems. This includes passwords stored in hashed or encrypted formats or files that contain hashed or encrypted passwords that are accessible with administrator privileges. Actions can be taken to protect authenticators, including maintaining possession of authenticators, not sharing authenticators with others, and immediately reporting lost, stolen, or compromised authenticators. Developers may deliver system components with factory default authentication credentials to allow for initial installation and configuration. Default authentication credentials are often well-known, easily discoverable, and present a significant risk. Authenticator management includes issuing and revoking authenticators for temporary access when they are no longer needed. The use of long passwords or passphrases may obviate the need to periodically change authenticators.

Official organization-defined parameters

Tailoring decisions required

Resolve these values through the governing organization’s approved tailoring and risk-management process before declaring the requirement implemented.

frequencyorganization-defined frequencythe frequency for changing or refreshing authenticators is defined.
eventsorganization-defined eventsevents that trigger the change or refreshment of authenticators are defined.
Bare Metal Cyber interpretation

Implementation perspective

Treat Authenticator Management as a CUI protection outcome that must be reflected in the system boundary, documented implementation, operational behavior, and assessment evidence. Pay particular attention to identity proofing, authentication strength, authenticator lifecycle, and resistance to credential compromise.

  1. Confirm the requirement is in scope for the CUI system components, services, users, and external connections being assessed.
  2. Resolve every organization-defined parameter through an approved governance and tailoring process.
  3. Map each clause of the requirement to an accountable owner, implementation mechanism, and evidence source.
  4. Verify that inherited and shared implementations are supported by current provider evidence and responsibility boundaries.
  5. Collect evidence during normal operation and review changes, exceptions, and deficiencies on a risk-based cadence.

Questions to ask

  • Which CUI assets, data flows, users, and services are protected by this requirement?
  • Which portions are implemented locally, inherited, shared, or not applicable, and what evidence supports that determination?
  • Do the system security plan, deployed configuration, operating process, and assessment evidence tell the same story?
  • What change, incident, or threshold should trigger reassessment?

Evidence and validation

  • identity proofing records
  • authenticator issuance and revocation logs
  • MFA and federation configuration
  • credential inventories and rotation evidence

Common failure patterns

  • MFA applied only to interactive users
  • service credentials without ownership or rotation
  • weak recovery paths that bypass strong authentication
  • federated trust not reviewed after partner changes
Official NIST SP 800-171A content

Assessment objectives and methods

Assessment objectives (12)
  1. a.

    the identity of the individual, group, role, service, or device receiving the authenticator as part of the initial authenticator distribution is verified.

  2. b.

    initial authenticator content for any authenticators issued by the organization is established.

  3. c.

    administrative procedures for initial authenticator distribution are established.

  4. c.

    administrative procedures for lost, compromised, or damaged authenticators are established.

  5. c.

    administrative procedures for revoking authenticators are established.

  6. c.

    administrative procedures for initial authenticator distribution are implemented.

  7. c.

    administrative procedures for lost, compromised, or damaged authenticators are implemented.

  8. c.

    administrative procedures for revoking authenticators are implemented.

  9. d.

    default authenticators are changed at first use.

  10. e.

    authenticators are changed or refreshed [Organization-defined: frequency] or when the following events occur: [Organization-defined: events].

  11. f.

    authenticator content is protected from unauthorized disclosure.

  12. f.

    authenticator content is protected from unauthorized modification.

Examine

  • identification and authentication policy and procedures
  • procedures for authenticator management
  • system configuration settings
  • list of system authenticator types
  • system design documentation
  • system audit records
  • change control records associated with managing system authenticators
  • system security plan
  • other relevant documents or records

Interview

  • personnel with authenticator management responsibilities
  • personnel with information security responsibilities
  • system administrators

Test

  • mechanisms for supporting or implementing the authenticator management capability
Official source-control relationships

Source NIST SP 800-53 controls

These controls are referenced by the official SP 800-171 Rev. 3 OSCAL record. Open the corresponding control pages for complete control text, enhancements, D3FEND mappings, and related learning.

Source controlIA-5Open SP 800-53 control →
Source record

Authoritative sources

Bare Metal Cyber is an independent educational publisher and is not affiliated with or endorsed by NIST. The official publications, the responsible federal agency, and the governing contract or agreement determine applicability, tailoring, assessment depth, and required implementation.