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