> 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/storage/appsec-aws-337.md).

# SSM parameters are not utilizing KMS CMK. misconfiguration detected in code

## Rule Details

|                        |                           |
| ---------------------- | ------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_AWS\_337          |
| Category - Subcategory | Storage - Encryption      |
| Provider               | AWS                       |
| Severity               | HIGH                      |
| Framework              | Terraform, Terraform Plan |

## Impact

This rule is verifying that AWS System Manager parameters are utilizing Key Management Service (KMS) customer-managed keys (CMK) for encryption. This rule is crucial for providing additional layers of security, as it ensures that all sensitive data processed and stored by System Manager parameters are protected by reliable encryption methods. Not complying with this rule means your SSM parameters are not fully protected, leading to potential data breaches and non-compliance with data protection regulations.

## How to Fix

*Resource:* aws\_ssm\_parameter

* *Arguments:* key\_id

To fix the issue, you should enable encryption for SSM (System Manager) parameters using KMS Customer Master Key (CMK). CMK allows you to have more flexibility around key management, including who can use the key and for what resources.

## In the above code, the `aws_ssm_parameter` resource is configured to use a key from KMS (Key Management Service). The `key_id` attribute specifies the ARN (Amazon Resource Name) of the KMS key that should be used for encrypting the value of the parameter. \[source,go]

## resource "aws\_ssm\_parameter" "example" { name = "example" type = "SecureString" value = "example\_value" key\_id = "arn:aws:kms:us-east-1:123456789012:key/abcd1234-a123-456a-a12b-a123b4cd56ef" }


---

# 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/storage/appsec-aws-337.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.