Appearance
Segregation of duties
Also known as
- SoD
- SOD violations
- toxic combination
- access risk
- conflict
- conflicting permissions
- incompatible duties
- access review
- four-eyes
- run analysis
The segregation of duties (SoD) screen lists every role and user that holds two permissions that should not be in the same hands, such as creating vendors and paying them. The compliance team reviews each conflict and mitigates it, accepts it or fixes the roles.
The tabs at the top lead to the four SoD screens: Violations, Rule sets, Mitigating controls and Analysis and simulation.
Review the violations
- Open ComplianceSegregation of duties. Violations are sorted by risk, critical first.
- Filter by Status, Risk, Subject (Users or Roles) or Rule set.
- Select a row to see the conflict and the roles that grant each permission. See Violation detail.
| Column | What it shows |
|---|---|
| Rule | The rule code and name, such as P2P-01 Maintain vendors and pay them. |
| Subject | The user or role that holds both permissions. |
| Conflicting permissions | Permission A ⟷ permission B. |
| Through roles | The roles that grant them. |
| Risk | Low, Medium, High or Critical, from the rule. |
| Enforcement | Warn or Block, from the rule set. |
| Detected | When the conflict was first found. |
| Status | Open, Mitigated, Accepted or Resolved. |
Run the analysis
The analysis checks every role and user against the active rules. It runs every night; run it yourself after you change roles or rules.
- Select Run analysis.
- You see a summary such as "Analysis done: 7 open, 1 new, 2 resolved". Conflicts that no longer exist move to Resolved.
Past runs are listed on Analysis and simulation.
How enforcement works
Each rule set has an enforcement mode that applies when an administrator assigns roles to a user in Users:
| Mode | When a user's new roles break a rule |
|---|---|
| Off | Nothing happens at assignment; the nightly analysis still lists the conflict. |
| Warn | The assignment is saved, logged in the Assignment log and holders of Permission: compliance.sod.manage are notified. |
| Block | The assignment is refused with "Segregation of duties: this combination of roles is blocked by …", unless a mitigating control covers it. |
The role editor in Roles shows the same rules while you tick permissions. The Account admin role is left out of SoD checks while Exclude the account admin role is on in Compliance settings.
Differences by role
- Permission:
compliance.sod.viewshows the SoD screens. - Permission:
compliance.sod.analyseshows Run analysis. - Permission:
compliance.sod.managelets you edit rule sets, record mitigations and accept violations.
