Okta

LiveIdentity & Access

Okta connector — read-only, agentless

Scans Okta users, application assignments, and group memberships to map who can sign in to which application.

What we scan

User inventory, application assignments, and group memberships (never credentials)
Sign-on and access relationships

Read-only monitoring — nothing in your Okta data changes unless you turn on auto-remediation and grant write access separately.

• Okta administrator who can create an API token (Read-Only Administrator is sufficient and recommended)
• A read-only Okta API token (Security → API → Tokens) and your Okta org URL

Typical first scan: 1–4 minutes

okta.users.readList users and their status, last-login, enrolled MFA factors, and admin roles — to find accounts without MFA, admin sprawl, and dormant or deactivated users that still hold access.
okta.groups.readList groups and the built-in "Everyone" group to expand group-based app access.
okta.apps.readList app integrations and per-app user/group assignments — who can sign into which application (the core IdP governance surface), including AI / OAuth apps and their scopes.
okta.policies.readRead password, sign-on, and session policy to check minimum standards (password strength, admin MFA, session lifetime).
okta.logs.readRead a bounded slice of the System Log to flag suspicious events (repeated failed logins, new admin grants, new app additions) and detect zombie apps with no recent sign-in.

11 detection rules run on every Okta scan. Each finding ships with a plain-language explanation, the evidence behind it and remediation steps.

Connect your first source in minutes — free, read-only, no sales call.