Skip to main content

🛡️ AWS CloudTrail Configuration Changes Monitoring is not enabled🟢⚪

  • Contextual name: 🛡️ Configuration Changes Monitoring is not enabled🟢⚪
  • ID: /ce/ca/aws/cloudtrail/configuration-changes-monitoring
  • Tags:
  • Policy Type: COMPLIANCE_POLICY
  • Policy Categories: SECURITY

Similar Policies​

Similar Internal Rules​

RulePoliciesFlags
✉️ dec-x-b10287411

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, where metric filters and alarms can be established.

It is recommended that a metric filter and alarm be utilized for detecting changes to CloudTrail's configurations.

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.

Monitoring changes to CloudTrail's configuration will help ensure sustained visibility into the activities performed in the AWS account.

Impact​

Ensuring that changes to CloudTrail configurations are monitored enhances security by maintaining the integrity of logging mechanisms. Automated monitoring can provide real-time alerts; however, it may require additional setup and resources to configure and manage these alerts effectively. These steps can be performed manually within a

... 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 cloudtrail configuration 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 <cloudtrail_cfg_changes_metric> --metric-transformations metricName=<cloudtrail_cfg_changes_metric>, metricNamespace='CISBenchmark', metricValue=1 --filter-pattern '{ ($.eventName = CreateTrail) || ($.eventName = UpdateTrail) || ($.eventName = DeleteTrail) || ($.eventName = StartLogging) || ($.eventName = StopLogging) }'

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 RulesPoliciesFlagsCompliance
💼 CIS AWS v1.2.0 → 💼 3.5 Ensure a log metric filter and alarm exist for CloudTrail configuration changes1no data
💼 CIS AWS v1.3.0 → 💼 4.5 Ensure a log metric filter and alarm exist for CloudTrail configuration changes1no data
💼 CIS AWS v1.4.0 → 💼 4.5 Ensure a log metric filter and alarm exist for CloudTrail configuration changes1no data
💼 CIS AWS v1.5.0 → 💼 4.5 Ensure a log metric filter and alarm exist for CloudTrail configuration changes - Level 1 (Automated)1no data
💼 CIS AWS v2.0.0 → 💼 4.5 Ensure CloudTrail configuration changes are monitored - Level 1 (Manual)1no data
💼 CIS AWS v3.0.0 → 💼 4.5 Ensure CloudTrail configuration changes are monitored - Level 1 (Manual)1no data
💼 CIS AWS v4.0.0 → 💼 4.5 Ensure CloudTrail configuration changes are monitored (Manual)1no data
💼 CIS AWS v4.0.1 → 💼 4.5 Ensure CloudTrail configuration changes are monitored (Manual)1no data
💼 CIS AWS v5.0.0 → 💼 4.5 Ensure CloudTrail configuration changes are monitored (Manual)1no data
💼 CIS AWS v6.0.0 → 💼 5.5 Ensure CloudTrail configuration changes are monitored (Manual)1no data
💼 Cloudaware Framework → 💼 Alerting and Notification27no data
💼 FedRAMP High Security Controls → 💼 AU-12 Audit Record Generation (L)(M)(H)265no data
💼 FedRAMP High Security Controls → 💼 SI-4(20) Privileged Users (H)4851no data
💼 FedRAMP Low Security Controls → 💼 AU-12 Audit Record Generation (L)(M)(H)65no data
💼 FedRAMP Moderate Security Controls → 💼 AU-12 Audit Record Generation (L)(M)(H)65no data
💼 NIST CSF v2.0 → 💼 DE.CM-01: Networks and network services are monitored to find potentially adverse events150no data
💼 NIST CSF v2.0 → 💼 DE.CM-03: Personnel activity and technology usage are monitored to find potentially adverse events85no data
💼 NIST CSF v2.0 → 💼 DE.CM-09: Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events149no data
💼 NIST SP 800-53 Revision 5 → 💼 AU-12 Audit Record Generation44765no data