Walkthrough
One finding, from trigger to audit evidence.
David Okafor resigned. Eight days later, three systems still showed him active. This is every step VerifAIdentity took to reach that conclusion, and every piece of evidence behind it, exactly as the product stores it.
The trigger comes from HR
The HR worker export is the authority for who has left. Its termination date starts the clock; access ends at the end of that day.
- Source
- HR worker export (CSV), synced Nov 22, 04:37 UTC
- Record
- E1006, David Okafor
- Status
- Terminated, reason: resigned
- Termination date
- Nov 14, 2026 (treated as 23:59:59 UTC)
One person across every system
Accounts are matched to one person by employee ID, email and governance links. Each account keeps its system's own immutable ID; display names are never used as keys.
Match confidence for this person: high.
System Account (immutable ID) Okta david.okafor@lab.verifaidentity.com 00u19w5wsqgNU44pv698Entra david.okafor@venkatapedioutlook.onmicrosoft.com ca607f83-3126-4053-92b0-424bc5affa3aGovernance david.okafor 2e6145f4-7cab-5cbc-9c21-a08920b91636PingOne No account The obligation and its deadline
The rule is versioned and owned. The deadline is the company's setting, not ours; the framework references are for orientation, not a legal opinion.
- Rule
- CLK-LEAVER version 2.0, "Leaver access removed everywhere"
- Owner
- IAM operations lead
- Setting
leaver_removal_hours = 24- Deadline
- Nov 15, 2026, 23:59:59 UTC
- Scope
- Okta, Entra, PingOne, governance
- Related to
- PCI DSS 4.0 8.2.5, SOX ITGC user termination, HIPAA 164.308(a)(3)(ii)(C)
Expected against observed, on fresh data only
Each system's data must be newer than the freshness window (48 hours by default). Stale data makes the clock "cannot be verified", never "met".
System Expected Observed Data synced Okta Off Active Nov 22, 04:37 UTC, fresh Entra Off Enabled Nov 22, 04:37 UTC, fresh Governance Off Enabled Nov 22, 04:37 UTC, fresh What "active" actually means here
An active account is a reported state. Each account is described in layers, each with the evidence behind it. Layers we cannot observe are said to be unobservable, not assumed.
Okta: status ACTIVE; Okta's API does not list sessions; last sign-in Nov 14, 04:46 UTC, none after leaving.
Entra: enabled; none of the tenant's 0 Conditional Access policies blocks him; session revocation time is collected from the next sync; sign-in logs need P1 or P2.
Governance: a record, not a sign-in account; it still lists Okta and Entra access as approved.
System Account Sign-in Sessions Used after leaving Conclusion Okta Active Possible Not observable None seen Can still sign in Entra Enabled Possible Unknown Unknown Can still sign in Governance Enabled Not applicable Not applicable Not applicable Record only The verdict, at the strength the evidence allows
Breached: the deadline passed and fresh evidence shows the control failing. The statement stops where the evidence stops: possible access in two systems, no proven use.
Breached: overdue since Nov 15HighDavid Okafor left (HR: resigned on Nov 14). Still shown active in: Entra, Governance, Okta. Can still sign in: Entra, Okta. Still active as a record only: Governance.
What we cannot say: whether he used either account after leaving through a session we cannot see. Entra sign-in logs would close that gap.
Evidence that can be checked later
The clock record is fingerprinted with SHA-256 and appended to the tenant's evidence chain. Each chain entry links to the one before it and is signed with a key that never enters the database.
An auditor keeps the chain head. Later,
python -m stack.evidence verify lab head.jsonshows whether anything was edited, removed or rewritten since.- Clock
493ac5e5cb20f72d- Fingerprint
270b30c2ded006ca…ededff89- Chain entry
- linked to the previous entry and signed (HMAC-SHA256)
- History
- breached since Nov 22, 02:41 UTC
- Method
- EC-1.0, see Methods
Into your SIEM, in an open format
The same finding goes to your SIEM as an OCSF Compliance Finding over syslog (CEF), Splunk HEC or a signed webhook, with the fingerprint, so the evidence can be matched later.
{ "class_name": "Compliance Finding", "severity": "High", "status": "breached", "finding_info": { "uid": "493ac5e5cb20f72d", "title": "Leaver access removed everywhere" }, "compliance": { "control": "CLK-LEAVER", "status": "Fail" }, "unmapped": { "deadline_at": "2026-11-15T23:59:59+00:00", "evidence_sha256": "270b30c2…", "rule_version": "2.0" } }Asked in plain English
The assistant answers from the stored evidence and cites it. It does not re-decide the finding; the rule did that.
Is David Okafor removed everywhere?
No. The leaver clock is breached: still shown active in Entra, governance and Okta; Entra and Okta can still sign him in.
Based on evidence. Sources: clock 493ac5e5, HR record E1006.
What's the weather in Dallas?
Not enough evidence. This doesn't match a person or topic in the connected data.
No guess made.