Inventory
SailPoint retains: System of record for accounts and certifications
EmpowerID adds: Agent and NHI correlation on connected paths
Customer adoption path (choice, not a forced migration): Observe → Govern → Own
Solution
Extend the estate — do not rip and replace
Retain SailPoint, SAP GRC, ServiceNow, Entra, Okta, and Ping front doors while EmpowerID governs authority, execution, and evidence on declared paths.
Keep the front doors, add the governed spine
Requests and signals enter the spine; governed effects and evidence return on declared paths.
Existing front doors
- ServiceNow
- Existing IGA
- SAP GRC
- Custom portals / APIs
- AI agents
- Existing IdPs
Governed spine
- Context / graph
- Authorization
- Workflow / execution
- Evidence
↓ governed effects ↑ evidence
Connected destinations
- Directory: AD, Entra, Okta
- SaaS / cloud: Salesforce, M365
- ERP: SAP, Oracle
- Database / API: JDBC, REST
Legend
- Identity and context
- Execution
- Evidence and proof
What this diagram shows
- Front doors: ServiceNow, Existing IGA, SAP GRC, Custom portals / APIs, AI agents, Existing IdPs.
- Spine: Context / graph → Authorization → Workflow / execution → Evidence.
- Evidence returns to the proof chain.
Four SailPoint patterns
SAP IDM modernization while preserving SAP GRC
GRC logic remains in place
SAP GRCEmpowerID Virtual DirectoryGoverned spineMultiple targets
Speaks legacy LDAP dialect expected by GRC; normalizes into governed events.
Targets: Entra ID, Okta, ServiceNow, SAP IAS, Other validated destinations.
SAP IDM removed (former dependency)
Adoption modes
Services behind existing interfaces — users keep familiar portals.
Choose per journey; change later without re-architecting.
Distributed deployment
Shared policy contract with local PDP, PIPs, PEP, and evidence producers — architectural option, not universal topology.
Shared policy contract — versioned authorization model
Entity A
- • Local PDP
- • Local PIPs / facts
- • Local PEP
- • Local evidence producer
Entity B
- • Local PDP
- • Local PIPs / facts
- • Local PEP
- • Local evidence producer
Entity C
- • Local PDP
- • Local PIPs / facts
- • Local PEP
- • Local evidence producer
Shared policy contract with local PDP, PIPs, PEP, and evidence producers — architectural option, not universal topology.
Legend
- Policy and decision
- Execution
- Evidence and proof
What this diagram shows
- Shared policy contract — versioned authorization model
- Entity A: Local PDP, Local PIPs / facts, Local PEP, Local evidence producer.
- Entity B: Local PDP, Local PIPs / facts, Local PEP, Local evidence producer.
- Entity C: Local PDP, Local PIPs / facts, Local PEP, Local evidence producer.
- Shared policy contract with local PDP, PIPs, PEP, and evidence producers — architectural option, not universal topology.
Get Started
Connect once. Govern consistently. Change safely.
Request Demo See the platform in action
Talk to an Expert Technical consultation
