CloudWatch log metric filter and alarm are not set for VPC changes Affecting CloudWatch service in AWS
Severity Framework
Snyk CCSS
Rule category
Monitoring / Accounts Monitoring
Is your enviroment affected by this misconfiguration?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsFrameworks
AWS-Well-Architected
CIS-AWS
HIPAA
ISO-27001
NIST-800-53
PCI-DSS
SOC-2
- Snyk ID SNYK-CC-00116
- credit Snyk Research Team
Description
Monitoring changes to VPCs helps ensure that VPC traffic flow is not being negatively impacted.
How to fix?
Create an aws_cloudwatch_log_metric_filter
and aws_cloudwatch_metric_alarm
with an appropriate pattern attribute set for an aws_cloudwatch_log_group
and aws_cloudtrail
set of resources.
Use the following pattern attribute set:
$.eventName=CreateVpc
$.eventName=DeleteVpc
$.eventName=ModifyVpcAttribute
$.eventName=AcceptVpcPeeringConnection
$.eventName=CreateVpcPeeringConnection
$.eventName=DeleteVpcPeeringConnection
$.eventName=RejectVpcPeeringConnection
$.eventName=AttachClassicLinkVpc
$.eventName=DetachClassicLinkVpc
$.eventName=DisableVpcClassicLink
$.eventName=EnableVpcClassicLink