Insider Sabotage: Segregation-of-Duties Risk Graph

Org Parameters

Employees 24

Avg. permission grants / employee 3.5

Ready. Grant permissions, then try an insider attempt.

Live Readouts

SoD risk score (toxic holders)0

Min. colluders to sabotage1

Total permission grants0

How it works

This models separation / segregation of duties (SoD) — the standard defensive control against a single insider sabotaging a system alone. Ten sensitive permissions form five toxic pairs, each a request/approval split:

Initiate Wire Transfer  ↔  Approve Wire Transfer
Grant System Access     ↔  Approve Access Review
Deploy Code to Prod     ↔  Approve Code Deploy
Export Customer Data    ↔  Approve Data Export
Delete Audit Logs       ↔  Modify Backup Retention

Each employee is granted permissions at random with probability p = avg/10. With enforcement OFF, nothing stops one account from acquiring both halves of a pair — a single compromised or malicious insider can act and cover their tracks alone. With enforcement ON, the policy layer blocks the second grant of any pair a person already holds, so:

SoD risk score R = Σ_employees 1[holds both permissions of any toxic pair]
Enforcement ON  →  R = 0 for every pair, every employee
Enforcement OFF →  R grows with headcount × avg. grants

Forcing R to zero doesn't remove risk, it raises the minimum collusion size from 1 insider to 2 — an attacker now needs a second, independently-privileged account to complete the same sabotage. "Simulate Insider Attempt" launches a probe from the highest-risk (or, if none, highest-privilege) node toward the system core: red means the account alone reached it (breach), green means it stalled — the action needed an approval from someone else who wasn't compromised.

Real-world relevance: this is the model behind SOX financial controls, PAM policy engines, and code-review "two-person rule" gates — the graph is a live audit report of who could sabotage what, alone.

Employee — clean Employee — toxic pair held Permission node System core

⚠ Couldn't load the 3D engineThree.js failed to load from the CDN. Check your connection and reload.