A.5.18ISO 27001Last reviewed 19 February 2026

ISO 27001 A.5.18: Access rights

Privilege creep is one of the most common audit findings out there. Someone joins the marketing team, moves to product, then to engineering - and by the end they have access to everything from the CRM to the production database. Nobody removed the old permissions.

Work through the ISO 27001 assessment, record supporting evidence and review the gaps in your answers.

Start my free ISO 27001 assessmentNo account · No credit card · Save when useful

Requirement summary

Access rights to information and other associated assets shall be provisioned, reviewed, modified and removed in accordance with the organization's topic-specific policy on and rules for access control.

Check the source wording and scope in ISO/IEC 27001:2022. The guidance below explains how to approach a review.

In Plain Language

This control is about the operational management of access rights: granting them properly, reviewing them regularly, updating them when roles change, and revoking them when they are no longer needed. It is separate from identity management (A.5.16) - a person can keep their identity but their access rights should change as their role evolves.

Everything here ties back to the principles in your access control policy (A.5.15) - least privilege and need-to-know. Access should never be granted without proper authorisation, and stale permissions need to be actively cleaned up.

How to Implement

Build a structured process covering the full access rights lifecycle: provisioning, review, modification, and revocation.

For provisioning, set up a formal request-and-approve workflow. Every request needs a business justification, specific resource and access level details, and sign-off from the resource owner. Pre-define standard role packages so you are not reinventing the wheel for every new hire.

For role changes, trigger an access review whenever someone moves team, department, or location. The new manager approves what is needed going forward, the old manager confirms what can be removed. This is how you stop privilege creep.

For periodic reviews, set a schedule based on system criticality. System and information owners should verify that each user still needs their current access. Document the results and act on findings. Automate with identity governance tooling where you can - manual reviews do not scale well.

For revocation, be prompt. Cover all the scenarios: someone leaving the organisation, finishing a project or contract, changing roles, or going on extended leave. Wire this into your offboarding process so nothing falls through.

Set up a break-glass procedure for emergencies where access is needed urgently outside normal channels. Include enhanced logging, mandatory post-incident review, time-limited grants, and automatic revocation. Every emergency access event should be documented and reviewed by management.

Evidence to review

Access request and approval records for recent provisioning activities
Periodic user access review records with actions taken on findings
Evidence of access modification when users change roles
Records of timely access revocation for recent departures
Emergency access procedure documentation and usage logs

Common Mistakes

Access rights accumulate over time without removal of unnecessary privileges
Access reviews are conducted but findings are not remediated in a timely manner
No formal approval workflow for access requests resulting in ad hoc provisioning
Access is not modified when users change roles within the organization
Emergency access is granted but not reviewed or revoked after the emergency

Related Controls Across Frameworks

Framework	Control ID	Relationship
SOC 2	SOC 2 CC6.2: Logical and Physical Access - User Registration and Authorization	Equivalent
SOC 2	SOC 2 CC6.3: Logical and Physical Access - Role-Based Access and Least Privilege	Related
GDPR	GDPR Art.32: Security of Processing	Related
NIS2	NIS2 Art.21(2)(i): Human Resources Security and Access Control Policies	Related

Frequently Asked Questions

What is privilege creep and how do we prevent it?

It is what happens when people change roles and keep accumulating access without the old stuff being removed. After a few moves, someone might have admin access to systems they haven't touched in years. Prevent it by running regular access reviews, using role-based access that adjusts when roles change, and having managers periodically verify what their team actually needs. Identity governance tools can flag excessive access automatically, which helps a lot at scale.

How should we handle emergency access requests?

Have a documented break-glass procedure ready before you need it. It should cover: who can approve (senior management, even verbally if needed - document it afterwards), time limits on the access grant, enhanced logging of everything done during the emergency session, automatic revocation after a set period, and a mandatory post-incident review. The point is to allow urgency without throwing controls out the window.

Track ISO 27001 compliance in one place

Work through the ISO 27001 assessment, record supporting evidence and review the gaps in your answers.

Start Free Assessment

Start without an account · Sign up only to save

Start my free ISO 27001 assessment