Skip to content

Configure Segregation-of-Duties rules

SoD rules are on Security & Risk → SoD & Policy Engine (page SoD & Policy Engine), on the Rule Builder tab. Identity Admins, PAM Admins, Tenant Owners and Super Admins see the New Rule and Run Scan buttons.

What a rule is

A rule names two entitlements that one person must not hold together, such as “Create vendor” and “Approve payment”. Rules are always between entitlements, never between roles, applications or whole permission sets. When AtmanID checks a person, an entitlement they hold through a role counts as held. You can have only one rule for each pair of entitlements. The entitlements must already be in the catalog, which you fill by onboarding the application first.

Create a rule

  1. On the Rule Builder tab, click New Rule.
  2. Fill in Create SoD Rule:
Field Notes
Rule Name (required) For example “Accounts Payable vs Vendor Setup”
Description Why the combination is a control risk
Entitlement A, Entitlement B (required) Search the catalog. A and B must be different.
Enforcement Action Block or Warn (the default). See below.
Risk Level Critical, High (the default) or Medium
Financial Exposure (optional) The dollar exposure if the combination is abused. Leave it blank to use your tier’s default.
Compliance Tags Free text, with quick-add chips: SOX, HIPAA, PCI-DSS, GDPR, ISO-27001, NIST, SOC2
  1. Click Create Rule. New rules are active straight away.

To change a rule, click Edit on its row. You can change everything except the entitlement pair. For a different pair, create a new rule. Disable and Enable turn a rule off and on; rules are never deleted. Export and Import move rule sets as JSON, up to 100 rules per import.

Block and Warn, at request time

When someone asks for access, the request form checks it straight away. On submit and at final approval, AtmanID checks again against the access the person already holds:

Action What happens
Block The requester sees “SoD Conflict — Request Blocked” and cannot submit. An approver cannot approve it either. A blocked conflict can never be given an exception.
Warn The requester sees “SoD Conflict Detected” and can still submit. The request goes ahead, and AtmanID records an open violation for review. A Warn does not hold the request until an exception is approved.

Grants made directly, rather than through a request, are not blocked. They are checked only when Run SoD detection on every access provisioning event is turned on. That option is off by default and is under Platform Config → Governance Settings → SoD.

Detection after the fact

A scan checks everyone’s current access against every active rule. It runs every day at 03:00 UTC, or now if you click Run Scan. Each conflict it finds appears on the Violations tab with one of these statuses: New, Escalated, Queued (for remediation), Exception or Resolved. Each row has these actions:

  • Remediate: revoke one of the two entitlements. You need a justification of at least 20 characters.
  • Escalate: send the violation to your organisation’s SoD escalation role.
  • Exception: offered only for Warn rules.

Exceptions

  1. On a violation, click Exception.
  2. Enter a Business Justification, any Compensating Controls, and an Expiry (days) — max 90.
  3. Click Submit Exception Request.

A PAM Admin, Identity Admin, Tenant Owner or Super Admin decides the request in the Exception Inbox. Nobody can approve their own request. Once approved, the violation shows Exception and the conflict stops being flagged until the exception expires. Revoke ends an exception early and reopens the violation. Requests left pending for 7 days are denied automatically. Under Platform Config → Governance Settings → SoD you can set the Exception Duration Cap and Minimum Justification Length.

Test a rule

On the What-If Simulator tab, pick a User and a Hypothetical entitlement to grant, then click Run simulation. The result shows whether the grant would be blocked, warned or allowed. Nothing is granted or recorded. The simulator checks saved, active rules only, so save the rule first. A rule cannot be previewed in draft.

Audit events

SOD_RULE_CREATED, SOD_RULE_UPDATED, SOD_RULE_DEACTIVATED, SOD_SCAN_COMPLETED, ACCESS_REQUEST_SOD_BLOCKED, ACCESS_REQUEST_SOD_WARNING, APPROVAL_SOD_BLOCKED, SOD_VIOLATION_REMEDIATED, SOD_EXCEPTION_REQUESTED, SOD_EXCEPTION_APPROVED, SOD_EXCEPTION_DENIED and SOD_EXCEPTION_REVOKED. Find them in the audit trail.

© AtmanID · Privacy