📝 AWS CloudTrail VPC Changes Monitoring is not enabled 🟢
- Contextual name: 📝 VPC Changes Monitoring is not enabled 🟢
- ID:
/ce/ca/aws/cloudtrail/vpc-changes-monitoring - Located in: 📁 AWS CloudTrail
Flags
Our Metadata
- Policy Type:
COMPLIANCE_POLICY - Policy Category:
SECURITY
Similar Policies
- Cloud Conformity
- Internal
dec-x-9dc82014
Similar Internal Rules
| Rule | Policies | Flags |
|---|---|---|
| ✉️ dec-x-9dc82014 | 1 |
Description
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.
It is possible to have more than one VPC within an account; additionally, it is also possible to create a peer connection between two VPCs, enabling network traffic to route between them.
It is recommended that a metric filter and alarm be established for changes made to VPCs.
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.
VPCs in AWS are logically isolated virtual networks that can be used to launch AWS resources. Monitoring changes to VPC configuration will help ensure VPC traffic flow is not getting impacted. Changes to VPCs can impact network accessibility from the public internet and additionally impact VPC traffic flow to and from resources launched in the VPC.
... see more
Remediation
Remediation
If you are using CloudTrails and CloudWatch, perform the following to setup the metric filter, alarm, SNS topic, and subscription:
- Create a metric filter based on filter pattern provided which checks for VPC 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 <vpc_changes_metric> --metric-transformations metricName= <vpc_changes_metric>, metricNamespace='CISBenchmark', metricValue=1 --filter-pattern '{ ($.eventName = CreateVpc) || ($.eventName = DeleteVpc) || ($.eventName = ModifyVpcAttribute) || ($.eventName = AcceptVpcPeeringConnection) || ($.eventName = CreateVpcPeeringConnection) || ($.eventName = DeleteVpcPeeringConnection) || ($.eventName = RejectVpcPeeringConnection) || ($.eventName = AttachClassicLinkVpc) || ($.eventName = DetachClassicLinkVpc) || ($.eventName = DisableVpcClassicLink) || ($.eventName = EnableVpcClassicLink) }'Note: You can choose your own metricName and metricNamespace strings. Using the same metricNamespace for all Foundations Benchmark metrics will group them together.
... see more