> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/appsec-rules/iac-security/public-exposure/appsec-gcp-114.md).

# GCP Storage buckets are publicly accessible to all users misconfiguration detected in code

## Rule Details

|                        |                                      |
| ---------------------- | ------------------------------------ |
| Cortex AppSec Rule ID  | APPSEC\_GCP\_114                     |
| Category - Subcategory | Public Exposure - Storage Buckets    |
| Provider               | GCP                                  |
| Severity               | HIGH                                 |
| Framework              | Terraform, Terraform Plan            |
| Mapped CSPM/KSPM Rule  | 41f7a4b1-cad6-4fbf-b698-1fd11a8869a8 |

## Impact

This rule reviews if a Google Cloud Storage bucket is safeguarded against public access. It essentially checks if measures to prevent public access are enforced on these storage buckets. If storage buckets are left publicly accessible, sensitive and private data stored within them could be exposed to unauthorized users. This potentially leads to data breaches, sabotage, or the unlawful use of this data. Therefore, this rule ensures these storage buckets are secured and not vulnerable to such risks.

## How to Fix

*Resource:* google\_storage\_bucket

* *Arguments:* public\_access\_prevention

To fix the identified issue, you should ensure the "public\_access\_prevention" setting is enabled for your Google Cloud Storage bucket. This would help to protect your bucket from unintentional or unauthenticated public access.

Here is an example:

## The above code sets 'public\_access\_prevention' to 'enforced' for the Google Cloud Storage bucket. This enables public access prevention, so the Google Cloud Storage bucket cannot be accessed publicly. \[source,go]

## resource "google\_storage\_bucket" "example\_bucket" { name = "example\_bucket" location = "US" uniform\_bucket\_level\_access = true bucket\_policy\_only = true iam\_configuration { uniform\_bucket\_level\_access { enabled = true } public\_access\_prevention = "enforced" } }


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/appsec-rules/iac-security/public-exposure/appsec-gcp-114.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.