Case study · Identity and access
Access that reconciles itself.
Provisioning, reconciliation, and auditing across enterprise systems, with existing identity groups as the source of truth.
The problem
Access changes moved through multiple enterprise systems. Provisioning was manual, access drifted from the intended profile, and proving who had access to what meant assembling evidence from several places.
What we built
Zencode designed and built Sentra as a .NET and Angular application. A profile engine resolves grants by priority with deny-override rules, then compares desired access to actual access for each environment. Changes are applied idempotently and written to an audit log. Scheduled scans catch drift.
- Profile-based access resolution with priority and deny-override rules.
- Desired versus actual access comparison for each environment.
- Idempotent changes and an audit trail for every update.
- Scheduled scans that detect drift.
- Role-based access for administration, operations, audit, and read-only users.
The result
Provisioning and reconciliation are automated, changes are auditable, and administrators can see effective access and differences instead of reconstructing them by hand.
Confidentiality
Client and system names are withheld. Architecture and outcomes are described without client-specific details.
Related
Start here
Need access provisioning and reconciliation?
Tell us which systems hold the access, where the manual work is, and what an audit needs to prove. We will tell you whether we are the right fit.