Cloud identity provider
The cloud directory most sign-ins pass through; its export carries last sign-in, MFA and guest accounts. The checker reads the system column to group the accounts; the findings come from the other columns, the same way for every system.
What the export usually carries
A cloud identity provider export usually carries the user, user type (member or guest), enabled, last sign-in, created and, in a separate report, MFA registration. Last sign-in commonly records interactive sign-ins by people; sign-ins by applications, service principals and managed identities are often logged separately and may not appear in that field, so an application reading as never signed in is a question, not a gap.
What the checker most often raises here
- 1. A leaver's own account is still enabled: The staff list is pasted, the account belongs to one person (a person or an administrator account, or a contractor whose own code is in the staff list), the staff list says that person left on or before the as-at date, and the account does not read as disabled. With no enabled column it is worded as a question.
- 4. Dormant for more than the threshold: The account is enabled or its status is not recorded, it is not a break-glass account, and its last used date is more than the threshold you set (default 90 days) before the as-at date. With CIS Controls ticked, more than 45 days (CIS 5.3) also fires; with PCI DSS ticked, more than 90 days (8.2.6) fires on user accounts. An account never used fires when its created date is older than the same periods. Exactly the period never fires.
- 10. Not reviewed within the interval: The list has a last reviewed column, and this account's cell is blank or older than the interval you set (default 12 months) before the as-at date. With PCI DSS ticked, user accounts also fire at more than 6 months (7.2.4); with CIS Controls ticked, every account at more than 12 months (6.8). Exactly the interval never fires. Without the column, the finding does not fire and every line says the column is missing.
- 2. Owner has left, or owner not recognised: The account is not a personal account, its owner names a person, and the staff list is pasted: when the list says that person has left it is a gap; when the owner is not in the list at all it is a question ("owner not recognised, confirm"). Without a staff list this finding never fires.
Account types found here
- Built-in or vendor default accounta system account
- Break-glass or emergency accounta user account
- AI agent credentiala system account
- Automation or bot (scheduled jobs, RPA)a system account
- Service accounta system account
- API key or access keya system account
- OAuth client or app registrationa system account
- Device or workload identitya system account
- Mailbox or resource accounta user account
- Test accounta user account
- Shared or generic logina user account
- Administrator or privileged person accounta user account
- Contractor or guesta user account
- Person (employee)a user account
The system names in your export are matched to these classes by the browser dictionary; product names are never shown on these pages. A system the dictionary does not place reads as other, and every finding still works.