Use cases.
One problem, the checks we ran and what they found. Most come from our own project work with the client names removed; the rest are illustrative scenarios, and each one is marked.
Use cases
5 results for “segregation of duties”. Show everything
A consumer-goods company puts six applications under one control framework
Six business applications around SAP were each governed on their own. One matrix of 91 controls and 103 segregation-of-duties rules, tested against real user data, showed what to fix first.
Segregation of duties where one application feeds SAP
A distributor system and a cloud procurement platform both feed SAP, and neither had a segregation-of-duties rule set. We defined 293 functions, found 41 conflicts and rated each by whether one person alone could cause a loss.
A bank reviews who can do what across 15 applications
A bank needed a role and access review across 15 core applications. Ten checks on users, roles and job titles found segregation-of-duties conflicts, dormant access and roles that were near copies of each other.
An engineering manufacturer's SAP audit, built from raw tables
An engineering manufacturer wanted its SAP configuration, access and transactions audited together. Rule-based analytics on raw table extracts found over-privileged accounts and segregation-of-duties conflicts.
Before a core banking go-live, 40 job roles mapped to 611 screens
A bank moving to a new core banking system had job titles matched to access in the old system, but none in the new one. Reusing the old mapping, we built one matrix of 2,368 rows in under three weeks.
No use cases match every filter.
Read the thinking behind it
Short articles on revenue leakage, fraud, controls, forecasting and private AI.