Skip to main content

📝 AWS CloudTrail Disable CMK or Schedule CMK Deletion Events Monitoring is not enabled 🟢

  • Contextual name: 📝 Disable or Schedule Deletion CMK Events Monitoring is not enabled 🟢
  • ID: /ce/ca/aws/cloudtrail/disable-or-schedule-deletion-cmk-events-monitoring
  • Located in: 📁 AWS CloudTrail

Flags​

Our Metadata​

  • Policy Type: COMPLIANCE_POLICY
  • Policy Category:
    • SECURITY

Similar Policies​

Similar Internal Rules​

RulePoliciesFlags
✉️ dec-x-f70dd11f1

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.

It is recommended that a metric filter and alarm be established for customer created CMKs which have changed state to disabled or scheduled deletion.

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.

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

Impact​

Creation, storage, and management of CMK may create additional labor requirements compared to the use of Provide Managed Keys.

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 disabled or scheduled for deletion CMK's 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 <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.

  1. 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 re-use the same topic for all monitoring alarms.

... see more

policy.yaml​

Open File

Linked Framework Sections​

SectionSub SectionsInternal RulesPoliciesFlags
💼 CIS AWS v1.2.0 → 💼 3.7 Ensure a log metric filter and alarm exist for disabling or scheduled deletion of customer created CMKs1
💼 CIS AWS v1.3.0 → 💼 4.7 Ensure a log metric filter and alarm exist for disabling or scheduled deletion of customer created CMKs1
💼 CIS AWS v1.4.0 → 💼 4.7 Ensure a log metric filter and alarm exist for disabling or scheduled deletion of customer created CMKs1
💼 CIS AWS v1.5.0 → 💼 4.7 Ensure a log metric filter and alarm exist for disabling or scheduled deletion of customer created CMKs - Level 2 (Automated)1
💼 CIS AWS v2.0.0 → 💼 4.7 Ensure disabling or scheduled deletion of customer created CMKs is monitored - Level 2 (Manual)1
💼 CIS AWS v3.0.0 → 💼 4.7 Ensure disabling or scheduled deletion of customer created CMKs is monitored - Level 2 (Manual)1
💼 CIS AWS v4.0.0 → 💼 4.7 Ensure disabling or scheduled deletion of customer created CMKs is monitored (Manual)1
💼 CIS AWS v4.0.1 → 💼 4.7 Ensure disabling or scheduled deletion of customer created CMKs is monitored (Manual)1
💼 CIS AWS v5.0.0 → 💼 4.7 Ensure disabling or scheduled deletion of customer created CMKs is monitored (Manual)1
💼 Cloudaware Framework → 💼 Alerting and Notification25
💼 Cloudaware Framework → 💼 Cryptographic Configuration8
💼 FedRAMP High Security Controls → 💼 AC-2(4) Automated Audit Actions (M)(H)113
💼 FedRAMP High Security Controls → 💼 AU-12 Audit Record Generation (L)(M)(H)247
💼 FedRAMP High Security Controls → 💼 SI-4(20) Privileged Users (H)4648
💼 FedRAMP Low Security Controls → 💼 AU-12 Audit Record Generation (L)(M)(H)47
💼 FedRAMP Moderate Security Controls → 💼 AC-2(4) Automated Audit Actions (M)(H)13
💼 FedRAMP Moderate Security Controls → 💼 AU-12 Audit Record Generation (L)(M)(H)47
💼 NIST CSF v2.0 → 💼 DE.CM-01: Networks and network services are monitored to find potentially adverse events83
💼 NIST CSF v2.0 → 💼 DE.CM-03: Personnel activity and technology usage are monitored to find potentially adverse events59
💼 NIST CSF v2.0 → 💼 DE.CM-09: Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events89
💼 NIST SP 800-53 Revision 5 → 💼 AC-2(4) Account Management _ Automated Audit Actions1113
💼 NIST SP 800-53 Revision 5 → 💼 AU-12 Audit Record Generation44547