Multiple Logon Failure Followed by Logon Success
Identifies multiple logon failures followed by a successful one from the same source address. Adversaries will often brute force login attempts across multiple users with a common or known password, in an attempt to…
Description
Identifies multiple logon failures followed by a successful one from the same source address. Adversaries will often brute force login attempts across multiple users with a common or known password, in an attempt to gain access to accounts.
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.
- Log source category
- event_index
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 |
|---|---|
| docs.microsoft.com/en-us/windows/security/threat-protection/auditing/event-4625 | 7from 2 sources |
From the source
- At source
- Open at source
- Upstream identifier
- 4e85dc8a-3e41-40d8-bc28-91af7ac6cf60
- Tagged by the source as
- Data Source: Windows Security Event LogsDomain: EndpointNoise: HighOS: WindowsPerformance: NormalPlatform: WindowsProfile: AggressiveResources: Investigation GuideResources: OsqueryRule Type: Event Correlation (EQL)Tactic: Credential AccessThreat: Brute ForceUse Case: Threat Detection
Licence
- Published under
- Elastic License 2.0Read the licence
- Attribution
- Required
Authorship
- Written by
- Published
- Sep 20, 2026
- Version
- 3