Skip to main content

📝 AWS S3 Bucket Server Access Logging is not enabled 🟢

  • Contextual name: 📝 Bucket Server Access Logging is not enabled 🟢
  • ID: /ce/ca/aws/s3/bucket-server-access-logging
  • Located in: 📁 AWS S3

Flags​

Our Metadata​

  • Policy Type: COMPLIANCE_POLICY
  • Policy Category:
    • SECURITY

Similar Policies​

Similar Internal Rules​

RulePoliciesFlags
✉️ dec-x-e00143332

Logic​

Description​

Open File

Description​

AWS S3 Server Access Logging enables you to track and analyze access to your S3 buckets, providing detailed records of requests made to the objects.

Rational​

When Server Access Logging is enabled for an S3 (source) bucket, Amazon S3 starts to capture access logs and store them in a separate (destination) bucket designated for logging purposes. These logs are typically stored in a standardized format and can be easily analyzed using various AWS tools or third-party services.

The access logs generated by S3 contain information such as:

  • Requester's IP Address: The IP address of the entity making the request to access the S3 bucket.
  • Request Timestamp: The date and time when the request was made.
  • Requested Resource: The specific object within the S3 bucket that was accessed.
  • HTTP Method: The method used for the request (e.g., GET, PUT, DELETE).
  • Response Status: The HTTP status code returned by S3 in response to the request.
  • Bytes Sent/Received: The number of bytes sent from S3 to the requester and received by S3 from the requester.

... see more

Remediation​

Open File

Remediation​

Prerequisites​

  • The destination (target) bucket must be in the same AWS Region and AWS account as the source bucket.
  • Your destination bucket should not have server access logging enabled.
  • S3 buckets that have S3 Object Lock enabled can't be used as destination buckets
  • The destination bucket must not have Requester Pays enabled.
  • Default server-side encryption with AWS Key Management Service (AWS KMS) keys (SSE-KMS) is not supported.

From Command Line​

It's recommended that you create a dedicated logging bucket in each AWS Region that you have S3 buckets in. Then have your Amazon S3 access logs delivered to that S3 bucket. Distinguish buckets from each other by adding a prefix.

Step 1. Grant permissions for server access log delivery by using a bucket policy​

To grant permissions to the logging service principal, use the put-bucket-policy command. Replace {{your-log-destination-bucket}} with the name of your destination bucket.

aws s3api put-bucket-policy --bucket {{your-log-destination-bucket}} --policy file://{{policy.json}}

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

policy.yaml​

Open File

Linked Framework Sections​

