ISO 27001:2022 Annex A 5.18 – Access Rights Explained

Access control decisions only become effective when access rights are correctly granted, changed, and removed.

Annex A 5.18 exists to ensure organisations manage access rights in a controlled, business-led way throughout their lifecycle, so that people and systems have the access they need — and no more.

This control focuses on the practical execution of access control, turning policy and identity management into day-to-day action.

ISO 27001

Quick Guide: Annex A 5.18 at a Glance

Annex A 5.18 of ISO 27001:2022 addresses the provisioning, modification, and revocation of access rights.

At a practical level, this means:

  • Granting access rights based on business need
  • Ensuring access is authorised before being provided
  • Adjusting access when roles or responsibilities change
  • Revoking access promptly when it is no longer required
  • Maintaining appropriate oversight of access changes

The control does not require complex workflows or tooling. It expects a clear, consistent process that prevents unauthorised, excessive, or lingering access.

In-Depth Guide to Annex A 5.18

What Is Annex A 5.18 and Why Does It Matter?

Most access-related incidents are not caused by attackers breaking controls, but by:

  • Excessive access being granted
  • Access not being removed after role changes
  • Former users retaining access
  • Privileged access persisting without review

Annex A 5.18 addresses these risks by ensuring access rights are actively managed, rather than assumed to remain appropriate indefinitely.

This control applies to:

  • Employees
  • Contractors and third parties
  • Temporary or privileged users
  • Physical and logical access

Consistency across all user types is essential.

How to Implement Annex A 5.18 Effectively

A pragmatic approach to Annex A 5.18 usually includes the following elements.

1. Grant Access Based on Business Authorisation

Access rights should be granted only after appropriate authorisation.

This typically involves:

  • Approval from the information or system owner
  • Verification that access aligns with the user’s role
  • Ensuring segregation of duties is considered where relevant

Access should never be provisioned before authorisation is obtained.

2. Align Access Rights With Job Roles

Access is most manageable when it aligns with defined roles.

Role-aligned access:

  • Reduces excessive permissions
  • Simplifies access requests and approvals
  • Supports consistent application across systems

Where roles are not formally defined, access decisions should still be justified against business responsibilities.

3. Modify Access Promptly When Roles Change

Access requirements often change before people leave the organisation.

Triggers for access modification include:

  • Promotion or demotion
  • Temporary assignments
  • Changes in responsibilities

Failure to adjust access during role changes is a common source of hidden risk.

4. Revoke Access When It Is No Longer Required

Access should be removed promptly when it is no longer justified.

This includes:

  • Leavers
  • End of contracts or temporary assignments
  • Removal of system or service use

Revocation should cover both logical and physical access.

5. Pay Particular Attention to Privileged Access

Privileged access carries higher risk and greater potential impact.

Organisations often apply:

  • Additional approval steps
  • Tighter scope and duration
  • More frequent review

Privilege should be controlled deliberately, not inherited by default.

6. Maintain Visibility of Access Changes

Maintaining records of access changes supports:

  • Accountability
  • Investigation of incidents
  • Assurance and review

Records do not need to be complex, but they should be reliable and protected.

In-Depth Guide to Annex A 5.1

What is Annex A 5.1 and Why Does It Matter?

  • What the organisation values
  • How security decisions are approached
  • Where accountability sits
  • Aligns security with business objectives
  • Supports proportionate, risk-based decisions
  • Provides a reference point during incidents and disputes
  • Creates consistency without bureaucracy

How to Implement Annex A 5.1 Effectively

1. Define a Comprehensive Information Security Policy
  • Scope: What the policy applies to (systems, data, people).
  • Objectives: Why security is important for the business.
  • Roles & Responsibilities: Who is accountable for security.
  • Key Principles: Risk management, access control, and data protection.
2. Secure Senior Management Approval
  • Review and approve policies.
  • Ensure resources are allocated for implementation.
  • Lead by example in enforcing security policies.
3. Communicate and Train Employees
  • Include security policies in onboarding and ongoing training.
  • Ensure policies are easily accessible to all employees.
  • Encourage acknowledgment and acceptance of security responsibilities.
