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

# IAM policy uses the AWS AdministratorAccess policy misconfiguration detected in code

## Rule Details

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

## Impact

This rule is designed to monitor for any use of the AWS AdministratorAccess policy within your infrastructure. The AdministratorAccess policy in Amazon Web Services (AWS) provides complete, unrestricted access to all resources in an AWS account. It's a built-in managed policy that attaches to an identity (user, group of users, or role) to determine what actions the identity can and cannot perform.

Granting AdministratorAccess policy is generally a bad practice for security reasons. It can lead to a variety of security risks, including misconfigurations or compromise leading to unauthorized access or data breaches. By overprovisioning permissions, it increases the potential attack surface for malicious users.

The principle of least privilege (POLP), an important computer security concept, advises that every module must be able to access only the information and resources that are necessary for its legitimate purpose. In other words, users should have the minimum levels of access necessary to complete their job functions.

It is always advisable to assign granular permissions, creating custom policies with specific access permissions rather than using AWS AdministratorAccess policy. This way, it significantly reduces the risk of accidental exposure or illicit activities.

## How to Fix

*Resource:* aws\_iam\_policy

* *Arguments:* name

To fix this issue, define least privilege access as per the necessity of the role or user. Instead of using the `AdministratorAccess` policy, use a more restricted managed policy or create a custom policy that only gives the permissions necessary for required tasks.


---

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