A.5 Organizational controls

A.5.17 Authentication information

Not mandatory by default – decided in your SoA

What it means in plain language

Manage passwords, keys and other secrets securely: how they are issued, stored, changed and what users must do with them.

Is it mandatory? Not automatically. You must consider this control in your Statement of Applicability (6.1.3 d). Include it if your risk assessment, laws, contracts or business needs require it; if you exclude it, write down a justification an auditor will accept.

Why this control matters

Authentication controls should govern how passwords, keys, tokens, and recovery factors are issued and handled across their lifecycle. The practical risk is not only weak secrets, but also poor storage, accidental sharing, unmanaged reset processes, and gaps when staff move or leave. Clear allocation distinguishes user responsibilities from administrator responsibilities and shows how MFA, vaulting, and temporary credential handling fit together.

Common auditor findings to check for

Potential gaps to test in your own environment, not a claim about observed audit frequency.

  • Passwords or API keys are shared in chat, spreadsheets, or tickets, so no accountable user can be identified and secret exposure cannot be traced.
  • Temporary credentials remain valid after first login or are not forced to change, allowing unauthorized reuse of onboarding secrets.
  • MFA is deployed selectively, leaving remote email, VPN, or privileged access paths protected by weaker authentication than the policy intends.

How you can implement it

Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.

  • State how different authentication factors are issued, stored, rotated, recovered, and revoked. The policy should set principles such as unique credentials, MFA for sensitive services, and prohibition on storing secrets in plain text. The procedure should describe approved storage methods, such as a password manager or secret vault, and who administers them.
  • Separate end-user duties from administrator duties. Users must protect passwords, not disclose one-time codes, and report suspected compromise. Administrators should enforce complexity or passphrase rules where relevant, disable shared passwords unless formally justified, and ensure service account secrets have named owners, rotation plans, and review dates. Include a process for secure reset after identity verification.
  • Define lifecycle handling for temporary credentials, API keys, recovery codes, SSH keys, and hardware tokens. Temporary credentials should expire quickly and require first-use change where applicable. Recovery mechanisms need approval and logging so social engineering attempts can be traced. For privileged accounts, require stronger authentication and a second channel for resets or enrolment changes.
  • Use illustrative review cadence: monthly checks for admin account enrolment, quarterly secret vault audits, and event-driven reviews after compromise, staff departure, or supplier termination. Retain evidence from vault access logs, MFA enrolment reports, password reset tickets, and rotation records. Where legacy systems cannot support the intended control, document compensating measures and an end-date for remediation.

What an auditor will ask to see

  • Authentication Information Management procedure and password manager or secret vault configuration record.
  • MFA enrolment report showing user, method, protected system, and exceptions approved by owner.
  • Secret rotation log for API keys, service passwords, and administrative tokens with dates and accountable owners.

Baseline documents in the kit

These free kit documents help you document or evidence A.5.17. Each one is tailored to your organization when you build your kit.

Connect this work to your ISMS

Review the dependencies with A.8.5 — Secure authentication and A.8.2 — Privileged access rights. Keep the ownership and evidence consistent across these activities.

Required information and the kit’s 19-document core for the wider implementation context.

Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.

For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.

Get these documents tailored to your organization

109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.

Start free

Plain-language interpretation by an ISO/IEC 27001 lead implementer, not the official text of ISO/IEC 27001:2022.