Applying Separation of Duties

Key Takeaways

  • An access-based separation of duties policy compares two lists of conflicting access items for a human identity.

  • Choose the policy response for a conflicting new request and check the tenant-wide block setting.

  • Use policy runs and violation records to find existing conflicting access, then verify the actual grant origins.

  • A mitigating control records how a violation is addressed. Verify removal separately when the corrective action is revocation.

Last updated: November 2026

Define conflicting capabilities

Separation of duties (SoD) limits the ability of a single person to perform conflicting duties. For example, a purchasing employee can maintain supplier banking details or release payments, but the business may decide a single person should never hold both capabilities. Translate the two duties into the access actually represented in the source model. Verify entitlement values, how each role or access profile obtains them, and which identities can exercise them. A label such as Finance Worker gives too little evidence to define a meaningful conflict.

In SailPoint’s access-based SoD policy, List A and List B hold the conflicting access items. Items can be entitlements, access profiles, or roles. A violation occurs when a human identity has access in both lists. The identity need only have an item on each side. Choose the item type that represents the policy, and test alternate paths that reach the same capability. Both lists need content. The documented maximum is 50 items per side.

Choose the response and scope

Open Admin > SoD Policies, create the policy and define ownership, level, grant conflict handling and the two lists. Designate an owner to manage the policy and identify who should address violations. Review the exact lists and enable the policy. In its Access Requests setting, Block submission cancels conflicting requests. Allow submission routes conflicts to configured approvers. The global switch Block all Identity Security Cloud access requests with SoD conflicts also cancels conflicting requests in Identity Security Cloud when enabled, regardless of individual policy settings. Check this setting when the local policy appears to allow the request but the request is blocked. Record the policy’s risk level and, separately, the effective request disposition. A risk classification expresses the severity of the policy. The request-control settings determine whether a conflicting request is canceled or routed for review.

Observed conditionAppropriate control or verification
User has one capability and requests a conflicting oneEvaluate both sides of the access policy and the effective request blocking setting
User already holds both sidesRun or schedule the policy and inspect Policy Violations
User has two items on the same side onlyThis policy’s two-sided conflict condition has not been met
A business exception is permittedRecord an appropriate mitigating control with context and expiration under the organization’s procedures
A conflicting grant is to be removedIdentify the effective assignment and verify actual revocation on the target

Work a payments conflict

Suppose List A contains Supplier Bank Edit. List B contains Payment Release and Emergency Payment Release. A worker who holds Supplier Bank Edit and requests Payment Release would meet the cross-list conflict if granted. With the tenant-wide block enabled, the conflicting request is canceled even if the individual policy allows submission. In a review-based setup without that global block or another blocking policy, the policy’s Allow submission setting routes the request to the reviewers. Confirm that the test recipient already holds the needed first-side access in SailPoint before interpreting the result. For a negative case, try the same item for a person who holds no List A item and verify this policy does not fire.

An old assignment could leave both capabilities in place even if new conflicting requests are blocked. Use Run Policy or its schedule to detect the existing combination. Review the violating items, identity and owner in Policy Violations. If an entitlement arrives through an assigned role, inspect that role and its assignment path before choosing remediation. A policy run provides detection evidence. It leaves actual access removal to the corrective process. If the business allows an exception, apply the appropriate mitigating control and record why and when to revisit it.

Confirm the outcome

Check the request and activity records for the expected cancellation or review, along with the target’s actual state. For an existing violation, record the original cross-list items and what corrective action was authorized. Compare current identity access and target membership after remediation. A certification can review existing access for continued need. The SoD policy and its prevention setting evaluate a defined conflict independently. Document both the preventive test and the result of monitoring for violations already present.

See SailPoint’s SoD policy definitions and settings, global request prevention, and violation mitigation.

Test Your Knowledge

An enabled SoD policy allows submission of conflicting requests. The tenant-wide switch to block all Identity Security Cloud requests with SoD conflicts is enabled. A worker requests an item that would conflict with their current access. What should happen?

A

It must reach the item owner because local allow always takes priority

B

The platform cancels the conflicting request under the global block

C

The account holding the existing access is deleted immediately

D

The request is granted and sent only to a future certification

Test Your Knowledge

An engineer discovers that an existing identity already holds entitlements in both lists of a newly enabled SoD policy. Which action provides evidence of the existing violation for remediation?

A

Create a Request Center segment for the identity

B

Submit a new request for one of the existing items

C

Raise the reminder frequency for pending approvals

D

Run or schedule the policy and review the violating items and their actual assignments

Sections you finish are checked off in the contents.