> 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/appsec2-aws-64.md).

# A Policy is not Defined for KMS Key misconfiguration detected in code

## Rule Details

|                        |                            |
| ---------------------- | -------------------------- |
| Cortex AppSec Rule ID  | APPSEC2\_AWS\_64           |
| Category - Subcategory | IAM - Expired Key Controls |
| Provider               | AWS                        |
| Severity               | MEDIUM                     |
| Framework              | Terraform, Terraform Plan  |

## Impact

This rule is designed to detect situations where the KMS key policy is undefined within your AWS environment. KMS keys are essential for data encryption and it's crucial to monitor and manage the policies that define their use to ensure data security is maintained.

## How to Fix

*Resource:* aws\_kms\_key

* *Arguments:* policy

The policy argument should be specified to define the KMS key policy.

Secure code example:

## The above code is secure because it defines a valid key policy for the KMS key, ensuring that access and usage are managed according to the organization's requirements. \[source,go]

## resource "aws\_kms\_key" "example" { description = "KMS key for example" policy = <\<POLICY { "Version": "2012-10-17", "Id": "default", "Statement": \[ { "Sid": "DefaultAllow", "Effect": "Allow", "Principal": { "AWS": "arn:aws:iam::123456789012:root" }, "Action": "kms:*", "Resource": "*" } ] } POLICY }


---

# 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/appsec2-aws-64.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.