Potential Okta Brute Force (Multi-Source)
Detects potential brute force attacks against a single Okta user account from multiple source IPs, indicating attackers rotating through proxy infrastructure to evade IP-based detection.
Detection logic
Its licence does not clear it for publishing here
Sunturai publishes a detection's own text where the licence it arrived under has been reviewed and permits it, and Elastic License 2.0 has not. The query as its source wrote it, its canonical form and the hash that pins this revision are in the workspace record.
Detection requirements
- Platform
- ContainersESXiIaaSIdentity ProviderLinuxmacOSNetwork DevicesOffice SuiteSaaSWindows
The rule states no platform. This is derived from the ATT&CK technique it maps to.
Known benign triggers
- Shared service accounts accessed from multiple legitimate infrastructure IPs.
- Users with legitimate multi-location access (mobile + home + office) experiencing concurrent login issues.
MITRE ATT&CK mappings
0 exclusive techniques.This is coverage no other published rule has; it is not this rule's total technique count.
References
| Reference | Cited by |
|---|---|
| developer.okta.com/docs/reference/api/event-types/ | 56from 2 sources |
| support.okta.com/help/s/article/Troubleshooting-Distributed-Brute-Force-andor-Password-Spray-attacks-in-Okta | 6 |
| www.elastic.co/security-labs/monitoring-okta-threats-with-elastic-security | 48from 2 sources |
| www.elastic.co/security-labs/starter-guide-to-understanding-okta | 48from 2 sources |
| www.elastic.co/security-labs/testing-okta-visibility-and-detection-dorothy | 45 |
| www.okta.com/identity-101/brute-force/ | 6 |
From the source
- At source
- Open at source
- Upstream identifier
- 5889760c-9858-4b4b-879c-e299df493295
- Tagged by the source as
- Data Source: OktaData Source: Okta System LogsDomain: IdentityNoise: LowPerformance: FastPlatform: OktaProfile: RecommendedResources: Investigation GuideRule Type: ES|QLTactic: Credential AccessThreat: Brute ForceUse Case: Identity and Access AuditUse Case: Threat Detection
Licence
- Published under
- Elastic License 2.0Read the licence
- Attribution
- Required
Authorship
- Written by
- Published
- Sep 20, 2026
- Version
- 3