📝 Google Logging Log Sink exports logs to a Storage Bucket without Bucket Lock 🟢

• Contextual name: 📝 og Sink exports logs to a Storage Bucket without Bucket Lock 🟢
• ID: /ce/ca/google/logging/storage-bucket-retention-policy
• Located in: 📁 Google Logging

Flags

• 🟢 Policy with categories
• 🟢 Policy with type
• 🟢 Production policy

Our Metadata

• Policy Type: COMPLIANCE_POLICY
• Policy Category:
  • SECURITY

Similar Policies

• Cloud Conformity
  • Configure Retention Policies with Bucket Lock

Logic

• 🧠 prod.logic.yaml 🟢
  • 📗 Google Logging Log Sink
  • 🔌 Google Storage Bucket - object.extracts.yaml
  • 🔌 Google Logging Log Sink - object.extracts.yaml
  • 🧪 test-data.json

Description

Open File

Description

Enabling retention policies on log buckets will protect logs stored in cloud storage buckets from being overwritten or accidentally deleted. It is recommended to set up retention policies and configure Bucket Lock on all storage buckets that are used as log sinks.

Rationale

Logs can be exported by creating one or more sinks that include a log filter and a destination. As Cloud Logging receives new log entries, they are compared against each sink. If a log entry matches a sink's filter, then a copy of the log entry is written to the destination.

Sinks can be configured to export logs in storage buckets. It is recommended to configure a data retention policy for these cloud storage buckets and to lock the data retention policy; thus permanently preventing the policy from being reduced or removed. This way, if the system is ever compromised by an attacker or a malicious insider who wants to cover their tracks, the activity logs are definitely preserved for forensics and security investigations.

Impact

... see more

Remediation

Open File

Remediation

From Google Cloud Console

1. If sinks are not configured, first follow the instructions in the recommendation: Ensure that sinks are configured for all Log entries.
2. For each storage bucket configured as a sink, go to the Cloud Storage browser at https://console.cloud.google.com/storage/browser/<BUCKET_NAME>.
3. Select the Bucket Lock tab near the top of the page.
4. In the Retention policy entry, click the Add Duration link. The Set a retention policy dialog box appears.
5. Enter the desired length of time for the retention period and click Save policy.
6. Set the Lock status for this retention policy to Locked.

From Google Cloud CLI

1. To list all sinks destined to storage buckets:

    gcloud logging sinks list --folder=FOLDER_ID | --organization=ORGANIZATION_ID | --project=PROJECT_ID

2. For each storage bucket listed above, set a retention policy and lock it:

    gsutil retention set [TIME_DURATION] gs://[BUCKET_NAME] gsutil retention lock gs://[BUCKET_NAME]

For more information, visit https://cloud.google.com/storage/docs/using-bucket-lock#set-policy.

policy.yaml

Open File

Linked Framework Sections

