What it asks for. Authenticators such as passwords, tokens, keys and certificates must be managed through their life: verify identity at issue, set initial content, ensure strength, handle loss and revocation, change defaults, protect them from disclosure and change them when appropriate.
In practice. This means a password policy aligned with current guidance (length over complexity, screening against breached passwords, no forced periodic change without cause), phishing-resistant MFA where possible, secure enrolment and recovery processes, and secrets managers for machine credentials. Auditors look for policy settings, enrolment procedures, evidence that default credentials are changed and how secrets are stored and rotated.
Common gaps. Weak account recovery and help desk reset processes are a frequent route around strong authentication. Secrets in source code, scripts and configuration files remain a widespread gap.