Skip to content
SailPoint coexistence Federated identity governance

SailPoint and SafePaaS: what each one governs

SafePaaS does not replace SailPoint. It governs what a role permits once the user is inside the ERP — the layer an identity platform cannot see.

Beside SailPoint, not instead of it — one rule book across every system in the same business process.

Book a Demo See How It Connects
Business Role read as SailPoint defines it, down to the security attributes Every snapshot re-tested in full, so a conflict reintroduced since the last one surfaces Handed back findings from every governed system return to SailPoint, where your process already lives One rule book applied across every system in the process, not one tool per application
The entitlement model we read

A SailPoint user’s authority is five layers below the role name

SafePaaS reads the SailPoint security model as SailPoint defines it: user, business role, IT role, entitlement, security attributes. 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 a SailPoint user to effective authority
  1. Layer 1 User
  2. Layer 2 Business Role
  3. Layer 3 IT Role
  4. Layer 4 Entitlement
  5. Layer 5 Security Attributes

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

Where SafePaaS and SailPoint divide the work

What does SailPoint already govern?

SailPoint owns the account and the process around it, reading its own model to do so: user, business role, IT role, entitlement, security attributes. None of that is in question, and SafePaaS does not replace any of it.

▸ The account itself — joiners, movers and leavers ▸ Birthright access, and the request and approval workflow ▸ Provisioning a user into the downstream system, and recording that they hold a role there ▸ Certification campaigns, run against what it knows
Connection

How does SafePaaS connect to SailPoint?

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 SailPoint → 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, Business Role, IT Role, Entitlement and Security Attributes 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 SailPoint 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 SailPoint and to every other system in the same business process.

Proof
~14,000 employees in 100+ countries

Ran SafePaaS across an estate whose key systems in scope included SAP ECC, SAP GRC and SailPoint.

Key systems in scope SAP ECC SAP GRC SailPoint Read the case study
8 to 22 apps high-impact applications onboarded in 9 months 55% less manual effort for quarterly identity access reviews
FAQs

What SailPoint teams ask first.

The security model as SailPoint defines it: user, business role, IT role, entitlement, security attributes. 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 identity governance
Pillar Enhance your IGA Pillar Policy-based access governance across the estate Index All application coverage
Next step

See how SafePaaS governs a SailPoint 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 SailPoint defines it — user, business role, IT role, entitlement, security attributes 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