Detectsod-analyzer
Sodly
SAP Segregation-of-Duties analysis
487conflicts surfaced in a single run
Explore SodlyPlatform
One platform. Five modules. The whole loop.
Rinexis isn't only a service — it's a multi-tenant platform behind it. Five modules under one Control Shell find access risk, fix it, prove the fix against a live SOD engine, and export it back to SAP. Findings flow between modules: a Sodly conflict becomes a Roleforge redesign in one click.
Stage 1 of 5: Detect — Sodly. See every SOD conflict — with the evidence.
Sodly
See every SOD conflict — with the evidence.
Match assigned transactions and authorizations against your ruleset to surface every Segregation-of-Duties conflict, rated Critical → Low and backed by real execution counts — so you remediate confirmed risk first, not theoretical noise.
Explore Sodly487conflicts surfaced in a single run
Measuresod-analyzer · coverage
Coverage Scanner
Can you even trust your SOD ruleset?
64.99%composite coverage on a real ruleset
Explore Coverage ScannerExposetcodex
Tcodex
The transactions GRC can't see
7wrapper T-codes GRC reported as zero
Explore TcodexRemediateroleforge
Roleforge
Redesign the role. Prove it's clean. Ship it.
2 → 0conflicts resolved, 100% coverage, pre-ship
Explore RoleforgeGovernitgc-audit-control
ITGC Audit Control
Run the whole ITGC audit in one place
4engagements tracked end-to-end
Explore ITGC Audit ControlThe loop
Find it, fix it, prove it, ship it — without leaving the platform.
Sodly
Find the conflict
A critical SOD conflict surfaces — with real execution evidence.
Roleforge
Redesign the role
Edit T-codes, auth objects, and org-levels in a 3-pane editor.
live sodly
Prove it's clean
Re-simulate against the real engine: 2 → 0, coverage 100%.
PFCG export
Ship it to SAP
Emit an AGR_1251 workbook a Basis admin imports directly.
And Tcodex exposes a class of risk GRC literally can't see — custom wrapper transactions like ZME23 → ME23N that bypass transaction-level SOD checks entirely.