1200KM / sigma-rule
AWS ElastiCache Security Group Created — Sigma Rule
Sigma rule 4ae68615-866f-4304-b24b-ba048dfa5ca7. AWS ElastiCache Security Group Created — Sigma Rule. Detects when an ElastiCache security group has been created.
Rule metadata and linked tags
Author: Austin Songer @austinsonger. Source status: test; severity: low. Source dates: 2021-07-24 / 2022-10-09.
{
"product": "aws",
"service": "cloudtrail"
}Pinned original Sigma rule · Detection Rule License 1.1
Source SHA-256: 027461e043897cf30e90a6511e8f815ad52931e5fb472743a03d6d5b064b910a
Detection logic
Original source YAML. Source-tag agreement is not proof of complete semantic coverage. This rule has not been compiled for a SIEM backend or validated against live telemetry here.
title: AWS ElastiCache Security Group Created
id: 4ae68615-866f-4304-b24b-ba048dfa5ca7
status: test
description: Detects when an ElastiCache security group has been created.
references:
- https://github.com/elastic/detection-rules/blob/598f3d7e0a63221c0703ad9a0ea7e22e7bc5961e/rules/integrations/aws/persistence_elasticache_security_group_creation.toml
author: Austin Songer @austinsonger
date: 2021-07-24
modified: 2022-10-09
tags:
- attack.persistence
- attack.t1136
- attack.t1136.003
logsource:
product: aws
service: cloudtrail
detection:
selection:
eventSource: elasticache.amazonaws.com
eventName: 'CreateCacheSecurityGroup'
condition: selection
falsepositives:
- A ElastiCache security group may be created by a system or network administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. Security group creations from unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
level: low
False positives
- A ElastiCache security group may be created by a system or network administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. Security group creations from unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
Source references
Connected ecosystem references
Exact source-tagged techniques
Telemetry review
Read the original logsource above, then inspect the linked detection workspaces for technique-level sensor context. No per-rule telemetry equivalence is inferred.
Pinned research references. No browser attack runner, live simulation result or validated detector is asserted. Source mappings and validation limits are preserved. ATT&CK / Atomic provenance · Detection provenance.