Join our Newsletter — 33% off our NHI Course
Home› FAQ› Cyber Security› What is the difference between segregation of duties…
Cyber Security

What is the difference between segregation of duties and compensating controls in a small business?

← Back to all FAQ
By NHI Mgmt Group Editorial Team Updated October 31, 2026 Domain: Cyber Security

Segregation of duties is the ideal control design, where different people perform incompatible tasks such as approval, custody, and reconciliation. Compensating controls are alternative safeguards used when staffing is too limited for full separation. They rely on oversight, review, approval, and monitoring to reduce risk, but they do not fully replace the assurance provided by a clean division of responsibilities.

How segregation of duties and compensating controls differ in a small business

Segregation of duties is a control design principle: no single person should control incompatible steps such as approving, recording, and reconciling the same transaction. In a small business, that ideal is often hard to achieve because staffing is limited. Compensating controls are the practical fallback, using review, monitoring, and approval to reduce risk when perfect separation is not possible.

SoD is stronger because it removes the opportunity for one person to both cause and conceal an error or fraud. Compensating controls accept that the risk cannot be eliminated in the same way, so they try to detect misuse faster and make abuse harder to hide. That makes them useful, but inherently less protective than true separation.

The difference matters most when deciding whether a control gap is a design choice or a temporary exception. If the business can split duties, SoD should be the default. If it cannot, the compensating control must be specific, repeatable, and evidence-based, not just a promise that someone will “keep an eye on it.”

What small businesses should expect from each control

In a small team, SoD often has to be adapted rather than applied in a textbook way. That may mean the same person can prepare a payment but cannot approve it, or can create a vendor but cannot release funds. The goal is to avoid a single point of unchecked authority over money, access, or sensitive records.

Compensating controls are the next-best safeguard when that clean split is impossible. They usually include a second-person review, manager approval, exception reporting, periodic reconciliation, or independent monitoring. The control only works if the reviewer has enough context and authority to stop or question the action, not merely sign off after the fact.

For a practical overview of control design, NHI Management Group’s Security Control Types Guide explains why compensating controls sit in a different category from preventive separation. The key idea is that they reduce exposure, but they do not create the same assurance as structural separation.

Why the distinction matters for fraud, errors, and audit evidence

The control choice changes the residual risk profile. SoD is mainly about preventing conflict, while compensating controls are about narrowing the window for undetected misuse. That distinction is important for cash handling, payment approval, journal entries, vendor master changes, refunds, and privileged system access, where one unchecked role can create both error and concealment risk.

Small businesses also need to think about evidence. A compensating control is only credible if it leaves a trail: who reviewed, what was reviewed, when it was reviewed, and what was escalated. Without that record, the control may exist in theory but be hard to defend during an audit, a dispute, or an internal investigation.

If the organisation is trying to document why full separation is not possible, the Security Exceptions and Risk Acceptance Guide is useful because it frames compensating controls as a bounded exception rather than an informal workaround. That mindset helps keep the control tied to ownership, expiry, and review.

What to do when staffing limits make full separation impossible

When a small business cannot fully separate duties, the safest approach is to narrow the exception as much as possible. Keep the highest-risk step separate first, usually approval or release, then add independent review of the completed action. If the same person must perform multiple steps, increase oversight frequency and require evidence that the review happened.

It also helps to define where compensating controls are not acceptable. If a task can materially move money, alter records, or grant access, the business should treat it as a higher-risk exception and use stronger oversight than for routine admin work. A temporary workaround that becomes permanent is where weak controls usually turn into control failure.

For small teams, the most useful control pattern is usually a mix of role restriction, approval, and post-action review rather than relying on one person to “be careful.” NHI Management Group’s Small Business Cybersecurity Basics Guide is a good starting point for the wider operating context, while the control decision itself should remain focused on reducing the chance of unchecked action.

Risk and Threat Considerations

When duties are combined, the main risk is not just human error, it is undetected misuse. A person who can create, approve, and reconcile the same activity can hide fraud, suppress evidence, or make a mistake harder to spot. Compensating controls reduce that exposure, but they depend on the reviewer being independent enough, attentive enough, and frequent enough to catch the problem before damage spreads.

Failure mechanism: The same actor retains enough end-to-end authority to initiate a harmful action and then validate it as if it were legitimate, which weakens both prevention and detection.

Impact: Financial loss, inaccurate records, delayed detection, and weaker accountability, especially where a small business has few people, limited oversight, and a high reliance on trust.

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 compensating controls both reduce excess authority in small business processes.
AU-6 — Audit Review, Analysis, and ReportingCompensating controls rely on review and monitoring to detect misuse or error.
Recommendation — Limit each role to the minimum authority needed and separate incompatible duties where possible. Review audit records and exceptions so compensating controls can surface misuse quickly.
ISO/IEC 27001:2022A.5.3 — Segregation of dutiesThe question is directly about SoD as a control design principle.
A.5.28 — Collection of evidenceCompensating controls need traceable evidence that reviews and approvals occurred.
Recommendation — Separate incompatible tasks so one person cannot both perform and conceal a harmful action. Retain approval and review evidence that proves the compensating control operated.
CIS Controls v8CIS-6 — Access Control ManagementDuty separation and review are core access-governance safeguards in small businesses.
Recommendation — Assign and review access so no single user accumulates unchecked authority over critical actions.

Practitioner Guidance

What to verify: Verify that any compensating control is independently observable, produces evidence, and is performed by someone who can actually challenge the underlying action. A review that always happens after the fact, without a stop mechanism or follow-up, is usually too weak to justify the exception.

Decision rule: If the task can directly move money, change ownership, or grant access, prefer SoD wherever staffing allows. If you must use compensating controls, make the exception time-bound and review it as soon as staffing or process changes make proper separation possible.

Practitioner takeaway: Small businesses should treat compensating controls as a controlled fallback, not a substitute for good control design. The closer a process gets to money, access, or record integrity, the less comfortable you should be with informal review and the more important documented, independent oversight becomes.

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 October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org