AWS EC2 Network Access Control List Creation
editAWS EC2 Network Access Control List Creation
editIdentifies the creation of an AWS Elastic Compute Cloud (EC2) network access control list (ACL) or an entry in a network ACL with a specified rule number.
Rule type: query
Rule indices:
- filebeat-*
- logs-aws*
Severity: low
Risk score: 21
Runs every: 10 minutes
Searches indices from: now-60m (Date Math format, see also Additional look-back time)
Maximum alerts per execution: 100
References:
- https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ec2/create-network-acl.html
- https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_CreateNetworkAcl.html
- https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ec2/create-network-acl-entry.html
- https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_CreateNetworkAclEntry.html
Tags:
- Elastic
- Cloud
- AWS
- Continuous Monitoring
- SecOps
- Network Security
Version: 2 (version history)
Added (Elastic Stack release): 7.9.0
Last modified (Elastic Stack release): 7.10.0
Rule authors: Elastic
Rule license: Elastic License
Potential false positives
editNetwork ACLs may be created by a network administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. Network ACL creations from unfamiliar users or hosts should be investigated. If a known behavior is causing false positives, it can be excluded from the rule.
Investigation guide
editThe AWS Filebeat module must be enabled to use this rule.
Rule query
editevent.action:(CreateNetworkAcl or CreateNetworkAclEntry) and event.dataset:aws.cloudtrail and event.provider:ec2.amazonaws.com and event.outcome:success
Threat mapping
editFramework: MITRE ATT&CKTM
-
Tactic:
- Name: Persistence
- ID: TA0003
- Reference URL: https://attack.mitre.org/tactics/TA0003/
-
Technique:
- Name: Redundant Access
- ID: T1108
- Reference URL: https://attack.mitre.org/techniques/T1108/
Rule version history
edit- Version 2 (7.10.0 release)
-
- Formatting only