Detections
Analytics

4.7 Ensure disabling or scheduled deletion of customer created CMKs is monitored

Warning! Audit Deprecated

This audit has been deprecated and will be removed in a future update.

View Next Audit Version

Information

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 recommended that a metric filter and alarm be established for customer-created CMKs that have changed state to disabled or are scheduled for deletion.

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.

Data encrypted with disabled or deleted keys will no longer be accessible. Changes in the state of a CMK should be monitored to ensure that the change is intentional.

NOTE: Nessus has not performed this check. Please review the benchmark to ensure target compliance.

Solution

If you are using CloudTrail trails and CloudWatch, perform the following steps to set up the metric filter, alarm, SNS topic, and subscription:

 -

Create a metric filter based on the provided filter pattern that checks for CMKs that have been disabled or scheduled for deletion and uses the <trail-log-group-name> taken from audit step 1:

aws logs put-metric-filter --log-group-name <trail-log-group-name> --filter-name <disable-or-delete-cmk-changes-metric> --metric-transformations metricName=<disable-or-delete-cmk-changes-metric>,metricNamespace='CISBenchmark',metricValue=1 --filter-pattern '{($.eventSource = kms.amazonaws.com) && (($.eventName=DisableKey)||($.eventName=ScheduleKeyDeletion)) }'

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

 -

Create an SNS topic that the alarm will notify:

aws sns create-topic --name <sns-topic-name>

Note : You can execute this command once and then reuse the same topic for all monitoring alarms.

Note : Capture the TopicArn that is displayed when creating the SNS topic in step 2.

 -

Create an SNS subscription for the topic created in step 2:

aws sns subscribe --topic-arn <sns-topic-arn> --protocol <sns-protocol> --notification-endpoint <sns-subscription-endpoints>

Note : You can execute this command once and then reuse the same subscription for all monitoring alarms.

 -

Create an alarm that is associated with the CloudWatch Logs metric filter created in step 1 and the SNS topic created in step 2:

aws cloudwatch put-metric-alarm --alarm-name <disable-or-delete-cmk-changes-alarm> --metric-name <disable-or-delete-cmk-changes-metric> --statistic Sum --period 300 --threshold 1 --comparison-operator GreaterThanOrEqualToThreshold --evaluation-periods 1 --namespace 'CISBenchmark' --alarm-actions <sns-topic-arn>

Impact:

Creation, storage, and management of CMK may require additional labor compared to the use of AWS-managed keys.

See Also

https://workbench.cisecurity.org/benchmarks/19631

Item Details

References: CSCv7|6.3

Plugin: amazon_aws

Control ID: 24cfa4026e023666b56f2bc9b8b705e545e1154d42c1fc040cfb9a5485037051