How a rule decides
Each rule has a condition, an attack category, a MITRE ATT&CK technique and impact scores for confidentiality, integrity and availability. Severity comes from the highest of those three scores. Rules can look back over stored logs, remove duplicate alerts and group new alerts under an existing one. Here are a few of the built-in rules.
- RDP brute force attack
- Kerberoasting attack detection
- AWS CloudTrail log suspended
- Cobalt Strike DNS beacon pattern detected
- ESXi ransomware attack detection
Events arrivingeach one checked, then stored
- wineventloglogon203.0.113.45svc-backup on dc01Alert
- wineventlogprocess-createdwks-0457outlook.exeStored
- wineventloglogon-failed203.0.113.45svc-backup on dc01Stored
- wineventloglogon-failed203.0.113.45svc-backup on dc01Stored
- firewall-fortigate-trafficdeny192.0.2.20010.20.0.10:3389Stored
- wineventloglogon-failed203.0.113.45svc-backup on dc01Stored
- wineventloglogon-failed203.0.113.45svc-backup on dc01Stored
- awsGetObject10.30.0.12backups-prod bucketStored
Detection rule
Windows: Multiple Logon Failure Followed by Logon Success
MITRE ATT&CK T1110, Brute Force
Failed logons for the same account, from the same address, in 5 minutes10 of 10
Then a successful logon from that address
No alert yet
The rule fires on the event that completes the pattern.
Alert raisedHigh
10 failed logons, then a success, for svc-backup on dc01 from 203.0.113.45.
Raised while the event was processed, before it was written to storage.