Join our Newsletter — 33% off our NHI Course
Home› FAQ› Governance, Ownership & Risk› What is the difference between segregation of duties…
Governance, Ownership & Risk

What is the difference between segregation of duties and policy-based access control in financial governance?

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

Segregation of duties prevents one person from holding conflicting permissions that could enable fraud or error. Policy-based access control assigns access according to business rules and job responsibilities. They work together but solve different problems. SoD blocks unsafe permission combinations, while policy-based access control decides who should receive access in the first place.

How SoD differs from policy-based access control

Segregation of duties and policy-based access control both shape who can do what, but they operate at different layers. SoD is a control against dangerous combinations of permissions, especially where one person could create, approve, and execute a harmful action. Policy-based access control is a decision model that grants or denies access based on rules, context, and business intent.

SoD is usually about preventing a single actor from accumulating power across steps in a process. Policy-based access control is usually about expressing the organisation’s access rules in a consistent way. In practice, SoD can be one of the business rules inside a policy model, but it is not the same thing as the policy model itself.

That difference matters in financial governance because one control is designed to stop fraud-enabling combinations, while the other is designed to make access decisions repeatable and aligned to role, context, or transaction rules. A good policy engine can enforce SoD constraints, but it can also enforce many other access rules that have nothing to do with duty separation.

Where each control sits in financial governance

SoD is strongest in processes with staged approval and execution, such as payments, journal entries, vendor setup, trading, refunds, or user provisioning. Its purpose is to make sure no single individual can both initiate and finalise a high-impact action without oversight. In finance, that helps reduce fraud risk, error risk, and the ability to conceal misuse.

Policy-based access control is broader. It can decide access from attributes such as department, role, transaction type, device, location, time, data sensitivity, or approval state. For a finance team, that means access can change with business context instead of relying only on static role assignment. If you want a deeper comparison of authorisation models, the Authorisation Models Guide is the relevant starting point.

Because policy-based access control is rule-driven, it can support fine-grained access decisions that SoD alone cannot express. SoD answers, “Should this person hold incompatible powers at the same time?” Policy-based access control answers, “Should this person get this access under these conditions?” The controls overlap, but the governance question is different.

Why the distinction matters for controls and auditability

Financial governance teams often fail when they treat access design and duty separation as the same control. That can leave either too much access granted up front, or a neat policy model that still permits conflicting powers. The better pattern is to model access rules first, then check whether any combination of those rules violates SoD constraints.

SoD also needs exception handling. Some finance functions cannot be fully separated in small teams, so compensating controls, monitoring, and periodic review become part of the design. Policy-based access control can make those exceptions more precise, but it does not remove the need to review them. If you need a practical reference for building those controls, the Segregation of Duties (SoD) Guide is the most directly aligned internal resource.

For organisations that want one governance pattern to anchor policy, review cadence, and revocation discipline, the Access Control Policy Template is a useful companion because it connects access rules to least privilege, reviews, and revocation expectations.

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 and CIS Controls v8 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.

FrameworkControl / ReferenceRelevance
NIST SP 800-53 Rev 5AC-6 — Least PrivilegeSoD and policy-based access control both support limiting excessive access in finance.
AC-2 — Account ManagementAccess assignment, review, and revocation underpin policy-based access governance and SoD enforcement.
AC-5 — Separation of DutiesSoD is directly a separation-of-duties control for preventing conflicting authority.
Recommendation — Apply AC-6 to restrict access to the minimum needed for each finance task. Use AC-2 to govern account creation, role assignment, review, and removal. Implement AC-5 to prevent a single user from holding conflicting privileges.
ISO/IEC 27001:2022A.5.15 — Access controlPolicy-based access control and SoD are both access-control governance mechanisms.
A.8.3 — Information access restrictionFinancial governance needs policy-driven access restrictions that enforce business rules and least privilege.
A.5.3 — Segregation of dutiesSoD is explicitly named in Annex A and fits finance control design.
Recommendation — Define access rules and exceptions under A.5.15 and review them regularly. Restrict access by business need and transaction sensitivity under A.8.3. Separate incompatible finance duties and document any compensating controls under A.5.3.
CIS Controls v8CIS-6 — Access Control ManagementCIS 6 covers account lifecycle, access restriction, and controlled authorization practices.
Recommendation — Use CIS-6 to manage access, review entitlements, and revoke conflicting privileges.

Practitioner Guidance

What to prioritise: Define SoD as a negative control over conflicting power, then define policy-based access control as the mechanism for granting access. If the two are mixed together in one policy without clear testing, teams often miss toxic combinations until audit or incident response.

What to verify: Check whether the policy model can express both allow rules and forbidden combinations. If it cannot, you will need a separate SoD ruleset or a compensating review process for high-risk workflows such as payment approval, vendor master changes, and emergency access.

Decision rule: If the issue is “who should receive access,” use policy-based access control. If the issue is “which combinations of access are unsafe,” treat it as SoD governance and test the full permission set, not just the individual entitlement.

Practitioner takeaway: The cleanest governance design uses policy-based access control to assign access and SoD to constrain risky combinations, because one controls eligibility while the other controls conflict.

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