4. Regular Review & Continuous Improvement
  • Set a schedule for periodic policy reviews (at least annually).
  • Update policies based on business changes, new threats, or regulatory updates.
  • Conduct audits to ensure compliance and effectiveness.
5. Integrate Policies into the ISMS
  • Use it to develop more detailed security procedures.
  • Ensure policies align with other Annex A controls and broader risk management practices.
Key Differences: ISO 27001:2013 vs ISO 27001:2022
AspectISO 27001:2013ISO 27001:2022
Control StructureTwo separate controls: 5.1.1 & 5.1.2Merged into one control (5.1)
Implementation GuidanceLess prescriptiveMore detailed guidance for policy creation and alignment
Awareness & TrainingNot explicitly mentionedExplicitly requires policies to be part of training programmes
Attributes TableNot includedew attributes table for mapping policies to industry terms
Common Challenges & How to Overcome Them
  • Challenge: Employees don’t follow security policies.
  • Solution: Make policies practical and relevant to daily work. Use real-world examples in training.
  • Challenge: Policies are outdated or too generic.
  • Solution: Schedule annual reviews and update policies based on real threats and business changes.
  • Challenge: Policies are written in technical jargon.
  • Solution: Use plain language that all employees can understand.
  • Challenge: Lack of leadership buy-in.
  • Solution: Show how weak security affects business objectives—costs of breaches, loss of client trust, and legal penalties.
Final Recommendations
  • Make security policies living documents—review, refine, and update regularly.
  • Use policy training and awareness to create a security-conscious workforce.
  • Ensure policies are accessible, relevant, and easy to understand.
  • Keep policies aligned with business strategy and regulatory requirements.
  • Engage leadership in driving security culture from the top down.

Common Challenges and How to Overcome Them

  • Access granted informally or “just in case”
  • Require justification and authorisation
  • Access not updated during role changes
  • Align access changes with HR and operational processes
  • Delayed access removal for leavers
  • Integrate revocation into exit procedures
  • Poor oversight of privileged access
  • Apply tighter controls and visibility

Access risk accumulates quietly when rights are not actively managed.

In-Depth Guide to Annex A 5.1

What is Annex A 5.1 and Why Does It Matter?

  • What the organisation values
  • How security decisions are approached
  • Where accountability sits
  • Aligns security with business objectives
  • Supports proportionate, risk-based decisions
  • Provides a reference point during incidents and disputes
  • Creates consistency without bureaucracy

How to Implement Annex A 5.1 Effectively

1. Define a Comprehensive Information Security Policy
  • Scope: What the policy applies to (systems, data, people).
  • Objectives: Why security is important for the business.
  • Roles & Responsibilities: Who is accountable for security.
  • Key Principles: Risk management, access control, and data protection.
2. Secure Senior Management Approval
  • Review and approve policies.
  • Ensure resources are allocated for implementation.
  • Lead by example in enforcing security policies.
3. Communicate and Train Employees
  • Include security policies in onboarding and ongoing training.
  • Ensure policies are easily accessible to all employees.
  • Encourage acknowledgment and acceptance of security responsibilities.
4. Regular Review & Continuous Improvement
  • Set a schedule for periodic policy reviews (at least annually).
  • Update policies based on business changes, new threats, or regulatory updates.
  • Conduct audits to ensure compliance and effectiveness.
5. Integrate Policies into the ISMS
  • Use it to develop more detailed security procedures.
  • Ensure policies align with other Annex A controls and broader risk management practices.
Key Differences: ISO 27001:2013 vs ISO 27001:2022
AspectISO 27001:2013ISO 27001:2022
Control StructureTwo separate controls: 5.1.1 & 5.1.2Merged into one control (5.1)
Implementation GuidanceLess prescriptiveMore detailed guidance for policy creation and alignment
Awareness & TrainingNot explicitly mentionedExplicitly requires policies to be part of training programmes
Attributes TableNot includedew attributes table for mapping policies to industry terms
Common Challenges & How to Overcome Them
  • Challenge: Employees don’t follow security policies.
  • Solution: Make policies practical and relevant to daily work. Use real-world examples in training.
  • Challenge: Policies are outdated or too generic.
  • Solution: Schedule annual reviews and update policies based on real threats and business changes.
  • Challenge: Policies are written in technical jargon.
  • Solution: Use plain language that all employees can understand.
  • Challenge: Lack of leadership buy-in.
  • Solution: Show how weak security affects business objectives—costs of breaches, loss of client trust, and legal penalties.
