Skip to main content

πŸ“ AWS CloudTrail S3 Bucket Policy Changes Monitoring is not enabled 🟒

  • Contextual name: πŸ“ S3 Bucket Policy Changes Monitoring is not enabled 🟒
  • ID: /ce/ca/aws/cloudtrail/s3-bucket-policy-changes-monitoring
  • Located in: πŸ“ AWS CloudTrail

Flags​

Our Metadata​

  • Policy Type: COMPLIANCE_POLICY
  • Policy Category:
    • SECURITY

Similar Policies​

Similar Internal Rules​

RulePoliciesFlags
βœ‰οΈ dec-x-c4cc9ff51

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 changes to S3 bucket policies.

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 S3 bucket policies may reduce time to detect and correct permissive policies on sensitive S3 buckets.

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:

  1. Identify the log group name configured for use with active multi-region CloudTrail:

  • List all CloudTrails:

... [see more](description.md)

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 S3 bucket policy 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 <s3_bucket_policy_changes_metric> --metric-transformations metricName= <s3_bucket_policy_changes_metric>, metricNamespace='CISBenchmark', metricValue=1 --filter-pattern '{ ($.eventSource = s3.amazonaws.com) && (($.eventName = PutBucketAcl) || ($.eventName = PutBucketPolicy) || ($.eventName = PutBucketCors) || ($.eventName = PutBucketLifecycle) || ($.eventName = PutBucketReplication) || ($.eventName = DeleteBucketPolicy) || ($.eventName = DeleteBucketCors) || ($.eventName = DeleteBucketLifecycle) || ($.eventName = DeleteBucketReplication)) }'

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

... see more

policy.yaml​

Open File

Linked Framework Sections​

SectionSub SectionsInternal RulesPoliciesFlags
πŸ’Ό CIS AWS v1.2.0 β†’ πŸ’Ό 3.8 Ensure a log metric filter and alarm exist for S3 bucket policy changes1
πŸ’Ό CIS AWS v1.3.0 β†’ πŸ’Ό 4.8 Ensure a log metric filter and alarm exist for S3 bucket policy changes1
πŸ’Ό CIS AWS v1.4.0 β†’ πŸ’Ό 4.8 Ensure a log metric filter and alarm exist for S3 bucket policy changes1
πŸ’Ό CIS AWS v1.5.0 β†’ πŸ’Ό 4.8 Ensure a log metric filter and alarm exist for S3 bucket policy changes - Level 1 (Automated)1
πŸ’Ό CIS AWS v2.0.0 β†’ πŸ’Ό 4.8 Ensure S3 bucket policy changes are monitored - Level 1 (Manual)1
πŸ’Ό CIS AWS v3.0.0 β†’ πŸ’Ό 4.8 Ensure S3 bucket policy changes are monitored - Level 1 (Manual)1
πŸ’Ό CIS AWS v4.0.0 β†’ πŸ’Ό 4.8 Ensure S3 bucket policy changes are monitored (Manual)1
πŸ’Ό CIS AWS v4.0.1 β†’ πŸ’Ό 4.8 Ensure S3 bucket policy changes are monitored (Manual)1
πŸ’Ό CIS AWS v5.0.0 β†’ πŸ’Ό 4.8 Ensure S3 bucket policy changes are monitored (Manual)1
πŸ’Ό Cloudaware Framework β†’ πŸ’Ό Alerting and Notification25
πŸ’Ό 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 β†’ πŸ’Ό 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 β†’ πŸ’Ό AU-12 Audit Record Generation44547