Join our Newsletter — 33% off our NHI Course

Why does cross-application SoD drift cause risky access patterns?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20230
Topic starter  

TL;DR: Cross-application segregation of duties is harder to enforce consistently across ERP and business systems, according to Delinea. SoD programs need live detection, remediation, and evidence that holds up across business workflows.

Editorial analysis by NHI Mgmt Group, based on content published by Delinea: “Top Segregation of Duties (SoD) solutions to know about in 2026”.

Key questions

Q: When should organisations prioritise cross-application SoD over single-system controls?

A: They should prioritise it when core business workflows span multiple business applications and the same identity can request, approve, and execute steps in different systems.

Q: What signs show that SoD governance is failing in practice?

A: Common signs include users who can both create and approve transactions, admins who review their own privileged activity, recurring access creep, and unresolved toxic entitlement combinations.

Q: What breaks when segregation of duties is the only control in place?

A: SoD blocks some toxic combinations, but it does not clean up stale, unused, or orphaned access.

Practitioner guidance

  • Define SoD at the business-process level Map conflicts around end-to-end business activities such as create, approve, post, and pay, then trace where those steps live across ERP and adjacent applications.
  • Centralise access and risk visibility Build a single view of entitlements and SoD conflicts across the applications that support finance, procurement, HR, and customer operations.
  • Tie findings to workflow remediation Route SoD violations into approval and remediation workflows so conflicts are removed, constrained, or explicitly risk-accepted with evidence.

Bottom line: Segregation of duties is increasingly a cross-application governance problem, not a single-system configuration task.

Glossary terms: Segregation of Duties, Cross-application SoD Drift, Explainable Audit Trail, Workflow-Driven Remediation

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 7 days ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20712
 

Cross-application SoD is now the real control boundary: the old model assumed segregation could be enforced inside a single ERP. That assumption fails when finance, CRM, HR, and business workflows are split across separate applications with different permission models. The implication is that identity teams have to govern access combinations across the business process, not just within one platform.

A question worth separating out:

Q: How do security teams know if SoD controls are actually working?

A: SoD controls are working only if live access state matches the approved separation model across systems. Teams should verify that no identity can both initiate and validate the same sensitive transaction, and that exceptions are time-bound and independently reviewed. If certification reports look clean but operational workflows still allow self-approval, the control is failing.

👉 Read our full editorial: Cross-application SoD needs governance beyond periodic reviews


This post was modified 7 days ago by NHI Mgmt Group

   
ReplyQuote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.