Cross-System SoD — Multi-ERP conflict detection
50 conflict patterns spanning multiple ERP and cloud platforms. The fraud paths a single-system review will never see — a user creating a vendor invoice on SAP and releasing the payment on Oracle, posting GL on D365 and approving on NetSuite, granting IAM roles on AWS and clearing audit logs on Azure. This is the Onapsis-parity story.
1 How it works
Instead of hard-coding N×M platform-pair rules (which doesn't scale), the engine uses two layers:
- Business-function keyword map — for each of 28 business functions (AP_ENTRY, PAYMENT_RELEASE, GL_POSTING, USER_ADMIN, KEY_VAULT_READ, TREASURY_DEAL, etc.), V/ergent maintains the role-name keywords that signal the function on each platform. A new platform plugs in by adding keywords; rules require no change.
- Conflict definitions — 50 incompatible-function pairs. Adding a new conflict rule covers all platform combinations automatically.
The engine takes the merged user roster across all selected platforms, finds every user who holds at least one role matching function-A on any platform AND function-B on any other platform, and emits a violation per conflict / user / platform-pair.
2 The 50 conflict rules — by family
Accounts Payable / vendor-side
Accounts Receivable / customer-side
General Ledger / period / tax
Treasury / FX
HR / Payroll
Identity, role & log tampering
Cloud-native / multi-cloud
Asset / Inventory
PII data-export chains
3 What inputs does the engine need?
Cross-system SoD reuses the per-platform user/role exports your normal audit already uploads. Specifically the user_role_matrix.csv (or role_assignments.csv for cloud connectors) from each platform you want included in the cross-system view.
Identity merging happens by matching email / username / employee_id across rosters via audit/enhanced/user_identity.merge_rosters. If a user has different IDs on different platforms but the email matches, they are merged. The engine de-duplicates per (user, conflict, platform-pair) so violations are not double-counted.
4 Framework citations
Every violation carries 13-framework citations
Cross-system SoD specifically maps to: SOX CC6.3 · ISO 27001 A.9.4.1 · A.5.18 · A.8.10 · A.8.20 · NIST PR.AA-04 / PR.AC-04 · DE.AE-04 · COSO 2013 P10 · COBIT APO01.02 · BAI06.01 · DSS05.04 · PCI DSS 7.2 / 11.6 · GDPR Art 32 / 33 · Kenya DPA §41 · DORA Art 9(4)(c) · CIS AWS 3.x / 5.x · CIS Azure 5.x / 8.x · ACFE Occupational Fraud · FATF Trade-Based ML.
5 Where it appears in the V/ergent UI
Cross-system SoD runs as part of every audit run that includes 2+ platforms. Violations appear inline in the run-detail report (separately tagged as Cross-System) and in the dedicated dashboard at /api/cross-system-sod.
Browse the full registry at the Check Packs page — pack cross-system-sod.