Home / Demos / Access governance
Governance an auditor can verify.
Security and compliance reviewers want evidence, not assurances. This walkthrough covers four things. Staff roles are managed with server-enforced least privilege and a required reason for every change. A credential inventory lists what each service credential protects and who rotates it, without reading a single secret. Every PHI view is audited. And the PHI access log can be filtered and paged, and records its own use.
What you'll see
- Role and facility scoping enforced on the server, with every change audited with its reason
- A credential inventory that shows names and metadata only, never secret values
- PHI views recorded per synthetic patient, then found in the access log seconds later
- Meta-audit: viewing the log is logged, without storing the search terms typed
Chapters
- 0:00 Staff roster and roles
- 0:23 Least privilege on the server
- 0:42 Changing a role, with a reason
- 0:57 Credential inventory
- 1:14 Value-free rotation age
- 1:28 Every PHI view is audited
- 1:44 Searching the PHI access log
- 1:59 Paging and capped exports
- 2:16 Viewing the log is logged
- 2:24 Governance an auditor can verify
- 2:32 About this recording
Transcript
0:07 Administrators manage staff accounts and roles in one place. The roster filters by role, facility, and status, and every change is audited with the reason given.
0:23 Each user holds one role, and most roles are scoped to a facility. Least privilege is enforced on the server: a facility admin can't grant the admin role, and an auditor sees the roster read only.
0:42 Changing a role takes a required reason. The change applies at once, and the history records who changed what, when, and why.
0:57 The credential inventory lists every service-to-service credential: what it protects, who consumes it, who rotates it, and the rotation target. It shows names and metadata only. No secret value is ever read or displayed.
1:14 Rotation age comes from value-free metadata written at deploy time. This local stack has no deploy, so ages show as unknown instead of being guessed.
1:28 Every access to protected health information is audited. Opening the alert inbox records a view for each synthetic patient on the screen.
1:44 In the PHI access log, an admin filters by date, user, action, resource, or outcome, newest first. The views from a moment ago are already here.
1:59 Results come 50 at a time, with an older-page cursor, so even a large log stays quick. Exports are capped, and they're recorded too.
2:16 Viewing the log is itself logged. The audit row notes that a user filter was used, never the email address that was typed.
2:24 Least privilege, no secret values on screen, and every PHI access audited: governance an auditor can verify.
2:32 A note on this recording: the narration uses a synthetic voice, and all data shown is synthetic demo data, not a live customer deployment.
Want to see this on your workflow?
We run walkthroughs against realistic synthetic populations that match your case mix.
Request a walkthrough