Skip to content
CyberSimStart training
Illustration for the case: Aggressive scanning and a blocked LSASS access

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?

Open this case

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

  1. Read the escalation from an L1 colleague and the events they attached.
  2. Hunt the logs in KQL (Microsoft Sentinel) or SPL (Splunk) and pin the evidence.
  3. Find the root cause and scope the incident: which accounts and hosts are affected.
  4. Map what you found to MITRE ATT&CK, set the severity and choose the response.
  5. Get a debrief: what happened, the evidence you missed, and what the attacker does next if you were wrong.

Logs you will query

Microsoft SentinelSplunk
AuditLogsindex=azure sourcetype=azure:monitor:aad
CommonSecurityLogindex=firewall sourcetype=fgt_traffic
SigninLogsindex=azure sourcetype=azure:monitor:aad
Sysmonindex=sysmon sourcetype=XmlWinEventLog
SecurityEventindex=wineventlog sourcetype=XmlWinEventLog

Part of

More endpoint cases