Skip to content
Organisational controls
ISO 27001A.5.17

ISO 27001 Annex A 5.17 Authentication information

What it says

Allocation and management of authentication information shall be controlled by a management process, including advising personnel on appropriate handling of authentication information.

Quoted as published. Everything else on this page is written by Control Stack.

In plain English

Control the allocation and management of authentication information through a management process, which must include advising personnel how to handle it appropriately.

Your organisation must control the allocation and management of authentication information through a management process. Authentication information is what proves an identity at sign-in, such as passwords, PINs, cryptographic keys and data on hardware tokens. The process has two required parts:

  • Allocation and management: how this information is issued, replaced, reset and stored.
  • Advising personnel: telling people how to handle it appropriately. Your organisation decides what is appropriate, based on its risks and context.

Annex A 8.5 covers the authentication technologies themselves.

Why it matters

A vendor's default password left unchanged, a temporary password emailed in clear text, or a reset given to a caller nobody checked can each let someone sign in as another person. A controlled process and clear advice to personnel reduce those openings.

How to implement

  1. Write the process for issuing and replacing authentication information.

    Cover passwords, PINs, keys and tokens. Confirm the person's identity before issuing a new, replacement or temporary value. Deliver it by encrypted portal or another protected channel, not plain email. Make temporary values unique, hard to guess and changed at first use. Record significant events, such as issuing and resetting.

  2. Change vendor default credentials at installation.

    Add this to your build steps for devices, network equipment, applications and admin consoles, and check with a scan or a test sign-in before go-live. For a bought service, change the first administrator password the supplier issues as soon as you receive it.

  3. Set password systems to enforce the process.

    Let users set their own passwords, enforce a minimum length, require a change at first sign-in, block common, breached and previously used passwords, hide entry on screen and store passwords only as salted hashes. Where a bought service lacks these settings, use single sign-on, or record the gap if it offers neither.

  4. Keep shared and system secrets in an approved vault.

    Hold service account passwords, API keys and emergency administrator credentials in a password manager or similar tool, with access limited and logged. Change them when someone who knew them leaves or changes role, and keep them out of scripts and shared documents.

  5. Advise personnel how to handle authentication information.

    Give this advice to current personnel now, and to each new holder when credentials are first issued: keep secrets confidential, never share personal ones, use a different password for each service, avoid passwords built from personal details or dictionary words, and change a password at once if it may be exposed.

Keep it running

Force a change when compromise is suspected or someone who knew a shared secret leaves. Look again when a bought service brings its own passwords, the identity system changes, or incidents point to reset or password weaknesses.

Evidence and audit

  1. Check 1 of 5What an auditor asks for

    Ask for

    Records of recent resets and tokens issued by the service desk, plus a test reset request from someone it cannot identify.

    Look at

    How identity was checked, how the new value was delivered, and whether the test request gets through.

    Good evidence

    Each sampled record shows an identity check and delivery over a protected channel, and the test request is refused until identity is confirmed.

  2. Check 2 of 5What an auditor asks for

    Ask for

    Password settings in the identity system and in each bought service with its own sign-in.

    Look at

    Minimum length, change at first sign-in, blocking of common and breached passwords, and whether a test account can keep a temporary password.

    Good evidence

    Settings match the process on every sampled system, and a test account cannot keep a temporary password or choose a commonly used one.

  3. Check 3 of 5What an auditor asks for

    Ask for

    A list of recently installed devices and software taken from a network discovery scan or purchase records, with a test sign-in or credential scan for vendor defaults.

    Look at

    Whether any default password or key still works.

    Good evidence

    No sampled system accepts a vendor default credential.

  4. Check 4 of 5What an auditor asks for

    Ask for

    The vault for shared and system secrets, matched to the list of service accounts and shared identities.

    Look at

    Accounts whose secrets are held elsewhere, using a search of scripts and shared documents, and who can reach the vault.

    Good evidence

    Every sampled secret is in the approved vault, access is limited and logged, and the search finds none in plain text.

  5. Check 5 of 5What an auditor asks for

    Ask for

    The advice given to personnel on handling authentication information, with records of who received it.

    Look at

    What the advice covers, and who is missing when the records are compared with the current staff and contractor list.

    Good evidence

    The advice covers keeping secrets confidential, not sharing them and what to do after an exposure, and everyone on the staff and contractor list has received it.

Mappings

Closest match in ASD Essential Eight: E8-MF-ML3.3, Phishing-resistant multi-factor authentication for data repositories, which this control covers in full and more.

Essential Eight

ASD Essential Eight: 4 mappings

ASD ISM

ASD Information Security Manual: 55 mappings

ASD Essentials

ASD Essentials for enterprise IT: 3 mappings

Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.

Get help with this control

ISO 27001 training

Mindset Cyber, a PECB Authorised Titanium Partner, sells official PECB ISO/IEC 27001 courses that map directly to the controls in this library.