Network case · built on 2026 attacks
SSH switched on for a production hypervisor
SSH was switched on for a production hypervisor, with no maintenance window on the calendar. Patching, or the step before every VM goes dark?
- AdvancedLevel
- 35 minAbout
- 3 versionsEvery attempt
- KQL or SPLQuery language
Free. Read the briefing as a guest; investigating needs a free account.
The alert
ESXi: SSH access enabled on a production host
SSH was switched on for esxi-prod-03. We only expect that in a maintenance window and I cannot find one on the calendar. Could be patching, could be bad.
From one version of the case: the company, the people and the details change with every attempt.
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, then prove it: answer questions with values from the logs.
- 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.
Each attempt is another version: another company, other people, and sometimes another outcome. One version may be an attack, another a false alarm. You cannot learn the answer, only the method.
Logs you will query
| Microsoft Sentinel | Splunk |
|---|---|
Syslog | index=linux sourcetype=linux_secure |
What it is built on
Hypervisor takeovers: stolen vSphere admin rights, SSH switched on, then ransomware for every VM at once or a stolen domain database. The companies, people, domains and addresses are fictional; the behaviour and the log formats follow the public reporting.


