Segregation of duties, or in Italian separazione o segregazione dei compiti, is the principle that no one should control an entire operation alone, handling every stage from authorisation through to verification. The idea, then, is to divide a critical process among several people, so that an error or abuse must pass through at least two pairs of hands before it takes effect.
This principle originates in internal control and information security, but it applies to every decision that, taken by one person alone, exposes the organisation: a payment, an access right, a public message, a supplier. In this article we will explore the details together.
Segregation of duties in 4 key points
Who authorises, who executes and who verifies cannot be the same person
- 1
Segregation of duties prevents the same person from authorising, executing and verifying the same transaction.
- 2
It is achieved by separating incompatible roles and, where that is not possible, through compensating controls.
- 3
Against fraud it carries as much weight as the controls themselves: according to the ACFE, more than half of the cases analysed stem from absent or overridden controls.
- 4
The principle is not just about accounting: it applies to budgets, messages, suppliers and content.
Segregation of duties: meaning and definition
The meaning of this enigmatic concept lies in the word itself, segregate, which means to keep apart. The sharpest technical definition comes from information security: no user should have sufficient privileges to misuse the system alone; the person who authorises a payment should not also be the one who prepares it (NIST, SP 800-192). The reason is simple: a check performed by the same person who carried out the operation is a check on oneself, so an error or an abuse remains invisible until that person reports it.
In practice, four functions are distinguished, which within the same process should sit with different people: authorising, executing, recording, verifying. The table below explains them in more detail.
The four functions to keep separate
In the same process, different people.
| Function | Question it answers | If it coincides with another |
|---|---|---|
| Authorise | Can the transaction be carried out? | Whoever decides approves themselves: no one stops them |
| Execute | Who carries it out? | Whoever executes authorises themselves: abuse goes through without a second look |
| Record | Who keeps a record of it? | Whoever executes deletes or alters the trail: the transaction becomes invisible |
| Verify | Who checks that it went as it should? | Whoever executes checks their own work: the control becomes a formality |
How segregation of duties works
NIST distinguishes two ways of enforcing it. The static approach defines conflicting roles upfront, that is, roles the same person cannot hold. The dynamic approach checks the constraint at the moment of the transaction: the classic example is the two-person rule, in which the second signature must come from a different user than the first (NIST, SP 800-192, citing Sandhu and Samarati, 1994).
Static and dynamic separation
Two ways of enforcing the same principle.
| Static | Dynamics | |
|---|---|---|
| When it applies | Upstream: conflicting roles are defined | At the point of action: the constraint is checked when the operation is carried out |
| How it works | Roles the same person cannot hold | The second step must be performed by a different person from the first |
| Example (NIST) | The person who authorises a payment is not the person who prepares it | Two-person rule |
| Risk it addresses | Accumulation of incompatible roles | Approval of a transaction initiated by the same person |
Source: NIST, SP 800-192 (CSRC glossary, Separation of Duty), citing Sandhu and Samarati, 1994. Summary by Bliss.
The choice between the two depends on the transaction. Conflicting roles are defined once and always apply. Dynamic control is needed where the conflict only arises in the act itself, for example when the same person could approve a transaction they initiated.
Why it matters: the fraud data
The ACFE (Association of Certified Fraud Examiners) analysed 2,402 cases of occupational fraud in 143 countries and reports a median loss of $104,000 per case. In 33% of cases the primary weakness was a lack of internal controls; in a further 19% controls existed but were overridden. Together they account for more than half of cases (ACFE, Occupational Fraud 2026: A Report to the Nations).
Where controls give way
Primary internal control weakness in the fraud cases analysed by the ACFE (share of cases).
Source: ACFE, Occupational Fraud 2026: A Report to the Nations (fig. 37). The report does not name segregation of duties. The bar scale runs from 0 to 40%.
separation guards against both weaknesses, because controls are missing when one person covers the whole process, and controls are more easily bypassed when the person checking is the same as the person executing.
Is segregation of duties mandatory?
It depends on the context. Legislative Decree 231/2001 does not use the expression, but Article 6(2) requires organisational models to provide protocols for planning how the entity’s decisions are formed and implemented in relation to the offences to be prevented, and methods for managing financial resources capable of preventing them. In practice, and this is our reading, segregation of duties is one of the tools through which these protocols are put into effect. In information security standards it appears by name, for example in control 5.3 of ISO/IEC 27001:2022.
The Bliss angle: segregation of duties extends beyond accounting
Segregation of duties is almost always described as an accounting or IT control. We read it as a governance principle: an important decision holds when the person who proposes it, approves it, executes it and verifies it are distinct roles and someone is accountable for it. A company’s risk points are not only payments. They are a campaign budget, a message that commits the brand, the choice of a supplier, the publication of content, the output of an artificial intelligence system.
Separation beyond accounting
Five areas in which whoever proposes, whoever approves and whoever verifies should be separate roles.
| Scope | Whoever proposes | Who approves | Who verifies | If the roles coincide |
|---|---|---|---|---|
| Campaign budget | Who runs the campaign | Whoever is accountable for the budget | Someone who did not manage the spending | Spending inconsistent with objectives and undetected |
| Messages that commit the brand | Whoever writes | Who is accountable for the brand | Whoever checks the claims | Promises the company cannot keep |
| Supplier selection | Who needs it | Whoever is accountable for the budget | Someone with no relationship with the supplier | Choices based on relationships, not criteria |
| Publishing content | Who produces it | The approver | The specialist auditor | Unchecked online content |
| AI-generated content | Who uses the tool | Who is accountable for its use | Who reviews the outcome | Errors nobody catches before publication |
Bliss classification: the roles shown are generic and should be adapted to the organisation.
None of these lines requires an additional function. It requires roles to be written down, exceptions to have an approval level and verification to rest with someone who did not execute. This is the work we do through Brand Governance: when all four positions coincide in a single person, the brand no longer has a control; it has trust.
How segregation of duties is applied: the conflict matrix
The tool for applying the principle is the conflict matrix, also known as the SoD matrix: a table that cross-references activities and roles to flag combinations the same person should not hold. A six-step sequence, in our own summary:
- The critical processes are listed: those where an error or an abuse would cost the most.
- Each process is broken down into its constituent activities, each of which maps to one of the four functions.
- Activities are assigned to people as things stand today, not as the organisation chart says: what counts are actual permissions and actual habits.
- Identify pairs of conflicting functions assigned to the same person.
- Separate the roles or, where this is not possible, introduce a compensating control.
- The matrix is reviewed at fixed intervals and at every change of role, because permissions accumulate.
The step most often skipped is the third. An organisation that reasons from its organisation chart sees roles as they should be, and misses the person who has accumulated additional access rights and delegated authority over time.
Small organisations and the limits of the principle
In small organisations the same person often covers several functions. That is no reason to give up: responsibility must be made explicit, so that it does not depend on the team’s memory, and a compensating control must be introduced, such as approval by another person or a periodic sample review. The same applies to content, and the content governance guide notes that one person can hold several roles provided responsibility is written down.
The principle has two limits. The first is collusion: two people acting in concert can circumvent the separation, so the principle reduces risk without eliminating it. The second is cost: every additional step slows things down, and an organisation that separates everything ends up circumventing the rules. It makes sense to separate where the potential damage is high and to adopt a lighter workflow where it is low.
Domande frequenti
What is segregation of duties?
It is the principle whereby no single person controls an entire critical operation alone. The functions of authorisation, execution, recording and verification are assigned to different people, so that an error or an abuse has to pass through more than one pair of hands. It originates in internal control and information security, and extends to every high-risk decision.
How is segregation of duties translated into Italian?
The translations in use are separazione dei compiti, segregazione dei compiti and segregazione delle funzioni, often interchangeably. Professional texts also use the English expression or the acronym SoD. The meaning is the same: keeping apart functions that, if combined in one person, would allow a process to be abused without anyone noticing.
What is segregation of duties for?
It serves to reduce the risk of error and abuse: if the same person authorises, executes and verifies, no one can spot a problem. Dividing functions forces a second look, makes accountability visible and limits the damage any single person can cause. On its own it is not enough to prevent fraud, but it is one of the simplest controls.
Which functions should be separated?
It depends on the process. We identify four functions: authorising, executing, recording and verifying. Sources use different lists, often with three functions, but the criterion is the same: the person who carries out an operation must be neither the one who authorises it nor the one who checks it. Start with the processes where an error would cost the most.
What is an SoD matrix?
It is a table that cross-references activities and roles to identify incompatible combinations, that is, activities the same person should not perform together. It is built on actual permissions and working habits, not on the organisation chart. For each conflict, a decision is made whether to separate the roles or introduce a compensating control, and the matrix is reviewed at every change of role.
Is segregation of duties mandatory?
There is no single rule that mandates it by this name in every context. Legislative Decree 231/2001 requires organisational models with protocols governing decisions and the management of financial resources, and the principle is a standard tool for implementing them. It appears by name in information security standards such as ISO/IEC 27001, control 5.3.
What violates segregation of duties?
It is breached by any arrangement in which the same person can authorise and execute, or execute and verify, the same operation: someone who approves payments and also prepares them, someone who manages an access right and also checks its use. Often the breach is decided by no one: it arises from permissions and delegations accumulating over time.
What is segregation of duties in IT and SAP?
In information systems, separation concerns permissions: the same user is prevented from holding conflicting profiles, for example creating a supplier and approving its payments. In enterprise management systems such as SAP, conflicts are sought among authorisation profiles, and identity and access management (IAM) applies static and dynamic rules.
How does it differ from internal control?
Internal control is the overall system through which an organisation oversees its risks: rules, roles, checks, information flows. Segregation of duties is one of its control activities, and among the most basic. A system can have segregation and still not be effective, if written roles, periodic checks and someone accountable for the results are missing.
How does it apply in a small company?
When one person has to cover several functions, accountability is made explicit and a compensating control is introduced: approval by another person, a periodic sample review, a decision log. At the very least, verification must be kept separate from execution. The processes with the highest potential damage are separated first.
Who is responsible for segregation of duties?
Those who govern the organisation: the board and senior management define roles and approval levels. The control function checks that they work, but cannot take the place of those who decide. If no one is accountable for how roles are arranged, segregation becomes a document that does not govern behaviour.
Fonti e riferimenti
- NIST, Computer Security Resource Center, Glossary: Separation of Duty (SOD), da NIST SP 800-192
- ACFE, Occupational Fraud 2026: A Report to the Nations
- D.Lgs. 8 giugno 2001, n. 231, art. 6
- ISO/IEC, ISO/IEC 27001:2022, Information security management systems
- Bliss, Content governance: come governare i contenuti aziendali
- Bliss, Key person risk: cos’è e cosa causa
- Bliss, Brand Governance (pagina servizio)

