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

# AWS AdministratorAccess policy is used by IAM roles, users, or groups misconfiguration detected in c

## Rule Details

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

## Impact

This rule is checking for any IAM roles, users, and groups that are using the AWS AdministratorAccess policy. This is a security best-practice policy to avoid granting excessive permissions to users, roles, or groups. The AWS AdministratorAccess policy provides full access to all AWS resources, which could lead to misuse or abuse either knowingly or unknowlingly. In certain cases, it could increase the risk of data breaches or security compromises. Therefore, it's advised to have granular control over user permissions and grant only the necessary rights to fulfill tasks, adhering to the principle of least privilege.

## How to Fix

*Resource:* "aws\_iam\_role", "aws\_iam\_policy\_attachment", "aws\_iam\_role\_policy\_attachment" "aws\_iam\_user\_policy\_attachment", "aws\_iam\_group\_policy\_attachment", "aws\_ssoadmin\_managed\_policy\_attachment"

* *Arguments:* managed\_policy\_arns, policy\_arn, managed\_policy\_arn

To fix this issue, provide specific, least privilege IAM policies to your IAM roles, users, and groups instead of using the `AdministratorAccess` policy. You can do this by defining an IAM policy and attaching it to the necessary resources.


---

# 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-274.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.