AWS Security Group Configuration Change Detectionedit

Identifies a change to an AWS Security Group Configuration. A security group is like a virtual firewall, and modifying configurations may allow unauthorized access. Threat actors may abuse this to establish persistence, exfiltrate data, or pivot in an AWS environment.

Rule type: query

Rule indices:

  • filebeat-*
  • logs-aws*

Severity: low

Risk score: 21

Runs every: 10 minutes

Searches indices from: now-30m (Date Math format, see also Additional look-back time)

Maximum alerts per execution: 100



  • Elastic
  • Cloud
  • AWS
  • Continuous Monitoring
  • SecOps
  • Network Security

Version: 2 (version history)

Added (Elastic Stack release): 7.15.0

Last modified (Elastic Stack release): 7.16.0

Rule authors: Elastic, Austin Songer

Rule license: Elastic License v2

Potential false positivesedit

A 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.

Investigation guideedit

## Config

The AWS Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.

Rule queryedit

event.dataset:aws.cloudtrail and and
event.action:(AuthorizeSecurityGroupEgress or CreateSecurityGroup or
ModifyInstanceAttribute or ModifySecurityGroupRules or
RevokeSecurityGroupEgress or RevokeSecurityGroupIngress) and

Threat mappingedit


Rule version historyedit

Version 2 (7.16.0 release)
  • Formatting only