Paste your account export. See every account nobody owns.
Orphaned Account Checker reads your account export line by line for orphaned, dormant and unrotated accounts against ISO/IEC 27001, SOC 2, PCI DSS and CIS Controls, one inventory of every credential, each line read on owner, last rotation, last access review and last use. Paste your account export: people, service accounts, API keys and AI agent credentials. Every account whose owner has left or was never named comes back, with the dormant ones, the keys nobody rotated, service accounts anyone can log in to, shared logins and agent credentials nobody reviews, each with the clause an auditor will cite.
Paste an export, never a connection. Your directory's user export, your cloud platform's credential report or a spreadsheet: one line per account. Nothing connects to your systems and nothing leaves your browser until you save. Recognised secret patterns are removed; review the list before you save.
Never paste passwords, keys or tokens; the list needs names and dates only.
Masked names work. Replace account names and people with your own codes (E1042, SVC-07); every finding still works, and the staff list can use the same codes.
Every flag shows the rule that raised it and the column it read.
It never scores an account or a company, and never says an account is compliant, secure or safe to delete. A finding is a question for the account owner or the reviewer.
| Hook | Account | Owner | Findings |
|---|---|---|---|
| 1 | adm-E1008 administrator or privileged person account | E1008 left | 145 |
| 2 | svc-orders-api service account | E1005 left | 256 |
| 4 | svc-backup service account | IT Operations (team mailbox) team | 357 |
| – | agent-claims-triage ai agent credential | none named no owner | 31011 |
| 12 | breakglass-01 break-glass or emergency account | E1002 active | none raised |
40 accounts, 11 nobody owns, 5 dormant, 4 privileged with a gap.
14 of 14 finding types raised, 40 of 40 accounts typed, 2 assumed from the name.

Paste the export as it comes out
One account per row: account | type | system | owner at least, or the columns your export already carries (last logon, password last set, enabled, member of, MFA, last reviewed, ticket). Column names are matched against 220 names that directory, identity provider, cloud credential report and service account exports use.
Add the staff list, if you have it
One person per row: person | active or left | left on, masked or not. With it, owners who have left and a leaver's own enabled account become findings; without it, no owner is checked and the page says so.
Take the questions to the owners
Fourteen findings in a fixed order, from a leaver's enabled account to a secret pasted where a label belongs, each naming the accounts, the column that raised it, the clause from the regimes you tick, and the question for the account owner or the reviewer.
Why an export, and not a connector
A connector reads your directory live, and before anyone can use it a security review has to approve the access it asks for. The question the auditor, the board or the security manager asks first is simpler: across every login we have, people, service accounts, keys and agents, who owns each one, and which ones nobody does. The answer sits in the exports your team already pulls for the access review. That is what this reads, in your browser, from the export as it stands.
Orphaned accounts: the questions access reviewers ask
What does Orphaned Account Checker do?
It reads an account export line by line for orphaned, dormant and unrotated accounts against ISO/IEC 27001, SOC 2, PCI DSS and CIS Controls. Every account whose owner has left or was never named comes back, with the dormant ones, the keys nobody rotated, service accounts anyone can log in to, shared logins and agent credentials nobody reviews. Every flag shows the rule that raised it and the column it read.
What counts as an orphaned account?
An orphaned account is one whose owner has left or was never named. The tool reads people, service accounts, API keys and AI agent credentials from one inventory of every credential. It never scores an account or a company, and never says an account is compliant, secure or safe to delete.
Do I have to connect to my directory?
No. You paste an export, never a connection: your directory's user export, your cloud platform's credential report, or a spreadsheet, one line per account. Nothing connects to your systems, and nothing leaves your browser until you save. That avoids a connector access review before the check can run.
Is it safe to paste an export?
Never paste passwords, keys or tokens; the list needs names and dates only. Recognised secret patterns are removed in your browser, and you review the cleaned list before you save. Masked names work, so you can replace account names with your own codes and every finding still works.
Can I mask account names?
Yes. Replace account names and people with your own codes such as E1042 or SVC-07; every finding still works, and the staff list can use the same codes. That way the export you paste does not carry real identities.
Which regimes does it check against?
You can tick ISO/IEC 27001, SOC 2, PCI DSS (card data in scope), NIST SP 800-53, CIS Controls, NIS2 and ISO/IEC 42001. Every obligation is stated in the tool's words and cited to its clause. Where the page names an obligation without stating its requirements, it says so and does not state them.
Is it free?
Eight accounts can be checked free and no account is needed. A published dictionary of 14 account types, 12 system classes and 220 export column names loads with the page, and every check runs in your browser.
What does the staff list add?
Add a staff list of person, active or left, and left on, masked or not. With it, owners who have left and a leaver's own enabled account become findings; without it, no owner is checked and the page says so. The staff list can use the same codes as the account export.
What can I import?
You can paste a CSV, or SCIM or Okta JSON, or Microsoft Graph users JSON, or drop the file, with dedicated import pages for SCIM, Okta and Microsoft Graph. For a table, a header row with columns such as account, type, system, owner, enabled, last used, last changed, created, privileged or member of, interactive login, MFA, stored in, last reviewed, approval and notes is read.
Does it tell me an account is safe to delete?
No. It never scores an account or a company, and never says an account is compliant, secure or safe to delete. A finding is a question for the account owner or the reviewer. The tool shows the rule each finding rests on and leaves the decision with a person.
Does it cover service accounts, API keys and AI agent credentials?
Yes. The inventory covers people, service accounts, API keys and AI agent credentials. It brings back keys nobody rotated, service accounts anyone can log in to, shared logins, and agent credentials nobody reviews, each with the clause an auditor will cite.
How are dormancy and rotation periods set?
You set the regimes that apply and the periods: dormant after more than a number of days, changed within a number of days, and reviewed every number of months. A first line such as regimes, dormant after and as at sets those defaults. The findings then read your dates against the periods you set.
How Orphaned Account Checker compares with the alternatives
A spreadsheet is better for keeping the account inventory and editing it by hand before you use it, since it is free and fully under your control. An identity or security consultant is better on judgement, because deciding whether an account is safe to delete or worth a look is theirs, and a directory or identity platform with a live connector is better at reading the current state of every account continuously instead of from an export. A general AI assistant is better at drafting the review questions or the policy text, but it does not read a directory or cloud credential export against the clause text of ISO/IEC 27001, SOC 2, PCI DSS and CIS Controls. The checker reads the export you already pull, in your browser, and flags orphaned, dormant and unrotated accounts along with the rule and the column that raised each one; it never scores an account or a company and never says one is compliant, secure or safe to delete.
Primary source: ISO/IEC 27001:2022