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

# GCP GitHub Actions OIDC trust policy is insecurely configured misconfiguration detected in code

## Rule Details

|                       |                           |
| --------------------- | ------------------------- |
| Cortex AppSec Rule ID | APPSEC\_GCP\_125          |
| Category              | IAM                       |
| Provider              | GCP                       |
| Severity              | HIGH                      |
| Framework             | Terraform, Terraform Plan |

## Impact

This rule detects whether GCP GitHub Actions OIDC trust policies are insecurely configured, potentially allowing security vulnerabilities. Misconfigured policies can allow unauthorized access or introduce potential exploits via wildcards, abusable claims, or improperly formatted repository claims.

## How to Fix

*Resource:* google\_iam\_workload\_identity\_pool\_provider

* *Arguments:* role

To mitigate this issue, make sure your `google_iam_workload_identity_pool_provider` resource is properly configured without insecure claims.

* Avoid wildcards (`*`) or unsafe claim structures.
* Ensure claims follow safe and restricted formats. Abusable claims include: "workflow", "environment", "ref", "context", "head\_ref", "base\_ref"
* Use a specific repository reference.

## Example: \[source,go]

resource "google\_iam\_workload\_identity\_pool\_provider" "example" { ... issuer\_uri = "<https://token.actions.githubusercontent.com>" attribute\_mapping = { "google.subject" = "assertion.sub" }

* attribute\_condition = "assertion.sub == 'repo:\*'"
* attribute\_condition = "assertion.sub == 'repo:organization/repository'" }

***


---

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