Skip to main content

🛡️ AWS CloudTrail Security Group Changes Monitoring is not enabled🟢⚪

  • Contextual name: 🛡️ Security Group Changes Monitoring is not enabled🟢⚪
  • ID: /ce/ca/aws/cloudtrail/security-group-changes-monitoring
  • Tags:
  • Policy Type: COMPLIANCE_POLICY
  • Policy Categories: SECURITY

Similar Policies​

Similar Internal Rules​

RulePoliciesFlags
✉️ dec-x-3cfa53061

Description​

Open File

Description​

Real-time monitoring of API calls can be achieved by directing CloudTrail Logs to CloudWatch Logs or an external Security Information and Event Management (SIEM) environment, and establishing corresponding metric filters and alarms.

Security groups are stateful packet filters that control ingress and egress traffic within a VPC.

It is recommended that a metric filter and alarm be established to detect changes to security groups.

Rationale​

CloudWatch is an AWS native service that allows you to observe and monitor resources and applications. CloudTrail logs can also be sent to an external Security Information and Event Management (SIEM) environment for monitoring and alerting.

Monitoring changes to security groups will help ensure that resources and services are not unintentionally exposed.

Impact​

This may require additional 'tuning' to eliminate false positive and filter out expected activity so anomalies are easier to detect.

Audit​

If you are using CloudTrails and CloudWatch, perform the following to ensure that there is at least one active multi-region CloudTrail with prescribed metric filters and alarms configured:

... see more

Remediation​

Open File

Remediation​

If you are using CloudTrails and CloudWatch, perform the following to setup the metric filter, alarm, SNS topic, and subscription:

  1. Create a metric filter based on filter pattern provided which checks for security groups changes and the <cloudtrail_log_group_name> taken from audit step 1:
aws logs put-metric-filter --log-group-name "<cloudtrail_log_group_name>" --filter-name <security_group_changes_metric> --metric-transformations metricName=<security_group_changes_metric>, metricNamespace="CISBenchmark", metricValue=1 --filter-pattern "{ ($.eventName = AuthorizeSecurityGroupIngress) || ($.eventName = AuthorizeSecurityGroupEgress) || ($.eventName = RevokeSecurityGroupIngress) || ($.eventName = RevokeSecurityGroupEgress) || ($.eventName = CreateSecurityGroup) || ($.eventName = DeleteSecurityGroup) }"

Note: You can choose your own metricName and metricNamespace strings. Using the same metricNamespace for all Foundations Benchmark metrics will group them together.

  1. Create an SNS topic that the alarm will notify:

... see more

policy.yaml​

Open File

Linked Framework Sections​

SectionSub SectionsInternal RulesPoliciesFlagsCompliance
💼 CIS AWS v1.2.0 → 💼 3.10 Ensure a log metric filter and alarm exist for security group changes1no data
💼 CIS AWS v1.3.0 → 💼 4.10 Ensure a log metric filter and alarm exist for security group changes1no data
💼 CIS AWS v1.4.0 → 💼 4.10 Ensure a log metric filter and alarm exist for security group changes1no data
💼 CIS AWS v1.5.0 → 💼 4.10 Ensure a log metric filter and alarm exist for security group changes - Level 2 (Automated)1no data
💼 CIS AWS v2.0.0 → 💼 4.10 Ensure security group changes are monitored - Level 2 (Manual)1no data
💼 CIS AWS v3.0.0 → 💼 4.10 Ensure security group changes are monitored - Level 2 (Manual)1no data
💼 CIS AWS v4.0.0 → 💼 4.10 Ensure security group changes are monitored (Manual)1no data
💼 CIS AWS v4.0.1 → 💼 4.10 Ensure security group changes are monitored (Manual)1no data
💼 CIS AWS v5.0.0 → 💼 4.10 Ensure security group changes are monitored (Manual)1no data
💼 CIS AWS v6.0.0 → 💼 5.10 Ensure security group changes are monitored (Manual)1no data
💼 Cloudaware Framework → 💼 Alerting and Notification27no data
💼 FedRAMP High Security Controls → 💼 AU-12 Audit Record Generation (L)(M)(H)265no data
💼 FedRAMP High Security Controls → 💼 SI-4(20) Privileged Users (H)4851no data
💼 FedRAMP Low Security Controls → 💼 AU-12 Audit Record Generation (L)(M)(H)65no data
💼 FedRAMP Moderate Security Controls → 💼 AU-12 Audit Record Generation (L)(M)(H)65no data
💼 NIST CSF v2.0 → 💼 DE.CM-01: Networks and network services are monitored to find potentially adverse events145no data
💼 NIST CSF v2.0 → 💼 DE.CM-03: Personnel activity and technology usage are monitored to find potentially adverse events85no data
💼 NIST CSF v2.0 → 💼 DE.CM-09: Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events142no data
💼 NIST SP 800-53 Revision 5 → 💼 AU-12 Audit Record Generation44765no data