Section	Sub Sections	Internal Rules	Policies	Flags
💼 CIS GCP v1.2.0 → 💼 2.3 Ensure that retention policies on log buckets are configured using Bucket Lock - Level 1 (Automated)			1
💼 CIS GCP v1.3.0 → 💼 2.3 Ensure That Retention Policies on Cloud Storage Buckets Used for Exporting Logs Are Configured Using Bucket Lock - Level 2 (Automated)			1
💼 CIS GCP v2.0.0 → 💼 2.3 Ensure That Retention Policies on Cloud Storage Buckets Used for Exporting Logs Are Configured Using Bucket Lock - Level 2 (Automated)			1
💼 CIS GCP v3.0.0 → 💼 2.3 Ensure That Retention Policies on Cloud Storage Buckets Used for Exporting Logs Are Configured Using Bucket Lock - Level 2 (Automated)			1
💼 Cloudaware Framework → 💼 Logging and Monitoring Configuration			53
💼 FedRAMP High Security Controls → 💼 AC-3 Access Enforcement (L)(M)(H)		37	64
💼 FedRAMP High Security Controls → 💼 AC-5 Separation of Duties (M)(H)			13
💼 FedRAMP High Security Controls → 💼 AC-6 Least Privilege (M)(H)	8	11	52
💼 FedRAMP High Security Controls → 💼 MP-2 Media Access (L)(M)(H)			12
💼 FedRAMP Low Security Controls → 💼 AC-3 Access Enforcement (L)(M)(H)			64
💼 FedRAMP Low Security Controls → 💼 MP-2 Media Access (L)(M)(H)			12
💼 FedRAMP Moderate Security Controls → 💼 AC-3 Access Enforcement (L)(M)(H)			64
💼 FedRAMP Moderate Security Controls → 💼 AC-5 Separation of Duties (M)(H)			13
💼 FedRAMP Moderate Security Controls → 💼 AC-6 Least Privilege (M)(H)	6		52
💼 FedRAMP Moderate Security Controls → 💼 MP-2 Media Access (L)(M)(H)			12
💼 ISO/IEC 27001:2013 → 💼 A.12.4.2 Protection of log information		2	3
💼 ISO/IEC 27001:2013 → 💼 A.18.1.3 Protection of records		2	4
💼 ISO/IEC 27001:2022 → 💼 5.10 Acceptable use of information and other associated assets		11	26
💼 ISO/IEC 27001:2022 → 💼 5.15 Access control		14	30
💼 ISO/IEC 27001:2022 → 💼 8.3 Information access restriction		10	23
💼 ISO/IEC 27001:2022 → 💼 8.4 Access to source code		8	21
💼 NIST CSF v1.1 → 💼 ID.GV-3: Legal and regulatory requirements regarding cybersecurity, including privacy and civil liberties obligations, are understood and managed		2	4
💼 NIST CSF v1.1 → 💼 PR.AC-4: Access permissions and authorizations are managed, incorporating the principles of least privilege and separation of duties		16	52
💼 NIST CSF v1.1 → 💼 PR.IP-4: Backups of information are conducted, maintained, and tested		5	8
💼 NIST CSF v1.1 → 💼 PR.PT-1: Audit/log records are determined, documented, implemented, and reviewed in accordance with policy		17	33
💼 NIST CSF v2.0 → 💼 GV.OC-03: Legal, regulatory, and contractual requirements regarding cybersecurity - including privacy and civil liberties obligations - are understood and managed			7
💼 NIST CSF v2.0 → 💼 PR.AA-05: Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties			87
💼 NIST CSF v2.0 → 💼 PR.DS-10: The confidentiality, integrity, and availability of data-in-use are protected			104
💼 NIST CSF v2.0 → 💼 PR.DS-11: Backups of data are created, protected, maintained, and tested			9
💼 NIST CSF v2.0 → 💼 PR.IR-01: Networks and environments are protected from unauthorized logical access and usage			65
💼 NIST SP 800-53 Revision 4 → 💼 AU-11 AUDIT RECORD RETENTION	1	1	2
💼 NIST SP 800-53 Revision 5 → 💼 AC-3 Access Enforcement	15	5	33
💼 NIST SP 800-53 Revision 5 → 💼 AC-5 Separation of Duties			13
💼 NIST SP 800-53 Revision 5 → 💼 AC-6 Least Privilege	10	23	45
💼 NIST SP 800-53 Revision 5 → 💼 MP-2 Media Access	2		12
💼 PCI DSS v3.2.1 → 💼 1.2.1 Restrict inbound and outbound traffic to that which is necessary for the cardholder data environment, and specifically deny all other traffic.		10	28
💼 PCI DSS v3.2.1 → 💼 10.5 Secure audit trails so they cannot be altered.	5	2	5
💼 PCI DSS v4.0.1 → 💼 1.3.1 Inbound traffic to the CDE is restricted.			28
💼 PCI DSS v4.0.1 → 💼 1.3.2 Outbound traffic from the CDE is restricted.			28
💼 PCI DSS v4.0 → 💼 1.3.1 Inbound traffic to the CDE is restricted.			28
💼 PCI DSS v4.0 → 💼 1.3.2 Outbound traffic from the CDE is restricted.			28
💼 SOC 2 → 💼 CC5.2-3 Establishes Relevant Security Management Process Controls Activities		16	36
💼 SOC 2 → 💼 CC6.1-3 Restricts Logical Access		1	21
💼 SOC 2 → 💼 CC6.1-7 Restricts Access to Information Assets		12	25