Skip to content

Investigate and resolve a separation-of-duties violation

A separation-of-duties (SoD) violation means one person holds two entitlements that a rule says must not be held together — for example create vendor and approve payment. Each rule is either WARN (the conflict is allowed but flagged, and can be excepted) or BLOCK (the conflict must be removed).

Violations live in the Security & Risk hub → SoD & Policy Engine → SoD tab (SoD & Policy Engine). Remediating and escalating need Compliance Officer, PAM Admin, Identity Admin or Super Admin. Deciding exception requests needs PAM Admin, Identity Admin or Super Admin.

A blocked separation-of-duties conflict — entering and approving the same vendor bills — with grant exception, escalate and remediate on the same row.

1. Find the violation

  1. Open the Violations tab. The number beside it is the count of open violations.

  2. Filter by status:

    Filter Meaning
    Unresolved Everything still needing action (the default)
    New Detected, nobody has acted yet
    Escalated Routed to your organisation’s SoD escalation role
    Queued One entitlement revoked in AtmanID; a revocation ticket is open for the target system
    Exception An exception has been requested or approved
    Resolved Closed
  3. Each row shows the Violation (rule), User, Conflict Pair, Severity and Age (days open). The conflict pair also shows how recently each connected application was synced, so you know whether the data is current.

Violations come from the scheduled SoD scan, from the check that runs when someone requests access, and from the scan that runs when a person changes role (a JML mover event).

2. Read the conflict

Expand the row (the chevron at the end). You see:

  • Iris’s read of the violation, with a recommendation, at the top.
  • Detection — how and when it was found.
  • Conflicting Entitlements — both entitlements and the application each belongs to.
  • Resolution — what has been done so far, or how long it has been unresolved.

Before deciding, check which of the two entitlements the person actually uses in their job; that is usually the one to keep.

3. Decide

Remediate (any rule). Select Remediate. In Remediate SoD Violation, choose Revoke for one of the two entitlements, enter a Justification (at least 20 characters) and select Confirm Revocation. AtmanID removes the entitlement from the person’s record at once and opens a high-priority revocation ticket so it is removed in the target system too; the violation moves to Queued, and to Resolved once the ticket closes. Any open remediation task for the violation is closed automatically.

Request an exception (WARN rules only). Select Exception on the row, or Request Exception inside the remediation dialog. Enter a Business Justification (required), any Compensating Controls, and Expiry (days) — max 90 (the default is 30; your organisation may set a lower ceiling under Platform Config → Governance Settings → SoD tab). Select Submit Exception Request.

BLOCK-rule violations cannot be excepted — revoking one side is the only resolution.

Escalate. Escalate routes the violation to your organisation’s SoD escalation role and notifies them.

4. Approve or deny the exception

Open the Exception Inbox tab. For a pending request, select Approve, or Deny, add an optional note and select Confirm Deny. You cannot approve an exception you requested yourself. An approved exception can be ended early with Revoke → Confirm Revoke.

Exceptions are never permanent. When one expires, the violation re-opens automatically. Requests left undecided past the decision deadline are denied automatically.

Audit trail

Event Written when
SOD_VIOLATION_REMEDIATED An entitlement is revoked to resolve the violation
SOD_VIOLATION_ESCALATED The violation is escalated
SOD_EXCEPTION_REQUESTED An exception is requested
SOD_EXCEPTION_APPROVED, SOD_EXCEPTION_DENIED An approver decides
SOD_EXCEPTION_REVOKED An approved exception is ended early
SOD_EXCEPTION_EXPIRED, SOD_EXCEPTION_AUTO_DENIED The system expires or auto-denies an exception

Search for these on Audit & Reports (Security & Risk → Audit & Forensics). Every event name the platform writes is listed in the audit event reference.

Not available today: the remediation dialog has no “accept the risk” option, and exceptions cannot be granted for BLOCK rules or extended — request a new exception when one expires.

© AtmanID · Privacy