ISO 27001 Control A.5.17: Authentication Information
Passwords, passphrases, tokens, certificates, security keys, PINs: these are the things that prove an identity is genuine. If someone else gets hold of them, nothing else in your access model matters, because the system will happily treat the intruder as the real person. A.5.17 deals with how you issue, store, change and retire this material, and how you teach people to treat it. It is the 17th of 37 organizational controls in our walk through Annex A.
This is one of the areas where guidance has moved on a lot. Older policies demanded monthly password changes and complex character rules, which mostly produced predictable passwords on sticky notes. Modern thinking, including what ISO 27002 now describes, favors long, unique secrets, multi-factor authentication and fewer forced changes. The control is a good chance to update habits as well as paperwork.
What the control requires
Annex A control 5.17 of ISO 27001:2022 states that allocation and management of authentication information shall be controlled by a management process, including advising personnel on the appropriate handling of authentication information.
The key elements:
- Authentication information - everything used to prove identity, from passwords and PINs to hardware tokens, certificates and biometric templates
- Allocation and management - how it is issued, delivered, changed, reset, revoked and recovered
- Controlled by a management process - a defined and repeatable procedure, not left to individual systems or administrators
- Advising personnel - people are told what is expected of them, such as keeping secrets confidential and not sharing them
A.5.17 is a preventive control in ISO/IEC 27002:2022. Annex A states the control; ISO 27002 gives guidance, including that initial credentials should be temporary and unique, that people should be verified before credentials are reset, that default vendor passwords should be changed, and that personnel should be asked to sign a statement to keep personal authentication information confidential. It also points out that when password-based authentication is used, systems should support strong, user-chosen passwords and discourage predictable ones.
How to implement authentication information management
Set clear rules for secrets
Write a short standard that says what a good secret looks like for your environment. Practical elements usually include:
- Minimum length, with a preference for long passphrases over complexity tricks
- A requirement that passwords are unique per service and never reused from personal accounts
- Use of a company-approved password manager so that people do not have to remember dozens of secrets
- Checks against lists of known compromised passwords where your tools support it
- Changes triggered by evidence of compromise rather than by a fixed calendar, unless a specific system or rule requires otherwise
Whatever you choose, make the technical settings in your systems match the written standard. A policy requiring fourteen characters and a system that accepts eight is an easy audit finding.
Control issuing, resetting and recovery
The riskiest moments are the start and the middle of the life cycle. When an identity is created, as described under identity management, initial credentials should be unique and temporary, delivered securely and changed at first use. Never send a username and password in the same message.
Resets deserve special care because attackers target them. Decide how you verify the person asking: a call back to a known number, confirmation by the manager, or self-service backed by a second factor. Document the steps, and apply them to administrators and executives as strictly as to everyone else. Equally, define recovery for lost hardware tokens and phones, including how a lost device is reported quickly. Reporting habits from information security event reporting apply here.
Always change vendor defaults on devices, applications and accounts before they go live.
Prefer multi-factor and phishing-resistant methods
Where you can, add a second factor. Authenticator apps are better than SMS codes, and hardware security keys or passkeys are better still against phishing. Prioritize the places where compromise would hurt most: email, identity providers, remote access, administrator accounts and anything that holds confidential information. Document where multi-factor is required and where an exception has been granted, with the reason and a plan.
For service accounts, API keys and certificates, the same principles apply in a different form: store them in a secrets vault rather than in code or chat, rotate them on a schedule, and give them only the access needed. Never embed them in documents or shared notes.
Tell people what you expect and prove they were told
The control explicitly includes advising personnel. A one-page guide, a short section in induction and a reminder in information security awareness, education and training can cover it: do not share passwords, do not write them where others can see them, use the password manager, report suspected compromise at once. Many organizations also include a confidentiality clause covering credentials in the terms and conditions of employment. Keep records of acknowledgement. Keep the advice realistic, too: if people are told never to write anything down but given no password manager, they will find their own solution.
Plan for compromise, not just prevention
However good your standard is, some credentials will leak, through phishing, reuse on a breached site or a laptop left in a taxi. Decide in advance what happens next. Who is told, how fast can a session be revoked, which secrets must be rotated, and how do you check for misuse? People should know that reporting a possible compromise quickly is welcomed, not punished. A short runbook covering the first hour is worth far more than a long policy, and rehearsing it once a year with a realistic scenario shows both you and an auditor that it works.
Keep the process light enough that it gets used. If rotating a shared key means a week of coordination, teams will delay it. Automate rotation where you can, and keep an inventory of where each important secret is used so that changing it does not break production unexpectedly.
Related controls and clauses
A.5.15 connection. Access control sets the rules that authentication enforces.
A.5.16 connection. Identity management issues the identities that authentication information proves.
A.5.10 connection. Acceptable use of information and other associated assets is a natural home for the rule that credentials are personal and must not be shared.
A.6.2 connection. Terms and conditions of employment can carry the obligation to keep credentials confidential.
A.6.3 connection. Information security awareness, education and training teaches safe handling and phishing recognition.
A.6.8 connection. Information security event reporting is how a suspected leaked password reaches the right person quickly.
Forward reference. Access rights (A.5.18) is next in the series, and the technological control on secure authentication (A.8.5) covers the system side of this topic later on.
What auditors check
A management process. Auditors look for a documented procedure for issuing, resetting and revoking credentials, and ask who is responsible for it.
Technical settings match policy. They compare the password standard with real settings in the directory, key applications and remote access, and check where multi-factor is enforced.
Default and initial credentials. Expect questions on how initial passwords are delivered and whether defaults were changed on devices and applications.
Reset verification. They may test the help desk process by asking how identity is verified before a reset, or by observing a request.
Secrets in the wrong places. Auditors may search for credentials in documents, wikis, tickets or code repositories, or ask how service account secrets are stored.
Staff awareness. Interviews and acknowledgement records show whether people have been advised and understand their responsibilities.
Common mistakes to avoid
Forced frequent changes. Monthly changes tend to produce weaker, more predictable passwords. Change on evidence of compromise unless a specific requirement says otherwise.
Policy and system out of sync. A strong written standard that the system does not enforce proves nothing.
Sending credentials together. Username and temporary password in one email is a gift to anyone who reads it.
Weak reset process. Attackers know that talking a help desk into a reset is easier than breaking a password. Verify properly, and test it.
Shared secrets in chat and documents. Credentials pasted into messages, tickets or spreadsheets stay there forever. Give people a vault.
MFA with large unreviewed exceptions. A requirement that exempts executives and service accounts leaves the highest-value targets unprotected.
How 27kay can help
We help organizations modernize how they handle credentials in a way that makes security easier for people instead of harder. As part of ISO 27001 implementation, we review your standards and settings, design a reset and recovery process that holds up under pressure and prepare the evidence an auditor will ask for. For the full picture, see our ISO 27001 knowledge hub.
Could your help desk be talked into resetting the wrong person’s password? Get in touch - we will help you close that door before someone else tries it.