OpenParable
Skip to content
← Back to skills

Authenticator Management (03.05.12)_authenticator-management

DevOps & Security

Authenticator Management (03.05.12)_authenticator-management is an Agent Skill for devops & security published in the CyberStrikeus/CyberStrike repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/CyberStrikeus/CyberStrike/blob/HEAD/.cyberstrike/skill/NIST/SP800-171_rev3/03.05_identification-and-authentication/Authenticator Management (03.05.12)_authenticator-management/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/authenticator-management-03-05-12-authenticator-management, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Authenticator Management (03.05.12) Authenticator Management

High-Level Description

Family: Identification and Authentication Framework: NIST SP 800-171 Rev 3 Applicability: Systems processing, storing, or transmitting CUI

Verify the identity of the individual, group, role, service, or device receiving the authenticator as part of the initial authenticator distribution. Establish initial authenticator content for any authenticators issued by the organization. Establish and implement administrative procedures for initial authenticator distribution; for lost, compromised, or damaged authenticators; and for revoking authenticators. Change default authenticators at first use. Change or refresh authenticators [organization-defined] or when the following events occur: [organization-defined]. Protect authenticator content from unauthorized disclosure and modification.

What to Check

  • Verify Authenticator Management (03.05.12) Authenticator Management is implemented for CUI systems
  • Review SSP documentation for Authenticator Management (03.05.12)
  • Validate CMMC Level 2 assessment objective for Authenticator Management (03.05.12)
  • Confirm POA&M addresses any gaps for Authenticator Management (03.05.12)

How to Test

Step 1: Review System Security Plan

Examine the SSP for Authenticator Management (03.05.12) implementation description and responsible parties.

Step 2: Assess Implementation

# Verify security controls protecting CUI
# Check access controls, encryption, monitoring as applicable

# For Linux systems:
ls -la /etc/security/ 2>/dev/null
grep -r "CUI\|controlled" /etc/security/ 2>/dev/null

# For cloud:
# Use cloud-audit-mcp tools to assess posture

Step 3: CMMC Assessment Validation

Verify this requirement passes CMMC Level 2 assessment methodology per SP 800-171A Rev 3.

Tools

ToolPurposeUsage
cloud-audit-mcpAssess cloud CUI environmentcloud_audit_* tools
Manual ReviewSSP and POA&M reviewDocumentation analysis

Remediation Guide

Requirement Statement

Verify the identity of the individual, group, role, service, or device receiving the authenticator as part of the initial authenticator distribution. Establish initial authenticator content for any authenticators issued by the organization. Establish and implement administrative procedures for initial authenticator distribution; for lost, compromised, or damaged authenticators; and for revoking authenticators. Change default authenticators at first use. Change or refresh authenticators [organization-defined] or when the following events occur: [organization-defined]. Protect authenticator content from unauthorized disclosure and modification.

Supplemental Guidance

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.

Risk Assessment

FindingSeverityImpact
Authenticator Management (03.05.12) Authenticator Management not implementedHighCUI Protection - Identification and Authentication
Authenticator Management (03.05.12) partially implemented (POA&M)MediumCMMC certification risk

CWE Categories

CWE IDTitle
CWE-287Improper Authentication

References

Checklist

  • SSP documents Authenticator Management (03.05.12) implementation
  • Evidence of operating effectiveness collected
  • POA&M addresses any gaps
  • CMMC assessment objective met
  • Continuous monitoring active