Suspicious Remote Command Execution to EC2 Instances via AWS SSM

PremiumReviewedSigma · Medium · v1
Product
aws
Service
cloudtrail
Author
HuntRule
Published
2026-10-17
Updated
2026-10-17

ATT&CK techniques

Execution → Lateral Movement
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Persistence

  5. Priv Esc

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule detects use of AWS Systems Manager to run commands or open interactive sessions on EC2 instances through SendCommand and StartSession events. Adversaries with valid cloud credentials abuse SSM to reach virtual machines without SSH or RDP as described in Unit 42 cloud VM attack path research. Detecting these calls exposes control-plane driven access to compute workloads.

Related detections6 linkedT1021.007 — drag to rearrange
Suspicious SSH Key Push to EC2 via EC2 Instance Connect
Suspicious SSM Session or Command Execution on EC2 Instance (via cloudtrail)
Suspicious EC2 Instance Connect SSH Public Key Push (via cloudtrail)
Suspicious Google Cloud Function Create or Update Triggering Build
Suspicious EC2 Serial Console SSH Public Key Push (via cloudtrail)
AWS CloudTrail GetSigninToken Requests with Suspected Console User-Agent
Suspicious Remote Command Execution to EC2 Instances via AWS SSM
Pivot detection · T1021.007 · 6 related

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.