SectionSub SectionsInternal RulesPoliciesFlags
💼 APRA CPG 234 → 💼 67a network and user profiling that establishes a baseline of normal activity which, when combined with logging and alerting mechanisms, can enable detection of anomalous activity;1922
💼 APRA CPG 234 → 💼 h. audit logging and monitoring of access to information assets by all users;89
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [S3.9] S3 general purpose buckets should have server access logging enabled12
💼 Cloudaware Framework → 💼 Logging and Monitoring Configuration59
💼 FedRAMP High Security Controls → 💼 AC-2(4) Automated Audit Actions (M)(H)16
💼 FedRAMP High Security Controls → 💼 AC-6(9) Log Use of Privileged Functions (M)(H)726
💼 FedRAMP High Security Controls → 💼 AU-2 Event Logging (L)(M)(H)17
💼 FedRAMP High Security Controls → 💼 AU-3 Content of Audit Records (L)(M)(H)128
💼 FedRAMP High Security Controls → 💼 AU-6 Audit Record Review, Analysis, and Reporting (L)(M)(H)62030
💼 FedRAMP High Security Controls → 💼 AU-6(3) Correlate Audit Record Repositories (M)(H)8
💼 FedRAMP High Security Controls → 💼 AU-6(4) Central Review and Analysis (H)8
💼 FedRAMP High Security Controls → 💼 AU-10 Non-repudiation (H)7
💼 FedRAMP High Security Controls → 💼 AU-11 Audit Record Retention (L)(M)(H)1618
💼 FedRAMP High Security Controls → 💼 AU-12 Audit Record Generation (L)(M)(H)265
💼 FedRAMP High Security Controls → 💼 CA-7 Continuous Monitoring (L)(M)(H)210
💼 FedRAMP High Security Controls → 💼 CM-3 Configuration Change Control (M)(H)425
💼 FedRAMP High Security Controls → 💼 SI-4(20) Privileged Users (H)4851
💼 FedRAMP Low Security Controls → 💼 AU-2 Event Logging (L)(M)(H)17
💼 FedRAMP Low Security Controls → 💼 AU-3 Content of Audit Records (L)(M)(H)14
💼 FedRAMP Low Security Controls → 💼 AU-6 Audit Record Review, Analysis, and Reporting (L)(M)(H)24
💼 FedRAMP Low Security Controls → 💼 AU-11 Audit Record Retention (L)(M)(H)18
💼 FedRAMP Low Security Controls → 💼 AU-12 Audit Record Generation (L)(M)(H)65
💼 FedRAMP Low Security Controls → 💼 CA-7 Continuous Monitoring (L)(M)(H)110
💼 FedRAMP Moderate Security Controls → 💼 AC-2(4) Automated Audit Actions (M)(H)16
💼 FedRAMP Moderate Security Controls → 💼 AC-6(9) Log Use of Privileged Functions (M)(H)26
💼 FedRAMP Moderate Security Controls → 💼 AU-2 Event Logging (L)(M)(H)17
💼 FedRAMP Moderate Security Controls → 💼 AU-3 Content of Audit Records (L)(M)(H)128
💼 FedRAMP Moderate Security Controls → 💼 AU-6 Audit Record Review, Analysis, and Reporting (L)(M)(H)230
💼 FedRAMP Moderate Security Controls → 💼 AU-6(3) Correlate Audit Record Repositories (M)(H)8
💼 FedRAMP Moderate Security Controls → 💼 AU-11 Audit Record Retention (L)(M)(H)18
💼 FedRAMP Moderate Security Controls → 💼 AU-12 Audit Record Generation (L)(M)(H)65
💼 FedRAMP Moderate Security Controls → 💼 CA-7 Continuous Monitoring (L)(M)(H)210
💼 FedRAMP Moderate Security Controls → 💼 CM-3 Configuration Change Control (M)(H)219
💼 GDPR → 💼 Art. 30 Records of processing activities23
💼 ISO/IEC 27001:2013 → 💼 A.12.4.1 Event logging1518
💼 NIST CSF v1.1 → 💼 DE.AE-2: Detected events are analyzed to understand attack targets and methods1823
💼 NIST CSF v1.1 → 💼 DE.AE-3: Event data are collected and correlated from multiple sources and sensors1837
💼 NIST CSF v1.1 → 💼 DE.CM-1: The network is monitored to detect potential cybersecurity events1841
💼 NIST CSF v1.1 → 💼 DE.CM-3: Personnel activity is monitored to detect potential cybersecurity events2026
💼 NIST CSF v1.1 → 💼 DE.CM-7: Monitoring for unauthorized personnel, connections, devices, and software is performed1823
💼 NIST CSF v1.1 → 💼 DE.DP-4: Event detection information is communicated2932
💼 NIST CSF v1.1 → 💼 ID.SC-4: Suppliers and third-party partners are routinely assessed using audits, test results, or other forms of evaluations to confirm they are meeting their contractual obligations1519
💼 NIST CSF v1.1 → 💼 PR.PT-1: Audit/log records are determined, documented, implemented, and reviewed in accordance with policy1632
💼 NIST CSF v1.1 → 💼 RS.AN-1: Notifications from detection systems are investigated1823
💼 NIST CSF v1.1 → 💼 RS.CO-2: Incidents are reported consistent with established criteria1922
💼 NIST CSF v2.0 → 💼 DE.AE-02: Potentially adverse events are analyzed to better understand associated activities31
💼 NIST CSF v2.0 → 💼 DE.AE-03: Information is correlated from multiple sources46
💼 NIST CSF v2.0 → 💼 DE.AE-06: Information on adverse events is provided to authorized staff and tools32
💼 NIST CSF v2.0 → 💼 DE.AE-07: Cyber threat intelligence and other contextual information are integrated into the analysis37
💼 NIST CSF v2.0 → 💼 DE.CM-01: Networks and network services are monitored to find potentially adverse events115
💼 NIST CSF v2.0 → 💼 DE.CM-02: The physical environment is monitored to find potentially adverse events10
💼 NIST CSF v2.0 → 💼 DE.CM-03: Personnel activity and technology usage are monitored to find potentially adverse events81
💼 NIST CSF v2.0 → 💼 DE.CM-06: External service provider activities and services are monitored to find potentially adverse events31
💼 NIST CSF v2.0 → 💼 DE.CM-09: Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events134
💼 NIST CSF v2.0 → 💼 GV.SC-07: The risks posed by a supplier, their products and services, and other third parties are understood, recorded, prioritized, assessed, responded to, and monitored over the course of the relationship26
💼 NIST CSF v2.0 → 💼 ID.IM-01: Improvements are identified from evaluations20
💼 NIST CSF v2.0 → 💼 ID.IM-02: Improvements are identified from security tests and exercises, including those done in coordination with suppliers and relevant third parties33
💼 NIST CSF v2.0 → 💼 ID.IM-03: Improvements are identified from execution of operational processes, procedures, and activities34
💼 NIST CSF v2.0 → 💼 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded26
💼 NIST CSF v2.0 → 💼 ID.RA-07: Changes and exceptions are managed, assessed for risk impact, recorded, and tracked28
💼 NIST CSF v2.0 → 💼 ID.RA-10: Critical suppliers are assessed prior to acquisition26
💼 NIST CSF v2.0 → 💼 RC.CO-04: Public updates on incident recovery are shared using approved methods and messaging22
💼 NIST CSF v2.0 → 💼 RS.CO-02: Internal and external stakeholders are notified of incidents30
💼 NIST CSF v2.0 → 💼 RS.MA-02: Incident reports are triaged and validated24
💼 NIST SP 800-53 Revision 4 → 💼 AU-2 AUDIT EVENTS434
💼 NIST SP 800-53 Revision 5 → 💼 AC-2(4) Account Management _ Automated Audit Actions1416
💼 NIST SP 800-53 Revision 5 → 💼 AC-4(26) Information Flow Enforcement _ Audit Filtering Actions9
💼 NIST SP 800-53 Revision 5 → 💼 AC-6(9) Least Privilege _ Log Use of Privileged Functions1719
💼 NIST SP 800-53 Revision 5 → 💼 AU-2 Event Logging417
💼 NIST SP 800-53 Revision 5 → 💼 AU-3 Content of Audit Records31328
💼 NIST SP 800-53 Revision 5 → 💼 AU-6(3) Audit Record Review, Analysis, and Reporting _ Correlate Audit Record Repositories8
💼 NIST SP 800-53 Revision 5 → 💼 AU-6(4) Audit Record Review, Analysis, and Reporting _ Central Review and Analysis8
💼 NIST SP 800-53 Revision 5 → 💼 AU-10 Non-repudiation57
💼 NIST SP 800-53 Revision 5 → 💼 AU-12 Audit Record Generation44765
💼 NIST SP 800-53 Revision 5 → 💼 CA-7 Continuous Monitoring610
💼 NIST SP 800-53 Revision 5 → 💼 CM-3 Configuration Change Control81725
💼 NIST SP 800-53 Revision 5 → 💼 SC-7(9) Boundary Protection _ Restrict Threatening Outgoing Communications Traffic12
💼 NIST SP 800-53 Revision 5 → 💼 SI-3(8) Malicious Code Protection _ Detect Unauthorized Commands5
💼 NIST SP 800-53 Revision 5 → 💼 SI-4(20) System Monitoring _ Privileged Users5
💼 NIST SP 800-53 Revision 5 → 💼 SI-7(8) Software, Firmware, and Information Integrity _ Auditing Capability for Significant Events8
💼 PCI DSS v3.2.1 → 💼 10.2 Implement automated audit trails for all system components.7625
💼 PCI DSS v4.0.1 → 💼 10.2.1 Audit logs are enabled and active for all system components and cardholder data.724
💼 PCI DSS v4.0 → 💼 10.2.1 Audit logs are enabled and active for all system components and cardholder data.7124
💼 SOC 2 → 💼 CC6.1-8 Manages Identification and Authentication1824