HR says he left. Three systems still let him in.

VerifAIdentity reads HR, Okta, Microsoft Entra ID, PingOne and your governance tool (read-only), builds one record per person, and verifies with evidence where they disagree, which deadlines have passed, and what it cannot yet confirm.

David OkaforOperations Lead
SystemWhat it says
HRResigned on Nov 14
GovernanceEnabledShould be off
OktaActiveShould be off
Microsoft Entra IDActiveShould be off
PingOneNo account
Leaver deadline breachedDue Nov 15, 23:59 UTC. Six days overdue.

From our lab: a simulated company in our own tenants, November 21, 2026.

Each identity system is right about itself. Nobody checks them against each other.

Your sign-in, governance and HR systems each keep their own answer. VerifAIdentity compares them continuously and tells you what to fix first.

Leavers removed everywhere, on time

The HR termination date starts a clock. Every account must be off by your deadline, in every system.

In our lab: one leaver still active in three systems; two others removed 12 and 19 days late, kept as audit exceptions.

Access that matches what was approved

Accounts and admin roles are compared with your governance approvals, including systems never connected to governance.

In our lab: every Global Administrator traced to an approval, including the break-glass account.

Expiring secrets and attacks across vendors

App secrets and certificates get a warning window. Password spray and takeover attempts are spotted even when they span two vendors.

In our lab: an app secret expiring Feb 12, 2027 was flagged 82 days ahead.

How it works

Five steps, repeated every time it pulls. Nothing is written back to your systems.

  1. Connect, read-only

    Read-only API access to Okta, Entra, PingOne and governance, plus your HR export.

  2. One record per person

    Every account is matched to one person, across different usernames and systems.

  3. Rules and deadlines

    Consistency rules, compliance clocks and threat detections, with deadlines you set.

  4. Evidence

    Each finding keeps its source records and a SHA-256 fingerprint, so changes after the fact show.

  5. Your tools

    Findings go to your SIEM in the open OCSF format: syslog (CEF), Splunk HEC or a signed webhook.

VerifAIdentity Identity Command Center showing a posture score, open risks, people and findings
Identity Command Center on our lab data (simulated people).

Answers that show their sources, or say they can't answer

Ask in plain English. Every answer lists the records it used. When the connected data can't answer, it says so instead of guessing.

Is David Okafor removed everywhere?

No. The leaver clock is breached: still active in Entra, governance and Okta.

Based on evidence. Sources: clock 493ac5e5, fingerprint ee3b0af7, 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.

On our 40-question test set, 40 answers were correct or correctly declined. A design partner's own expert writes and judges the test set in a pilot.

Built to be trusted with identity data

Read-only, always
Connectors request read permissions only. VerifAIdentity cannot change, disable or create anything in your systems.
Only what the rules need
Names, usernames, status, roles, approvals and sign-in events. No passwords, tokens, messages or files.
Your data stays yours
Each company's data is kept apart in its own tenant. Pilot data is deleted when the pilot ends.
Evidence you can check
Findings and deadline records carry fingerprints, so an auditor can see that nothing was edited afterwards.
Rules decide, not a chatbot
Findings come from deterministic rules. Text inside your logs is treated as data, never as an instruction.
Fits what you run
It adds a cross-system view; it does not replace your identity provider, governance tool or SIEM.

Works with: Okta, Microsoft Entra ID, PingOne, midPoint, HR worker exports (CSV), Splunk, and any SIEM that accepts syslog or webhooks. SailPoint and Saviynt are next.

Run a read-only pilot with us

We are looking for a few design partners with more than one identity provider and a regulator or auditor who asks about leavers and privileged access.

What a pilot looks like

  • 30 to 60 days, read-only
  • Okta and Microsoft Entra ID plus your HR export
  • Two or three applications you choose
  • A dedicated hosted instance, or inside your own environment
  • About one hour a week from your IAM lead

How we judge it together

MeasureTarget
AccuracyAt least 90% correct or properly qualified on 40 cases your expert writes
EvidenceEvery finding links to its source records
Time to triageAt least 50% faster than your current workflow
IsolationNo data from any other tenant, tested
Real useYour engineers choose it in most target investigations

Where we are: VerifAIdentity is built and tested on lab data in our own tenants. It is not yet production ready, and a pilot is how we measure it on real data with you.