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

# AWS IAM policy documents allow \* (asterisk) as a statement's action misconfiguration detected in cod

## Rule Details

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

## Impact

This rule ensures that IAM policy documents do not allow "*" as a statement's actions. Allowing "*" in the actions of an IAM policy grants permissions to all actions, which can lead to potential security risks and unauthorized access. This rule checks whether any IAM policy documents contain statements with `"Action": "*"`, which should be avoided.

## How to Fix

To fix this issue, ensure that the IAM policy statements do not use "\*" in the actions. Instead, specify the specific actions that are required.

## Example: \[source,go]

Resources: MyIAMRole: Type: AWS::IAM::Role Properties: ... Policies:

* PolicyName: "example-policy" PolicyDocument: Version: "2012-10-17" Statement:
* Effect: "Allow" Action:
* * "\*" Resource:
* "arn:aws:s3:::example-bucket"
* "arn:aws:s3:::example-bucket/\*"

***


---

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