No CloudWatch alarm for AWS Config configuration changes

Severity: Medium
Service: Monitoring and alarms
Check ID: CLOUDWATCH_ALARM_CONFIG_CHANGES

What this check finds

No metric filter and alarm detect AWS Config recorder disable or delivery channel deletion events. Disabling Config silently breaks compliance monitoring. CIS v1.4 §4.9.

Passing looks like: CloudWatch alarm for AWS Config changes configured.

How to fix it

Create a metric filter covering StopConfigurationRecorder, DeleteDeliveryChannel, PutDeliveryChannel, PutConfigurationRecorder events and add an alarm.

Compliance controls it is evidence for

A failing result counts against these controls in KloudLytics; a passing one is evidence towards them. How compliance mapping works

Compliance controls mapped to No CloudWatch alarm for AWS Config configuration changes
Framework	Controls
CIS AWS Foundations Benchmark v5.0.0	4.9 Ensure AWS Config configuration changes are monitored
NIST SP 800-53 Rev5 (Moderate)	AU-6 Audit Record Review, Analysis, and Reporting CM-3 Configuration Change Control SI-4 System Monitoring
NIST Cybersecurity Framework 2.0	PR.PS-01 Configuration management practices are applied DE.AE-02 Adverse events are analyzed DE.CM-01 Networks are monitored
ISO/IEC 27001:2022 Annex A	A.8.9 Configuration management A.8.16 Monitoring activities A.8.32 Change management

Checked on every scan

KloudLytics runs this check each time it scans a connected AWS account, through a read-only role, and lists every affected resource with its region. On Pro and Business a fix is written for the specific resource rather than the general case above. The exact access it needs

More Monitoring and alarms checks

All Monitoring and alarms checks