> 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/iam/appsec-gcp-112.md).

# KMS policy allows public access misconfiguration detected in code

## Rule Details

|                        |                           |
| ---------------------- | ------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_GCP\_112          |
| Category - Subcategory | IAM - Overly Permissive   |
| Provider               | GCP                       |
| Severity               | HIGH                      |
| Framework              | Terraform, Terraform Plan |

## Impact

This rule is checking to ensure that the Key Management Service (KMS) policy does not allow public access. The Key Management Service is a critical component for managing encryption keys that are used to secure your data. If a KMS policy allows public access, it means anyone on the internet could potentially access your encryption keys. This is a significant security risk because if malicious actors gain access to your encryption keys, they can encrypt and decrypt your data, leading to potential data breaches or loss. Therefore, it's essential to keep KMS policies restricted to specific, trusted individuals or services.

## How to Fix

*Resource:* "google\_kms\_crypto\_key\_iam\_policy", "google\_kms\_crypto\_key\_iam\_binding", "google\_kms\_crypto\_key\_iam\_member"

* *Arguments:* policy\_data

To fix the issue, you need to ensure that the KMS policy does not allow public access. This can be done by ensuring that the member in the `bindings` block of KMS crypto keys and KMS key rings is not 'allUsers' or 'allAuthenticatedUsers'.

## This updated Terraform code is secure because it doesn't provide public access to the KMS crypto keys and KMS key rings. Instead, access is restricted to specified users, in this case '<jane@example.com>' for the crypto key and '<john@example.com>' for the key ring. \[source,go]

resource "google\_kms\_crypto\_key\_iam\_binding" "crypto\_key" { crypto\_key\_id = google\_kms\_crypto\_key.my\_crypto\_key.self\_link role = "roles/cloudkms.cryptoKeyEncrypterDecrypter"

members = \[ "user:<jane@example.com>" ] }

resource "google\_kms\_key\_ring\_iam\_binding" "key\_ring" { key\_ring\_id = google\_kms\_key\_ring.my\_key\_ring.self\_link role = "roles/cloudkms.admin"

## members = \[ "user:<john@example.com>" ] }


---

# 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/iam/appsec-gcp-112.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.