Final Recommendations
  • Make security policies living documents—review, refine, and update regularly.
  • Use policy training and awareness to create a security-conscious workforce.
  • Ensure policies are accessible, relevant, and easy to understand.
  • Keep policies aligned with business strategy and regulatory requirements.
  • Engage leadership in driving security culture from the top down.

Final Recommendations

Annex A 5.18 is about keeping access aligned with reality.

When access rights are managed effectively:

  • Unauthorised access risk is reduced
  • Insider and privilege-related risks are controlled
  • Accountability is clearer
  • Other access controls function as intended

Access control does not stop at policy or identity creation. It succeeds or fails in how access rights are granted, changed, and removed over time.

That is the outcome Annex A 5.18 is designed to achieve.

In-Depth Guide to Annex A 5.1

What is Annex A 5.1 and Why Does It Matter?

  • What the organisation values
  • How security decisions are approached
  • Where accountability sits
  • Aligns security with business objectives
  • Supports proportionate, risk-based decisions
  • Provides a reference point during incidents and disputes
  • Creates consistency without bureaucracy

How to Implement Annex A 5.1 Effectively

1. Define a Comprehensive Information Security Policy
  • Scope: What the policy applies to (systems, data, people).
  • Objectives: Why security is important for the business.
  • Roles & Responsibilities: Who is accountable for security.
  • Key Principles: Risk management, access control, and data protection.
2. Secure Senior Management Approval
  • Review and approve policies.
  • Ensure resources are allocated for implementation.
  • Lead by example in enforcing security policies.
3. Communicate and Train Employees
  • Include security policies in onboarding and ongoing training.
  • Ensure policies are easily accessible to all employees.
  • Encourage acknowledgment and acceptance of security responsibilities.
4. Regular Review & Continuous Improvement
  • Set a schedule for periodic policy reviews (at least annually).
  • Update policies based on business changes, new threats, or regulatory updates.
  • Conduct audits to ensure compliance and effectiveness.
5. Integrate Policies into the ISMS
  • Use it to develop more detailed security procedures.
  • Ensure policies align with other Annex A controls and broader risk management practices.
Key Differences: ISO 27001:2013 vs ISO 27001:2022
AspectISO 27001:2013ISO 27001:2022
Control StructureTwo separate controls: 5.1.1 & 5.1.2Merged into one control (5.1)
Implementation GuidanceLess prescriptiveMore detailed guidance for policy creation and alignment
Awareness & TrainingNot explicitly mentionedExplicitly requires policies to be part of training programmes
Attributes TableNot includedew attributes table for mapping policies to industry terms
Common Challenges & How to Overcome Them
  • Challenge: Employees don’t follow security policies.
  • Solution: Make policies practical and relevant to daily work. Use real-world examples in training.
  • Challenge: Policies are outdated or too generic.
  • Solution: Schedule annual reviews and update policies based on real threats and business changes.
  • Challenge: Policies are written in technical jargon.
  • Solution: Use plain language that all employees can understand.
  • Challenge: Lack of leadership buy-in.
  • Solution: Show how weak security affects business objectives—costs of breaches, loss of client trust, and legal penalties.
Final Recommendations
  • Make security policies living documents—review, refine, and update regularly.
  • Use policy training and awareness to create a security-conscious workforce.
  • Ensure policies are accessible, relevant, and easy to understand.
  • Keep policies aligned with business strategy and regulatory requirements.
  • Engage leadership in driving security culture from the top down.

The Annex Control Table

ISO 27001:2022 Organisational Controls
ISO 27001:2022 Technological Controls