Network case
Web shell on the public web server, pivot to SQL
w3wp.exe on the public web server spawned cmd.exe, and there is a new .aspx in the uploads folder.
- AdvancedLevel
- 35 minAbout
- New detailsEvery attempt
- KQL or SPLQuery language
Free. Read the briefing as a guest; investigating needs a free account.
The alert
IIS worker spawned a shell
w3wp.exe on RID-WEB-01 spawned cmd.exe and there's a new .aspx in the uploads folder. Looks like a web shell? Didn't check where it went
From one version of the case: the company, the people and the details change with every attempt.
About this kind of alert
Web shells: a script uploaded to an internet-facing web server that gives an attacker a command line, and a path further in.
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 |
|---|---|
Sysmon | index=sysmon sourcetype=XmlWinEventLog |
WebProxy_CL | index=proxy sourcetype=cisco:cloud_security:proxy |
SecurityEvent | index=wineventlog sourcetype=XmlWinEventLog |


