Azure VM Serial Console Connection with Unusual User and ASN
Identifies a connection to the Azure Serial Console of a virtual machine (VM) by an identity and source network combination that has not been observed recently. The Serial Console provides text-based console access…
Description
Identifies a connection to the Azure Serial Console of a virtual machine (VM) by an identity and source network combination that has not been observed recently. The Serial Console provides text-based console access to a VM through the boot diagnostics serial port, independent of the VM's network state. Because it does not traverse the VM's network interface, a Serial Console session bypasses Network Security Groups (NSGs), Just-in-Time (JIT) access policies, and other network controls. An adversary with a privileged Azure RBAC role (for example Virtual Machine Contributor) and boot diagnostics enabled on the target can use the Serial Console to obtain an interactive session as SYSTEM (Windows) or root (Linux).
Detection logic
Its licence does not clear it for publishing here
Sunturai publishes a detection's own text where the licence it arrived under has been reviewed and permits it, and Elastic License 2.0 has not. The query as its source wrote it, its canonical form and the hash that pins this revision are in the workspace record.
Detection requirements
- Platform
- ContainersESXiIaaSIdentity ProviderLinuxmacOSNetwork DevicesOffice SuiteSaaSWindows
The rule states no platform. This is derived from the 2 ATT&CK techniques it maps to.
- Log source category
- event_index
Known benign triggers
- System or platform administrators may legitimately use the Serial Console to troubleshoot a VM that is unreachable over the network (boot failures, misconfigured firewall/NSG, lost SSH/RDP access). The first connection per identity and source ASN will alert; baseline expected break-glass principals and their corporate/VPN networks and exclude them if verified as authorized.
MITRE ATT&CK mappings
1 exclusive technique.This is coverage no other published rule has; it is not this rule's total technique count.
References
| Reference | Cited by |
|---|---|
| blog.pwnedlabs.io/diving-deep-into-azure-vm-attack-vectors | 6 |
| learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/serial-console-overview | Only this detection cites it |
| www.netspi.com/blog/technical-blog/adversary-simulation/7-ways-to-execute-command-on-azure-virtual-machine-virtual-machine-scale-sets/ | 6 |
From the source
- At source
- Open at source
- Upstream identifier
- 97266eb4-b8c3-4e3e-9417-7d0ace6b3dfe
- Tagged by the source as
- Data Source: AzureData Source: Azure Activity LogsDomain: CloudNoise: LowPerformance: FastPlatform: AzureResources: Investigation GuideRule Type: New TermsTactic: Defense EvasionTactic: Lateral MovementUse Case: Threat Detection
Licence
- Published under
- Elastic License 2.0Read the licence
- Attribution
- Required
Authorship
- Written by
- Published
- Sep 20, 2026
- Version
- 3