Join our Newsletter — 33% off our NHI Course
Home› FAQ› Governance, Ownership & Risk› How should organisations implement segregation of duties across…
Governance, Ownership & Risk

How should organisations implement segregation of duties across access, change, and data management workflows?

← Back to all FAQ
By NHI Mgmt Group Editorial Team Updated November 5, 2026 Domain: Governance, Ownership & Risk

Start by separating initiation, approval, execution, and review across critical processes. Access grants should be independent from system administration, change deployment should be separate from development and testing, and data changes should require approval from an owner or reviewer. The goal is to ensure no single person can carry a sensitive action from start to finish without oversight.

How to design segregation of duties so it works across workflows

Segregation of duties only works when it is designed around the actual workflow, not just around job titles. The practical pattern is to separate request, approval, execution, and review so the same person cannot both authorise a sensitive action and complete it. That applies across access, change, and data workflows, with the exact control points tailored to the risk in each process.

For access workflows, the key control question is whether the approver has enough independence to challenge the request. For change workflows, the main issue is whether the person shipping the change can also authorise, test, or promote it without challenge. For data workflows, the control should focus on owner approval, review of sensitivity, and evidence that the change was legitimate and traceable.

Good SoD design is usually a combination of role design, workflow routing, and detective checks. The strongest implementations do not rely on one policy statement; they create separate paths for requestors, approvers, operators, and reviewers, then enforce those paths in the system where the work happens. NHI Management Group’s Segregation of Duties (SoD) Guide is useful when you need to move from principle to rulesets, conflicts, and compensating controls.

Where SoD breaks down in access, change, and data control

Most SoD failures come from combining too many powers in one workflow rather than one obvious policy breach. Access approvals can become rubber-stamped when the approver is functionally the same person as the requester. Change control fails when developers can also approve their own deployments or bypass testing in an emergency without later review. Data changes are risky when owners are absent and administrators can alter records without a second set of eyes.

SoD also weakens when the organisation treats exceptions as temporary but never retires them. Emergency access, break-glass privileges, and special deployment paths are legitimate, but they need tighter logging, time limits, and post-event review. Without that, the exception path becomes the real operating model. NHI Management Group’s Change Management Policy Template shows how approval, segregation, and emergency handling fit together in one operating process.

For data workflows, the failure mode is often ownership ambiguity. When nobody clearly owns a dataset or business record, technical teams end up approving changes they do not understand, or they create broad access so the process can keep moving. That is why owner review, sensitivity classification, and effective access checks need to be part of the workflow rather than separate paperwork. NHI Management Group’s Data Access Governance Guide is relevant where the workflow must show who can access sensitive data and why.

How to implement SoD rules without blocking the business

Start by defining the few workflows where SoD matters most: privileged access, production change, financial or master-data change, and high-impact data access. Then assign distinct roles for initiation, approval, execution, and review, and make the system enforce those separations wherever possible. If a workflow cannot be fully separated, document the compensating control and make the review independent, timely, and auditable.

Use policy checks where they have a real chance of being enforced, not just as after-the-fact reporting. For example, request tooling should prevent a requestor from being their own approver, deployment tooling should block promotion by the same user who built the change when risk is high, and data platforms should require owner sign-off for sensitive access or schema-altering changes. The goal is not bureaucracy, it is to stop one person carrying a sensitive action from start to finish unchecked.

Where SoD spans identity and privilege, combine the process rule with access design. A person who can request, approve, and execute privileged access has already defeated the control even if each step was formally logged. NHI Management Group’s IAM and IGA Basics helps anchor those workflow decisions in provisioning, reviews, and entitlement governance.

Risk and Threat Considerations

Weak segregation of duties creates concentration risk: one account, one role, or one team can approve and perform actions that should be independently checked. That increases the chance of fraud, accidental misuse, unauthorised production change, and silent data alteration. It also makes detection harder, because the same person can create the record, execute the action, and explain it afterward.

Failure mechanism: An attacker or insider abuses a workflow where approval, execution, and review are not truly independent, then uses legitimate process steps to hide malicious or excessive activity.

Impact: The organisation can end up with unauthorised access, unreviewed production changes, altered records, or compromised evidence of who approved what, which weakens both operational integrity and incident investigation.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST SP 800-53 Rev 5 sets the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.

FrameworkControl / ReferenceRelevance
NIST SP 800-53 Rev 5AC-5 — Separation of DutiesDirectly addresses separating authorise, perform and review functions.
AC-6 — Least PrivilegeSoD depends on limiting who can combine request, approval and execution powers.
CM-3 — Configuration Change ControlChange workflow segregation requires controlled authorisation, testing and promotion of changes.
Recommendation — Enforce AC-5 so no single role can approve and execute sensitive access, change, or data actions. Apply AC-6 to keep privileged workflow capabilities narrowly scoped and independently reviewable. Use CM-3 to separate change authorisation from build, test and deployment execution.
ISO/IEC 27001:2022A.5.3 — Segregation of dutiesAnnex A explicitly requires duties to be separated to reduce fraud and error risk.
Recommendation — Design workflows so conflicting duties are separated and exceptions are formally controlled.

Practitioner Guidance

What to prioritise: Put the strictest SoD rules on workflows that can change production state, grant privileged access, or modify high-value data. Those are the places where one skipped review can create the largest blast radius.

What to verify: Check that the workflow really separates people or functions, not just form fields. If the same user can create, approve, and execute by switching roles in the same session, the control is weaker than it looks.

Common mistake: Treating emergency paths as a special case that does not need follow-up. If break-glass use is not reviewed quickly and consistently, it becomes a standing exception rather than a controlled exception.

Practitioner takeaway: The best SoD design is the one that makes independence structural, not optional, because the control only works when the process itself prevents self-approval and self-execution.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on November 5, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org