Skip to main content

Cotool + Okta

Connect Okta to Cotool so agents search the System Log, run MFA fatigue and session detections, look up users, and revoke sessions in identity response.

Identity & Access
Updated

The short answer

With Okta connected, Cotool searches the Okta System Log, runs detections such as MFA push fatigue and session reuse on Okta logs, and gives identity response agents tools to retrieve Okta users and revoke their sessions.[1][2][3]

How it connects: Cotool connects to Okta's management APIs and supports private key JWT authentication. Okta service apps that request Okta scopes must authenticate with private_key_jwt: the app signs a JWT with a private key whose public key is registered in Okta.[1][6]

What Cotool uses from Okta

System Log
Agents search Okta System Log events during investigations, with rate-limit handling. Okta's event types include user.session.start and user.mfa.okta_verify.deny_push.[1][8]
Users
Detections and agents list and retrieve Okta users, for example to find active Okta accounts for people HR has terminated.[2][3]
Okta logs in Cotool
Okta System Log can be stored in Cotool, where detections query it as cotool_logs.okta.[2][4]

Response actions

These change state in Okta, so they are the steps teams usually gate behind approval.

Revoke user sessions
Identity response agents in Cotool can use a Revoke Okta User Sessions tool alongside Retrieve Okta User.[3]

Detections, hunts, and triage

MFA push fatigueDetection
Cotool's example detection counts denied Okta Verify pushes per user over 10 minutes and flags users with 5 or more denials. Okta notes that deny_push is a classic-API event; Identity Engine orgs log user.authentication.auth_via_mfa with reason INVALID_CREDENTIALS instead.[2][8]
Terminated but still activeDetection
A detection compares terminated workers in Rippling against active Okta users and sends any match to triage.[2]
Session replay to sensitive dataDetection
Cotool's detection library example correlates Okta session replay with Google Workspace Drive access and runs every 15 minutes on both sources.[2]
Identity alert responseResponse
An Identity Alert Responder triages Okta Identity Protection alerts, retrieves the user, and can revoke their sessions when compromise is confirmed.[3]

Example query

MFA push fatigue over Okta logs in Cotoolsql
SELECT actor_id, COUNT(*) AS denies
FROM cotool_logs.okta
WHERE event_type = 'user.mfa.okta_verify.deny_push'
  AND ts > now() - INTERVAL 10 MINUTE
GROUP BY actor_id
HAVING denies >= 5

Adapted from the detection on Cotool's Detect page. On Identity Engine orgs, match user.authentication.auth_via_mfa failures instead.[2][8]

Setup and permissions

Create an API service app in Okta, register its public key, grant the Okta scopes it needs, and assign it an admin role that allows those operations.[6]

PermissionAccess
System Log read scopeThe read scope in Okta's `okta.logs` family. It lets the app read System Log entries.[7]Read
okta.users.readRead existing users' profiles and credentials.[7]Read
okta.groups.readRead groups and their members.[7]Read
okta.sessions.readRead sessions in the org.[7]Read
okta.users.manageManage users' profile and credentials information. Grant it only if agents should act on users.[7]Write

How Cotool works with Okta

  • Cotool added private key JWT authentication for Okta in release 0.68.0 and improved System Log search reliability and rate-limit handling in 0.46.0.[1]
  • Detections are Python code mapped to a visual workflow, so the Okta MFA fatigue thresholds can be edited in the visual view.[2]

FAQ

Is this the same as Okta SSO for Cotool?
No. Okta SSO and SCIM provisioning for signing in to Cotool are configured separately with SAML 2.0 and SCIM 2.0. This page covers Okta as a security data source and response target.[5]
Why does my MFA fatigue rule find nothing?
Identity Engine orgs do not log user.mfa.okta_verify.deny_push; they log user.authentication.auth_via_mfa with reason INVALID_CREDENTIALS. Match the event your org emits.[8]

Sources

  1. Changelog (Cotool docs) · accessed November 16, 2026
  2. Detections are code (Cotool Detect) · accessed November 16, 2026
  3. Respond to every signal (Cotool Respond) · accessed November 16, 2026
  4. SIEM (Cotool) · accessed November 16, 2026
  5. Okta integration (Cotool docs) · accessed November 16, 2026
  6. Implement OAuth for Okta with a service app (Okta Developer) · accessed November 16, 2026
  7. OAuth 2.0 scopes (Okta Developer) · accessed November 16, 2026
  8. Event types (Okta Developer) · accessed November 16, 2026

Related integrations

All integrations

Use cases with Okta

Attackers are scaling with tokens

Cotool helps defenders operate at machine speed. See how security teams are scaling Detection & Response.

Book a demo