Network case
VPN account brute forced, admin access to file server
Five failed VPN logins for an IT admin account from one external IP, then one that worked. Follow it from the VPN to the file server.
- AdvancedLevel
- 35 minAbout
- New detailsEvery attempt
- KQL or SPLQuery language
Free. Read the briefing as a guest; investigating needs a free account.
The alert
VPN brute force followed by success
Five failed VPN logins for jjohnson from one external IP, then a success. It's an IT admin account and its VPN had no MFA - so once they were in, they already had rights on the file server. Didn't have time to dig further
From one version of the case: the company, the people and the details change with every attempt.
About this kind of alert
Remote access as the way in: guessed VPN passwords, and what an attacker does next inside the network.
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 |
|---|---|
CommonSecurityLog | index=firewall sourcetype=fgt_traffic |
SecurityEvent | index=wineventlog sourcetype=XmlWinEventLog |
Event | index=wineventlog sourcetype=XmlWinEventLog |
Sysmon | index=sysmon sourcetype=XmlWinEventLog |


