AWS CloudTrail: ElastiCache Cache Security Group Created

Flags CloudTrail events indicating a new ElastiCache cache security group was created.

FreeReviewedSigma · Low · v5
Product
aws
Service
cloudtrail
Author
Austin Songer @austinsonger (SigmaHQ), DRL 1.1
Published
2021-07-24
Updated
2026-07-31

ATT&CK techniques

Persistence
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  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 identifies AWS CloudTrail events where an ElastiCache cache security group is created via the CreateCacheSecurityGroup API. Attackers or administrators could use this to alter network access boundaries for ElastiCache resources, potentially enabling unwanted connectivity. Detection relies on CloudTrail telemetry with eventSource set to elasticache.amazonaws.com and eventName set to CreateCacheSecurityGroup.

Related detections9 linkedT1136 — drag to rearrange
Possible Unauthenticated Admin Creation in Dynamicweb CVE-2022-25369
Renamed User Account Creation Disguised in a Computer Account (via security)
Malicious Fortinet APT Group Abuse on Windows - User (via security)
Malicious User Account Created by a Computer Account (via security)
Default Account Usage
Suspicious Entra Cross-Tenant Access or External User Invitation via Azure Audit (via azure)
Possible FortiWeb Authentication Bypass via Path Traversal to fwbcgi (via webserver)
Malicious SQL SA Admin User Enabled (via application)
Suspicious Hidden Account Creation - With Fast Deletion (via security)
AWS CloudTrail: ElastiCache Cache Security Group Created
Pivot detection · T1136 · 9 related

Changelog

v5
  1. v5
    Candidate ingested via manual entry.2026-07-31
  2. v4
    Candidate ingested via manual entry.2026-07-31
  3. v3
    Candidate ingested via manual entry.2026-07-31
  4. v2
    Candidate ingested via manual entry.2026-07-31
  5. v1
    No changelog recorded for this version.2026-07-30

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