AWS EC2 Serial Console Access Enabled
Detects when EC2 Serial Console Access is enabled for an AWS account. The EC2 Serial Console provides direct, text-based access to an instance's serial port, bypassing the network layer entirely. While useful for…
Description
Detects when EC2 Serial Console Access is enabled for an AWS account. The EC2 Serial Console provides direct, text-based access to an instance's serial port, bypassing the network layer entirely. While useful for troubleshooting boot issues or network misconfigurations, enabling serial console access in production environments is rare and potentially dangerous. Adversaries may enable this feature to establish an out-of-band communication channel that evades network-based security monitoring, firewalls, and VPC controls. This access method can be used for persistent backdoor access or to interact with compromised instances without triggering network-based detection mechanisms.
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 SuiteWindows
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
- Administrators may legitimately enable serial console access during troubleshooting of instances with boot issues, network misconfigurations, or SSH access problems. Verify whether the user identity, user agent, and/or source IP should be making changes in your environment. Serial console access enablement by unfamiliar users or from unexpected locations should be investigated. If this is expected behavior for troubleshooting, it can be exempted from the rule, but ensure serial console access is disabled after troubleshooting is complete.
MITRE ATT&CK mappings
0 exclusive techniques.This is coverage no other published rule has; it is not this rule's total technique count.
References
| Reference | Cited by |
|---|---|
| docs.aws.amazon.com/AWSEC2/latest/APIReference/API_EnableSerialConsoleAccess.html | Only this detection cites it |
| docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-serial-console.html | Only this detection cites it |
| permiso.io/blog/lucr-3-scattered-spider-getting-saas-y-in-the-cloud | 7 |
From the source
- At source
- Open at source
- Upstream identifier
- e9fe3645-f588-43d6-99f5-437b3ef56f25
- Tagged by the source as
- Data Source: Amazon Web ServicesData Source: AWSData Source: AWS CloudTrailData Source: AWS EC2Domain: CloudNoise: LowPerformance: NormalPlatform: AWSResources: Investigation GuideRule Type: Custom Query (KQL)Service: AWS EC2Tactic: Defense Evasion
Licence
- Published under
- Elastic License 2.0Read the licence
- Attribution
- Required
Authorship
- Written by
- Published
- Sep 20, 2026
- Version
- 3