A.5 Organizational controls

A.5.16 Identity management

Not mandatory by default – decided in your SoA

What it means in plain language

Manage the full lifecycle of user identities – create, change, disable, delete – with one identity per person.

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

Identity management should control how each identity is created, changed, disabled, and deleted across the person’s lifecycle. The main risk is drift between HR records, directory accounts, and application identities, especially when contractors, movers, and leavers are handled manually or by different teams. A controlled identity lifecycle assigns clear ownership for account lifecycle events and defines when exceptions such as service or shared identities are acceptable and how they are controlled.

Common auditor findings to check for

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

  • New hires receive accounts before HR records are complete, causing mismatched names, wrong managers, or access based on informal requests rather than approved identity data.
  • Mover changes update email but not line-of-business systems, leaving former access active after a transfer of duties or location.
  • Leaver processing removes the main account but leaves orphaned identities, service accounts, or external collaboration access active beyond termination.

How you can implement it

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

  • Build the lifecycle around a single authoritative source, usually HR for staff and a vendor register for contractors, with the identity management procedure defining trigger events and required attributes. Include joiner, mover, and leaver steps, account uniqueness rules, and a prohibition on multiple personal identities unless a documented legal or operational case exists.
  • Define accountable roles for creation, validation, modification, suspension, and deletion. HR should initiate employment changes; managers should confirm need; IT or IAM administrators should execute and record the change; data owners should approve exceptions. The procedure should specify turnaround targets as illustrative operational service levels, not ISO requirements, and identify backup approvers for urgent cases.
  • Include controls for shared, service, and privileged identities: owner naming, separate password vaulting or secret storage, periodic review, and logs that link actions to a human operator. When an identity is reused or reassigned, record the rationale and deprovision the prior association. Align offboarding with asset return, mailbox retention, legal hold, and supplier end dates.
  • Test the process with sample cases such as promotion, resignation, maternity leave cover, and contractor expiry. Check whether access removal, group membership updates, and downstream SaaS deactivation happen consistently. Maintain evidence from ticket queues, HR extracts, identity provider logs, and exception registers so the lifecycle can be traced from trigger to closure.

What an auditor will ask to see

  • Joiner-mover-leaver procedure and HR trigger records showing identity creation, changes, suspension, and deletion steps.
  • Identity provisioning tickets linked to a named person, manager approval, unique identifier, and system account list.
  • Leaver checklist, deactivation log, and exception register for retained service or shared identities with owners and expiry dates.

Baseline documents in the kit

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

Connect this work to your ISMS

Review the dependencies with A.6.5 — Responsibilities after termination or change of employment and A.5.18 — Access rights. Keep the ownership and evidence consistent across these activities.

ISO/IEC 27001 vs SOC 2: evidence you can reuse 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.