ISO 27001 Control A.5.18: Access Rights
Access control sets the rules, identity management creates the accounts and authentication information proves who is knocking. Access rights are the permissions that actually decide what each person can do once they are in. They are also the part that drifts fastest. Every project, every urgent favor and every role change adds a permission, and almost nothing removes one. A.5.18 is the 18th of 37 organizational controls in our walk through Annex A, and it is where the “creep” gets managed.
If you have ever opened an old user list and found people with access to systems they have never touched, you already know the problem. The control asks for a living process: grant what is needed, check it regularly, adjust it when things change and take it away when it is no longer justified.
What the control requires
Annex A control 5.18 of ISO 27001:2022 states that 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.
The key elements:
- Access rights - the specific permissions, roles and entitlements a person or system holds
- Provisioned - granted through an approved request, with the owner’s authorization
- Reviewed - checked periodically to confirm they are still appropriate
- Modified and removed - adjusted on role changes, and withdrawn at termination or when no longer needed
- In accordance with the access control policy and rules - the process follows what you defined under access control
A.5.18 is a preventive control in ISO/IEC 27002:2022. Annex A states the control; ISO 27002 gives guidance, including obtaining authorization from the asset owner, considering segregation of duties, removing or adjusting rights promptly on change or termination, keeping a central record of rights and reviewing them at regular intervals. It also notes that rights may need to be adjusted before employment ends, depending on the risk of the departure.
How to implement access rights management
Make provisioning a request with an owner
Every grant should answer four questions: who is it for, what exactly do they need, why, and who approved it. The approver should be the owner of the asset or system, not simply the requester’s manager, since the owner understands the risk. A ticket or form that captures these answers takes little effort and creates the audit trail. Grant access by role profiles where you can, so that approval is quick for standard needs and exceptional requests stand out.
Check that the request does not create a conflict. Combinations such as creating and approving the same payments are the classic example, and segregation of duties gives you the principle. Apply least privilege and time limits where possible: temporary elevated access that expires automatically beats permanent access that someone promises to remove.
Review rights on a schedule
Periodic review is the heart of the control. A workable pattern is:
- Quarterly or half-yearly for privileged and high-risk access, such as administrators, finance systems and anything holding confidential data
- Annually for ordinary business applications
- Event-driven whenever someone changes role, a project ends or a supplier contract changes
Ask system owners to review a list of who has what and confirm or remove each entry. Reviewers need information they can understand: names, roles, last login and the level of access. A raw export of group memberships that nobody can read produces rubber-stamping. Record the date, the reviewer, the findings and the actions taken, and follow up until the removals are done.
Handle movers and leavers promptly
When someone changes role, review their rights and remove those tied to the old job. The identity management process should trigger this, supported by HR data. At termination, rights end according to your agreed timing, which may be immediate for higher-risk roles. This needs to line up with responsibilities after termination or change of employment and return of assets, so that physical and logical access end together.
Do not forget access given outside the main directory: local admin rights, shared mailboxes, SaaS invitations, source repository membership, cloud console roles and physical badges. Make a checklist of the places people tend to hold access and use it in both mover and leaver processes.
Keep a record of who holds what
You cannot review what you cannot see. Maintain, per system, a current list of who holds which rights, and keep it in a form that can be exported on request. For many organizations this is simply the output of the directory or application plus the ticket history. For systems without good reporting, a manually maintained register reviewed at the same cadence as the access review is acceptable. Tie the register to your inventory of information and other associated assets so that new systems are added to the review cycle from day one.
Start with the highest-risk systems
If this sounds like a lot, do not try to review everything at once. Pick the systems where misuse would hurt most: your identity provider, cloud administration, source code, finance and the stores of confidential customer data. Run a first review there, fix what you find and record it. Then widen the circle over a few cycles.
A first review is usually revealing. Expect to find former contractors, duplicated accounts, people with administrator rights who need them only occasionally and groups that nobody can explain. Treat these as normal findings of a first pass, not as failures. What matters to an auditor is that you found them, acted and have a schedule for repeating the exercise.
Finally, make removal easy. If taking access away requires a formal change request while granting it takes a message, the system will always drift towards more access. Give reviewers the ability to revoke directly, and agree that revoking something that turns out to be needed is a minor inconvenience, quickly reversible, rather than an incident.
Related controls and clauses
A.5.15 connection. Access control is the policy and rule set that access rights must follow.
A.5.16 connection. Identity management provides the identities that rights are attached to, and the joiner, mover and leaver triggers.
A.5.17 connection. Authentication information governs the credentials used to exercise those rights.
A.5.3 connection. Segregation of duties prevents conflicting combinations of rights.
A.6.5 and A.5.11 connection. Responsibilities after termination or change of employment and return of assets run together with removal of rights at departure.
Clause 9.2 connection. Clause 9.2, Internal audit, is a good place to test whether access reviews really happen and lead to action.
Forward reference. Information security in supplier relationships (A.5.19) starts the supplier group of controls, where access granted to third parties becomes a central theme.
What auditors check
Authorization trail. Auditors pick a sample of recent access grants and look for the request, the approval by the right owner and the business reason.
Access reviews. They ask for the last completed review for key systems, with evidence of who reviewed, what they found and which rights were removed.
Leaver testing. As with identities, they check recent leavers to confirm that rights were removed across all systems within the agreed time.
Mover handling. They look for people who changed role and test whether old rights were withdrawn.
Privileged access. Expect extra focus on administrator and high-impact rights: who holds them, why and how often they are reviewed.
Consistency with policy. The review frequency and approval rules should match what the access control policy says. Mismatches are common findings.
Common mistakes to avoid
Reviews that rubber-stamp. A manager clicking “approve all” on a list they do not understand does not satisfy the control. Provide readable lists and expect some removals.
Only adding, never removing. Access accumulates as people change roles. Moving someone should be a replace, not an add.
Approval by the wrong person. The requester’s manager may not know the risk of a finance system. Asset owners should approve.
No evidence kept. A review done in a meeting with no record counts as not done in an audit. Save the outputs.
Overlooking non-directory access. Local admin rights, cloud consoles and external SaaS accounts hide outside your main identity system.
Permanent temporary access. Emergency or project access that never expires quietly becomes standard. Set an end date at the time of granting.
How 27kay can help
We help organizations replace access creep with a calm, repeatable routine that takes hours rather than weeks each quarter. As part of ISO 27001 implementation, we design request and review steps that fit your tools, run a first review with you and prepare the evidence an auditor will ask for. For the full picture, see our ISO 27001 knowledge hub.
When did someone last remove a permission in your organization, and would you be able to show it? Get in touch - we will help you make access reviews something you can rely on.