Skip to main content

📝 Google Storage Bucket Uniform Bucket-Level Access is not enabled 🟢

  • Contextual name: 📝 Bucket Uniform Bucket-Level Access is not enabled 🟢
  • ID: /ce/ca/google/storage/uniform-bucket-level-access
  • Located in: 📁 Google Storage

Flags​

Our Metadata​

  • Policy Type: COMPLIANCE_POLICY
  • Policy Category:
    • SECURITY

Similar Policies​

Logic​

Description​

Open File

Description​

It is recommended that uniform bucket-level access is enabled on Cloud Storage buckets.

Rationale​

It is recommended to use uniform bucket-level access to unify and simplify how you grant access to your Cloud Storage resources.

Cloud Storage offers two systems for granting users permission to access your buckets and objects: Cloud Identity and Access Management (Cloud IAM) and Access Control Lists (ACLs). These systems act in parallel - in order for a user to access a Cloud Storage resource, only one of the systems needs to grant the user permission. Cloud IAM is used throughout Google Cloud and allows you to grant a variety of permissions at the bucket and project levels. ACLs are used only by Cloud Storage and have limited permission options, but they allow you to grant permissions on a per-object basis.

In order to support a uniform permissioning system, Cloud Storage has uniform bucket-level access. Using this feature disables ACLs for all Cloud Storage resources: access to Cloud Storage resources then is granted exclusively through Cloud IAM. Enabling uniform bucket-level access guarantees that if a Storage bucket is not publicly accessible, no object in the bucket is publicly accessible either.

... see more

Remediation​

Open File

Remediation​

From Google Cloud Console​

  1. Open the Cloud Storage browser in the Google Cloud Console by visiting: https://console.cloud.google.com/storage/browser
  2. In the list of buckets, click on the name of the desired bucket.
  3. Select the Permissions tab near the top of the page.
  4. In the text box that starts with This bucket uses fine-grained access control..., click Edit.
  5. In the pop-up menu that appears, select Uniform.
  6. Click Save.

From Google Cloud CLI​

Use the on option in a uniformbucketlevelaccess set command:

        gsutil uniformbucketlevelaccess set on gs://BUCKET_NAME/

policy.yaml​

Open File

Linked Framework Sections​

SectionSub SectionsInternal RulesPoliciesFlags
💼 CIS GCP v1.2.0 → 💼 5.2 Ensure that Cloud Storage buckets have uniform bucket-level access enabled - Level 2 (Automated)1
💼 CIS GCP v1.3.0 → 💼 5.2 Ensure That Cloud Storage Buckets Have Uniform Bucket-Level Access Enabled - Level 2 (Automated)1
💼 CIS GCP v2.0.0 → 💼 5.2 Ensure That Cloud Storage Buckets Have Uniform Bucket-Level Access Enabled - Level 2 (Automated)1
💼 CIS GCP v3.0.0 → 💼 5.2 Ensure That Cloud Storage Buckets Have Uniform Bucket-Level Access Enabled - Level 2 (Automated)1
💼 Cloudaware Framework → 💼 Secure Access53
💼 FedRAMP High Security Controls → 💼 AC-3 Access Enforcement (L)(M)(H)3764
💼 FedRAMP High Security Controls → 💼 AC-5 Separation of Duties (M)(H)13
💼 FedRAMP High Security Controls → 💼 AC-6 Least Privilege (M)(H)81153
💼 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)653
💼 FedRAMP Moderate Security Controls → 💼 MP-2 Media Access (L)(M)(H)12
💼 ISO/IEC 27001:2022 → 💼 5.10 Acceptable use of information and other associated assets1126
💼 ISO/IEC 27001:2022 → 💼 5.15 Access control1430
💼 ISO/IEC 27001:2022 → 💼 8.3 Information access restriction1023
💼 ISO/IEC 27001:2022 → 💼 8.4 Access to source code821
💼 NIST CSF v1.1 → 💼 PR.AC-4: Access permissions and authorizations are managed, incorporating the principles of least privilege and separation of duties1752
💼 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 duties88
💼 NIST CSF v2.0 → 💼 PR.DS-10: The confidentiality, integrity, and availability of data-in-use are protected108
💼 NIST CSF v2.0 → 💼 PR.IR-01: Networks and environments are protected from unauthorized logical access and usage66
💼 NIST SP 800-53 Revision 5 → 💼 AC-3 Access Enforcement15534
💼 NIST SP 800-53 Revision 5 → 💼 AC-5 Separation of Duties13
💼 NIST SP 800-53 Revision 5 → 💼 AC-6 Least Privilege102346
💼 NIST SP 800-53 Revision 5 → 💼 MP-2 Media Access212
💼 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.1035
💼 PCI DSS v4.0.1 → 💼 1.3.1 Inbound traffic to the CDE is restricted.35
💼 PCI DSS v4.0.1 → 💼 1.3.2 Outbound traffic from the CDE is restricted.35
💼 PCI DSS v4.0 → 💼 1.3.1 Inbound traffic to the CDE is restricted.735
💼 PCI DSS v4.0 → 💼 1.3.2 Outbound traffic from the CDE is restricted.35
💼 SOC 2 → 💼 CC5.2-3 Establishes Relevant Security Management Process Controls Activities1535
💼 SOC 2 → 💼 CC6.1-3 Restricts Logical Access121
💼 SOC 2 → 💼 CC6.1-7 Restricts Access to Information Assets1326