A.5 Organizational controls

A.5.3 Segregation of duties

Not mandatory by default – decided in your SoA

What it means in plain language

Split conflicting tasks between different people so that no single person can misuse a process unnoticed (e.g. request and approve their own access).

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

Segregation of duties reduces the chance that one person can create, approve, and conceal a risky action end to end. Teams should split or compensate for conflicts in access, payments, code change, and privileged operations using the Access Control Policy and Information Security Roles & Responsibilities. In smaller teams, the focus is on logging, independent review, and management oversight rather than rigid staffing assumptions.

Common auditor findings to check for

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

  • A requestor can approve their own access or exception, leaving no independent challenge, no traceable reviewer, and no documented compensating control.
  • Privileged changes are deployed by the same person who authored them, with no second review, no change ticket evidence, and no post-implementation verification.
  • A small team relies on informal trust, but there is no periodic management review of sensitive actions, no exception register, and no conflict mapping.

How you can implement it

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

  • Map conflicting duties for access, purchasing, payments, source code, backups, and privileged administration. Assign primary owner, approver, executor, and reviewer in the roles template, then define where one person cannot occupy multiple steps without a recorded compensating control.
  • For recurring exceptions, require a named manager to approve the risk, a reviewer independent of the task, and a time-bound expiry. Keep the exception linked to the Access Control Policy so reviewers can see why the deviation exists and when it must be removed.
  • Use practical checks such as dual approval tickets, merge request reviews, four-eyes release sign-off, and admin session logs. In very small teams, pair those with weekly management sampling of sensitive actions and a documented rationale for every overlap.
  • Review segregation conflicts whenever roles change, systems are added, or incidents reveal abuse paths. Record the review outcome, any compensating monitoring, and the date for revalidation so the control remains aligned with operational reality rather than a static org chart.

What an auditor will ask to see

  • A duty-separation matrix showing conflicting tasks, named approvers, compensating controls, and approved exceptions with expiry dates.
  • Change tickets, pull requests, or access requests showing independent approval and execution by different named roles.
  • Management review notes or exception register entries confirming periodic sampling of high-risk actions and unresolved conflicts.

Baseline documents in the kit

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

Connect this work to your ISMS

Review the dependencies with A.5.4 — Management responsibilities and A.8.2 — Privileged access rights. Keep the ownership and evidence consistent across these activities.

Required information and the kit’s 19-document core 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.