> 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-aws-393.md).

# AWS GitHub Actions OIDC authorization policies allow for unsafe claims or claim order on IAM role mi

## Rule Details

|                        |                           |
| ---------------------- | ------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_AWS\_393          |
| Category - Subcategory | IAM - Overly Permissive   |
| Provider               | AWS                       |
| Severity               | HIGH                      |
| Framework              | Terraform, Terraform Plan |

## Impact

This rule detects whether an `aws_iam_role` resource whose trust policy (`assume_role_policy`) uses GitHub Actions OIDC authorization is configured with potentially unsafe claims or claim orders. Misconfigured claims can lead to security vulnerabilities by allowing unauthorized access or unsafe token usage, potentially resulting in privilege escalation or abuse.

This is the resource-level counterpart of CKV\_AWS\_358, which inspects `data "aws_iam_policy_document"` blocks; this rule applies the same logic to IAM roles that define their trust policy inline.

Specifically, the rule checks for:

* Missing or invalid conditions on the `sub` variable.
* Wildcard values or generic claims that could be abused.
* Unsafe claim formats or orders in the `sub` variable.

## How to Fix

*Resource: aws\_iam\_role*

* *Argument: assume\_role\_policy*

To mitigate this issue, ensure the trust policy condition in the `aws_iam_role` resource:

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

## Example: \[source,go]

resource "aws\_iam\_role" "example" { name = "example" assume\_role\_policy = jsonencode({ Version = "2012-10-17" Statement = \[{ Effect = "Allow" Action = "sts:AssumeRoleWithWebIdentity" Principal = { Federated = "arn:aws:iam::123456123456:oidc-provider/token.actions.githubusercontent.com" } Condition = { StringEquals = {

* ```
       "token.actions.githubusercontent.com:sub" = "*"
  ```
* ```
       "token.actions.githubusercontent.com:sub" = "repo:myOrg/myRepo:*"
  ```

## } } }] }) }


---

# 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-aws-393.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.