Capabilities by platform
Use this page when a client asks “what do you do for our platform?”
Side by side
Section titled “Side by side”| Okta | Auth0 | Microsoft Entra ID | |
|---|---|---|---|
| Kind of identity | Workforce | Customer | Workforce |
| How events arrive | Event hook (push) | Log stream (push) | Microsoft Graph (poll) |
| Time to appear | Seconds | Seconds | 5 to 60 minutes |
| Credentials Identiguard holds | API service integration client ID and secret | None | App registration client ID and secret |
| Detectors | Yes | Yes | Yes |
| Health check report | Yes | Yes | Yes |
| Report comparison | Yes | Not yet | Not yet |
| Provider status page | Yes | Yes, by region | Yes, per tenant |
| Security advisories | Yes | Yes | Yes |
| Synthetic journeys | No | Yes | No |
| API metrics | No | Yes (beta) | No |
- Events arrive in real time through an event hook that Identiguard creates and manages.
- The integration is installed from the Okta Integration Network as a read-only API service integration.
- About 77 event types can be monitored, covering security, authenticators, admin roles, identity providers, policies, rate limits and application lifecycle.
- AD and LDAP directory agents are checked on a timer, with version and upgrade status.
- The report covers user lifecycle, international activity, system log activity, MFA factors and directory agents.
- Events arrive through a log stream that the client creates, manually or with Terraform. Identiguard never holds an Auth0 credential.
- All 185 Auth0 log event codes are catalogued. A recommended set leaves out the very high-volume codes.
- Auth0 Action log lines can be sent in as events.
- A metric stream (beta) adds API traffic, rate-limit hits and the busiest operations.
- Synthetic journeys replay sign-in, sign-up and password reset in a real browser.
- The report covers journey success rates, MFA health, the password reset funnel, connections, attack protection and API traffic.
Microsoft Entra ID
Section titled “Microsoft Entra ID”- Identiguard polls Microsoft Graph for risky users, risk detections, directory audits and sign-ins.
- What a client gets depends on their Microsoft licences. Sign-in data needs Entra ID P1. Workload identity risk needs Workload ID Premium.
- The report covers risk detections, risky users, sign-in failures, privileged changes, MFA coverage, Conditional Access, application credentials and Microsoft Secure Score.
- Report sections a tenant is not licensed for are marked Not available. They do not fail the report.
Okta and Entra together
Section titled “Okta and Entra together”Many clients run both. Put the two tenants in one correlation group and Identiguard links activity by the same person across both. Workforce and customer identities are never linked to each other.