> 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-99.md).

# GCP Pub/Sub Topics are anonymously or publicly accessible misconfiguration detected in code

## Rule Details

|                        |                        |
| ---------------------- | ---------------------- |
| Cortex AppSec Rule ID  | APPSEC\_GCP\_99        |
| Category - Subcategory | Public Exposure - APIs |
| Provider               | GCP                    |
| Severity               | MEDIUM                 |
| Framework              | Terraform              |

## Impact

Pub/Sub is commonly used for asynchronous communication for applications in GCP. Messages are published to a *Pub/Sub Topic* and the ability to publish a message is controlled via IAM policies. It is possible to make *Pub/Sub Topics* publicly or anonymously accessible. Public notification topics can expose sensitive data and are a target for data exfiltration. We recommend you ensure that neither anonymous or public access to *Pub/Sub Topics* is allowed.

## How to Fix

*Resource:* google\_pubsub\_topic\_iam\_binding

* *Field:* members
* *Resource:* google\_pubsub\_topic\_iam\_member
* *Field:* member \[source,go]

***

resource "google\_pubsub\_topic\_iam\_binding" "public\_binding" { topic = google\_pubsub\_topic.example.name role = "roles/pubsub.publisher"

members = \[

* "allUsers",
* "allAuthenticatedUsers", ] }

***

resource "google\_pubsub\_topic\_iam\_member" "public\_member" { topic = google\_pubsub\_topic.example.name role = "roles/pubsub.publisher"

* member = "allUsers"
* member = "allAuthenticatedUsers" }

***


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.