Suspicious AWS EC2 Instance Role Cloud Infrastructure Discovery
- Product
- aws
- Service
- cloudtrail
- Author
- HuntRule
- Published
- 2026-11-03
- Updated
- 2026-11-03
ATT&CK techniques
Cred Access → DiscoveryRecon
Resource Dev
Initial Access
Execution
Persistence
Priv Esc
Defense Evasion
Cred Access
Discovery
Lateral Movement
Collection
C2
Exfiltration
Impact
What it detects
This rule detects an assumed EC2 instance IAM role enumerating EC2 instances and security groups through the DescribeInstances and DescribeSecurityGroups APIs. In the Wiz Kubernetes privilege escalation case study an attacker who reached the Instance Metadata Service from a compromised EKS pod used the stolen instance role to perform cloud infrastructure reconnaissance. This is important because such discovery from a workload role that normally does not enumerate infrastructure is an early sign of a stolen credential being abused for lateral movement.
Reporting behind it
Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.
Unlock this rule to view and copy it
The detection logic is included with a plan. Everything else — context, mappings and implementation details — stays free on this page.
Signing in gives you 3 unlocks to spend on any rule in the library. No card, and they do not expire.
Also included
Unlocked rules convert on this page — to Splunk SPL or Splunk — Raw Index SPL or Microsoft Sentinel KQL or Microsoft Sentinel ASIM ASIM KQL or Microsoft Defender XDR KQL or Elastic Security KQL or Elastic Security Lucene or Elastic Security ES|QL or CrowdStrike Falcon CQL or SentinelOne PowerQuery or Palo Alto Cortex XDR XQL or Carbon Black Cloud Platform Search or Carbon Black EDR Process Search or Google Security Operations UDM Search or IBM QRadar AQL or Sumo Logic Cloud SIEM Rules expression or Rapid7 InsightIDR LEQL or Graylog Search or OpenSearch Lucene or OpenSearch PPL PPL or Grafana Loki LogQL or SQLite SQL or Zircolite SQLite — with the log-source profile the engine picked, the field map it used, and everything it could not express. Converting a rule you have unlocked costs no further credit.