Skip to content
SAP Ariba coverage Federated identity governance

SAP Ariba access governance

SafePaaS governs segregation of duties, privileged access and configuration change inside SAP Ariba — reading User, Group, Permissions and Realm, and testing policy against them.

Inside SAP Ariba, not beside it — the same rule book that governs every other system you run.

Book a Demo See How It Connects
Group read as SAP Ariba defines it, down to the realm Every snapshot re-tested in full, so a conflict reintroduced since the last one surfaces Across your estate SAP Ariba and every other system assessed together, so a duty held here and a duty held elsewhere meet One rule book applied across every system in the process, not one tool per application
Coverage at a glance

What SafePaaS reads, controls and monitors in SAP Ariba

Area Reads Controls Monitors
Access and segregation of duties User, Group, Permissions and Realm, and who holds each one SoD rules at the level of the entitlement itself; request-time prevention; simulation of a role change before it is applied; emergency access with a reason and an expiry New conflicts introduced by an entitlement change, expired assignments, and standing privilege nobody reviews
Transaction and configuration monitoring Posted documents, change records, master data, and the configuration settings that decide how money moves Policy on the settings that control the money — approval thresholds, tolerances and the terms applied to a payment Duplicate payments, threshold splitting, a master-data change followed by a payment, and configuration drift from baseline
Audit, risk and compliance Control test results, exceptions, approvals and the versioned SAP Ariba rule set One SAP Ariba control mapped to SOX, ITGC and internal policy; exceptions with an owner and an expiry Test status against each SAP Ariba control, and exceptions approaching expiry
The entitlement model we read

An SAP Ariba user’s authority is four layers below the role name

SafePaaS reads the SAP Ariba security model as SAP Ariba defines it: user, group, permissions, realm. Each layer is resolved, not assumed.

Only the deepest layers say what a user can actually do, and where. Everything above them is a container.

Figure 1 How SafePaaS resolves an SAP Ariba user to effective authority
  1. Layer 1 User
  2. Layer 2 Group
  3. Layer 3 Permissions what a member of the group may do
  4. Layer 4 Realm the boundary on how far that reach extends

A container in this chain can be widened while keeping the name an access review sees, and the deepest layer differs with every assignment. That is why SafePaaS tests the authority a user actually resolves to, not the label attached to it.

Coverage in detail

How each area works in SAP Ariba

How does SafePaaS enforce segregation of duties in SAP Ariba?

SafePaaS Enterprise Access Monitor tests SoD rules against an ERP Snapshot of your SAP Ariba security model — user, group, permissions, realm — rather than against the live system, so a test is repeatable and a result is defensible.

Modules Enterprise Access Monitor Enterprise iAccess Enterprise Roles Manager
▸ Defines rules at the level of the entitlements themselves, not just the user list, so a conflict is found where it actually lives ▸ False-positive filters remove inactive users, expired assignments and end-dated roles before anyone reviews a result ▸ Detects conflicts that span SAP Ariba and the rest of your estate, so a duty held in one system and a duty held in another are assessed together rather than separately ▸ Enterprise Roles Manager simulates a role change before it is applied, so a change does not reintroduce the violation you just remediated ▸ Violations carry status — Open, Closed, Remediation, Exception — with workflow, reminders and ITSM ticketing ▸ Mitigation records the compensating control and its evidence where a conflict cannot be removed ▸ Emergency access is granted with a stated reason, a time box, and a log of everything done while elevated
Connection

How does SafePaaS connect to SAP Ariba?

SafePaaS extracts through the platform’s own service interfaces — SOAP per security object, REST for transactions, or a direct database connection where the platform is not cloud-hosted.

Inside SAP Ariba → SafePaaS extraction SOAP services per security object returning XML; REST endpoints returning JSON for occurrences; a direct database connection where the platform runs on-premise.
Transfer → DataProbe The collected data is pushed out to SafePaaS through DataProbe.
Normalize → DataPaaS The transformation layer. Normalizes the data where required so one rule book can test it.
Result ERP Snapshot The point-in-time copy every module tests against — SoD, monitoring, certification and audit evidence alike.
What is read User, Group, Permissions and Realm How data moves Everything collected lands in the FSOD_* open interface tables, and DataPaaS normalizes it from there First snapshot A baseline of every user, role and entitlement assignment, and the first SoD test result set against your own rule book Protection Traffic terminates behind a WAF and an API gateway; the snapshot is tenant-isolated at rest
What runs inside SAP Ariba Nothing Extraction runs through the platform’s own service interfaces, so no SafePaaS component is deployed into it.

Because every governance module tests the snapshot rather than the live system, the same rule book applies to SAP Ariba and to every other system in the same business process.

Coexistence

Does SafePaaS replace SailPoint, Entra ID or my existing IGA?

No — and that is the point of federated identity governance. What your identity platform cannot see is what a role permits once the user is inside SAP Ariba, because that answer lives four layers down in the security model SAP Ariba publishes.

Your identity platform owns

The account

Joiners, movers and leavers Birthright access The request workflow Provisioning a user into SAP Ariba, and recording that they hold a role
SafePaaS owns

What the role permits

The entitlement behind the role name SoD across SAP Ariba and the rest of the estate Configuration and transaction change inside SAP Ariba Findings handed back to your IGA

So a certification in your IGA reflects the entitlement rather than the role name, and an access request is checked for SoD before it is approved.

FAQs

What SAP Ariba teams ask first.

The security model as SAP Ariba defines it: user, group, permissions, realm. SafePaaS resolves the chain rather than recording the role name, because the role name is a container and the permission lives below it.

Nothing inside the application. Extraction runs through its own service interfaces. Everything collected is pushed out to DataProbe, where DataPaaS normalizes it into the snapshot every governance module tests.

Every test runs against a snapshot taken at a point in time, and Enterprise Roles Manager simulates a role change before it is applied. A change that would reintroduce a remediated conflict is visible before it reaches production rather than at the next review.

A baseline of every user, role and entitlement assignment, and the first SoD test result set against your own rule book — typically the first time the estate has been assessed against one rule book rather than several.

No. Your identity platform keeps the account, the joiner-mover-leaver process and the request workflow. SafePaaS governs what the entitlement behind the role actually permits, and hands findings back, so a certification reflects the entitlement rather than the role name.

Go deeper on SAP governance
Pillar Make ERP SOX compliance easier to run Pillar Policy-based access governance across the estate Hub SAP application coverage Index All application coverage
Next step

See how SafePaaS governs an SAP Ariba estate

A working walkthrough against a demo environment, with a specialist who can map what you see onto the roles, organisation structure and audit pressure you actually have.

What the walkthrough covers How the entitlement chain is read as SAP Ariba defines it — user, group, permissions, realm An SoD conflict traced from the rule to the entitlements that create it How a role change is simulated before it reintroduces a remediated conflict Where SafePaaS sits relative to the IGA and GRC tooling you already run