A.5 Organizational controls

A.5.18 Access rights

Not mandatory by default – decided in your SoA

What it means in plain language

Grant, review, change and remove access rights in a controlled way, with regular reviews.

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

Access rights become weak when request, approval, implementation, and removal steps are split across inboxes and system consoles without a single accountable trail. Teams should align the Access Control Policy, User Access Management Procedure, and Access Rights Register so reviewers can see who approved what, when it was changed, and why it was removed. The strongest approach ties each change to a business need, review cadence, and named owner.

Common auditor findings to check for

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

  • Access is granted from informal messages without manager or system-owner approval, so the organization cannot show a controlled decision trail for user entitlement changes.
  • Periodic reviews exist but omit shared accounts, service accounts, or privileged roles, leaving stale access unnoticed and weakening evidence that access is still justified.
  • Leavers are removed from some platforms but not others, creating a mismatch between HR exit timing and technical revocation records that invites follow-up questions.

How you can implement it

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

  • Define a request-and-approval workflow that separates requester, approver, and implementer. For business applications, require the line manager and, where needed, the asset or system owner to approve before IT applies the change. Capture business justification, account type, scope, start date, and expiry date in the ticket or access log.
  • Run risk-based access reviews on a cadence matched to the system criticality. For high-risk systems, ask managers and system owners to confirm each user, privileged role, and inactive account; record attestation, exceptions, and remediation deadlines in the Access Rights Register.
  • Set explicit removal triggers for termination, role change, leave, contract end, and prolonged inactivity. Use HR exit notices, IAM workflow alerts, and service desk tasks so removal is time-bound. Record completion timestamps and any compensating restriction applied while access is being withdrawn.
  • Treat exceptions as controlled decisions, not informal workarounds. Require documented risk acceptance for temporary access, break-glass accounts, or emergency approvals. Keep evidence of periodic recertification, failed removals, and follow-up actions so auditors can trace both access administration and monitoring of exceptions.

What an auditor will ask to see

  • Access Rights Register entries showing user, role, approval date, review date, removal date, and reviewer comments.
  • Sample access request tickets with manager approval, system owner sign-off, and implementation timestamps for joiner, mover, and leaver events.
  • Quarterly review report for critical systems with exceptions, stale accounts, remediation owners, and closure evidence.
  • HR termination export matched to account-disable logs for the same date range, showing timely revocation across systems.

Baseline documents in the kit

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

Connect this work to your ISMS

Review the dependencies with A.5.15 — Access control and A.5.16 — Identity management. 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.