Endpoint case
Aggressive scanning and a blocked LSASS access
A big port scan from outside, then a mimikatz hit on LSASS that the EDR blocked. Who is behind it?
- IntermediateLevel
- 25 minAbout
- New detailsEvery attempt
- KQL or SPLQuery language
Free. Read the briefing as a guest; investigating needs a free account.
The alert
Perimeter port scan and a credential-dumping attempt
Big port scan from 203.0.113.62 then a mimikatz LSASS hit on RID-WS-0188. EDR says it blocked it but this looks bad - escalating.
From one version of the case: the company, the people and the details change with every attempt.
About this kind of alert
Scanning and credential-dumping alerts: what the start of an intrusion looks like, and also what an authorised test looks like.
What you do
- Read the escalation from an L1 colleague and the events they attached.
- Hunt the logs in KQL (Microsoft Sentinel) or SPL (Splunk) and pin the evidence.
- Find the root cause and scope the incident: which accounts and hosts are affected.
- Map what you found to MITRE ATT&CK, set the severity and choose the response.
- Get a debrief: what happened, the evidence you missed, and what the attacker does next if you were wrong.
Logs you will query
| Microsoft Sentinel | Splunk |
|---|---|
AuditLogs | index=azure sourcetype=azure:monitor:aad |
CommonSecurityLog | index=firewall sourcetype=fgt_traffic |
SigninLogs | index=azure sourcetype=azure:monitor:aad |
Sysmon | index=sysmon sourcetype=XmlWinEventLog |
SecurityEvent | index=wineventlog sourcetype=XmlWinEventLog |


