Skip to content
In the news TRM Labs × Finray — audit-ready crypto transaction monitoring for banking
Finray

Glossary · Controls

What is segregation of duties?

Segregation of duties is the design rule that no single person or system should control every step of a sensitive process, such as authorising, recording and handling assets, so that one error or one bad actor cannot go through unchecked.

Updated · Abbreviation SoD

What is segregation of duties?

Segregation of duties is a design rule: split a sensitive process so that no single person controls it from start to finish. The person who can create a vendor should not also release payments to that vendor; the person who can change production software should not also approve their own change. It is also written as separation of duties, or SoD.

The point is structural. It does not assume anyone is dishonest. It assumes people make mistakes and that systems fail, and it arranges the work so that one slip needs a second slip, somewhere else, to cause harm.

What do control frameworks say?

The US Government Accountability Office’s internal control standard (the “Green Book”), which follows the COSO internal control approach, is direct about it. Management considers segregation of duties when designing control activities so that incompatible duties are segregated; where that is not practical, it designs alternative controls (para 10.21). Segregation helps prevent fraud, waste and abuse, and the standard names the need to separate authority, custody and accounting of operations. It also states that segregation addresses the risk of management override but cannot absolutely prevent it, since two or more employees may collude (para 10.22). For small teams, alternative controls are expected (para 10.23).

ISO/IEC 27001:2022 lists segregation of duties as Annex A control 5.3; an organisation records in its Statement of Applicability whether and why each Annex A control applies. In EU financial regulation, DORA Article 9(4) expects access to be limited to what legitimate, approved activities need (point c) and changes to software and systems to be recorded, tested, assessed, approved, implemented and verified in a controlled manner (point e). The EBA’s guidelines on ICT and security risk management once covered similar ground for credit institutions, investment firms and payment service providers. Since DORA, their amended form (applicable from 20 May 2025) keeps only rules for payment service providers on relationship management with payment service users. DORA does not reduce to a single “segregation” rule either; it describes outcomes that role separation helps to evidence.

Which duties should be separated?

ProcessConflicting dutiesTypical separation
PaymentsCreate beneficiary; approve payment; reconcile bankThree roles, or two plus independent review
AccountingDraft a journal entry; approve posting; administer the ledgerMaker and approver differ; admin cannot post
PayrollMaintain employee data; run payroll; approve paymentPreparer and approver differ
AccessRequest access; approve access; grant accessRequester differs from approver
Software changeWrite change; review; deploy to productionAuthor differs from reviewer and approver
Audit trailAct in the system; administer the logsLog administration outside the acting roles

What is a worked example?

Illustrative example with synthetic numbers. A small company processes about 60 supplier invoices a month. One bookkeeper registers invoices, approves them and prepares the payment file, and the owner uploads the file to the bank without opening it. A CHF 9,800 invoice from a fictitious supplier is registered, approved and paid by the same person.

A redesign without extra staff: the bookkeeper registers invoices and prepares payments; the budget owner approves each invoice; the owner releases the payment batch and checks the batch total against the approved list; and a monthly report of new suppliers and changed bank details goes to the owner. Duties are still not fully separated, since the bookkeeper also maintains suppliers, so the monthly report is the alternative control the guidance calls for. The residual risk is written down instead of hidden.

How does segregation of duties differ from the four-eyes principle?

Four-eyes is a per-action rule: this specific action needs a different approver. Segregation of duties is the wider design: which roles may exist together in one person’s hands at all. A role design that allows one user to hold both “maker” and “approver” rights can defeat a four-eyes rule through role accumulation, which is why role reviews belong with approval rules.

How is it enforced in software?

  • Role-based access with exclusions: the system refuses to grant conflicting roles together, or flags them for review.
  • Identity checks on approval: an approval by the same identity as the maker is rejected, ideally in the data layer so that other clients cannot bypass it.
  • Admin separation: database and platform administrators cannot post business transactions, and business users cannot alter the audit trail.
  • Periodic access review: conflicts that crept in are found and removed.
  • Evidence: who held which role when, and what they did, recorded in an append-only hash-chained journal or comparable log.

What changes with AI agents?

OWASP’s guidance on excessive agency lists three root causes: excessive functionality, excessive permissions and excessive autonomy. Its mitigations include minimal extensions, minimal permissions on downstream systems, human approval of high-impact actions, and complete mediation, where the downstream system checks authorisation instead of trusting the model.

Read as segregation of duties: give an agent the least rights needed, keep “propose” apart from “approve” and “post”, and do not let it hold rights to change its own permissions or the controls around it. An agent identity should appear in the audit trail as itself, so that actions stay attributable. Safe replays after a timeout also matter, see idempotency in payments.

What are the common failure modes?

  • Role accumulation: people change jobs and keep old rights.
  • Shared accounts: one login means one person, however many users.
  • Superuser convenience: an administrator role used for daily business work.
  • Paper separation: duties split in a policy but not in system permissions.
  • Untracked exceptions: small teams make exceptions without recording the compensating control.

What does Finray do today, and what is not yet there?

In Corebanq Accounting, postings and bills require a second person’s approval by default, and a maker cannot approve their own change; that rule is enforced in the database. Changing the default is itself an approved change. We do not claim that every change always needs four eyes. Journal, audit log and access log are append-only and hash-chained with a verification check, and each company’s data is isolated by row-level security. AI features are off by default, and AI proposals carry no posting authority.

This entry describes a general control design, not a certification of any customer’s role model; the customer defines its own roles and review cycle. Finray Technologies Ltd’s ISO/IEC 27001:2022 certificate is a company-level information security management certification, not a product certification; see how we build. Platforms: Corebanq Accounting and Corebanq.

Frequently asked questions

What is segregation of duties in simple terms?
It means splitting a sensitive process so that different people, or different systems with different rights, handle the conflicting steps. The person who requests a payment should not also approve it, and the person who administers the system should not also post in it.
Which duties usually conflict?
The classic split from internal control guidance separates authority to approve, custody of assets, and recording of transactions. In IT the equivalents are approving access, operating production systems, and developing or changing the software, plus administering logs separately from the people the logs describe.
What if the organisation is too small to separate every duty?
Internal control guidance expects management to design alternative control activities where full segregation is not practical, such as independent review of the work, limits on amounts, and logs reviewed by someone outside the process. The gap should be recorded as a known risk, not ignored.
Does segregation of duties prevent fraud completely?
No. It reduces the chance that one person can act alone, but collusion between two people can still defeat it. Detective controls such as reconciliation, review of exceptions and an audit trail remain necessary.
How does segregation of duties apply to AI agents?
An agent should be treated as a role with its own narrow rights, not as a superuser. An agent that drafts should not be able to approve, post or change its own permissions. Authorisation should be enforced by the downstream system, not by the model's own judgement.

Sources

Published · Updated · All terms

Certificate of Registration NQA · UKAS Management Systems
ISO/IEC 27001:2022 Certificate of Registration issued by NQA to Finray Technologies Ltd, certificate number 215646, valid 21 October 2025 to 21 October 2028
Search
Type to search across Finray, products, company, and journal.

    Press Esc to close · ↵ to open the highlighted result.

    Book a briefing Step 1 of 3

    Your details

    Who is requesting the briefing.