Spike in Successful Logon Events from a Source IP
A machine learning job found an unusually large spike in successful authentication events from a particular source IP address. This can be due to password spraying, user enumeration or brute force activity.
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 2 ATT&CK techniques it maps to.
Known benign triggers
- Build servers and CI systems can sometimes trigger this alert. Security test cycles that include brute force or password spraying activities may trigger this alert.
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 |
|---|---|
| www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html | 103 |
From the source
- At source
- Open at source
- Upstream identifier
- e26aed74-c816-40d3-a810-48d6fbd8b2fd
- Tagged by the source as
- Data Source: Auditd ManagerData Source: Elastic DefendData Source: Windows Security Event LogsDomain: EndpointResources: Investigation GuideRule Type: Machine LearningRule Type: MLTactic: Credential AccessTactic: Defense EvasionUse 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
- 2