Suspicious Okta SSO Access to Many Applications in Short Window

PremiumReviewedSigma · Medium · v1
Product
okta
Service
okta
Author
HuntRule
Published
2026-10-25
Updated
2026-10-25

ATT&CK techniques

Initial Access → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Execution

  4. Cred Access

  5. Discovery

  6. Lateral Movement

  7. Collection

  8. C2

  9. Exfiltration

  10. Impact

What it detects

This rule detects a single Okta actor authenticating via SSO into six or more distinct application instances within five minutes. A rapid fan-out across many apps is consistent with a hijacked session enumerating available resources rather than normal user behaviour.

Related detections9 linkedT1078.004 — drag to rearrange
Suspicious Microsoft Entra Device Code Authentication Flow
Suspicious M365 Password Spraying via Azure PowerShell AppId from Quad7 Botnet
Suspicious AWS Instance Access or Export via SSH Key or Export Task
Suspicious Azure OpenAI Model Enumeration and Deployment Creation (via azure)
Suspicious Azure Cognitive Services Account Key Enumeration via ListKeys (via azure)
Malicious Business Email Compromise OAuth Application Sign-In via Entra ID Service Principal (via azure)
Suspicious AWS API Call from TruffleHog Credential Scanner User Agent
Suspicious Compute Instance Metadata Modification in GCP
Malicious JavaGhost Security Group Creation (via cloudtrail)
Suspicious Okta SSO Access to Many Applications in Short Window
Pivot detection · T1078.004 · 9 related

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.