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

# AWS Secrets Manager secret not encrypted by Customer Managed Key (CMK) misconfiguration detected in

## Rule Details

|                        |                                                       |
| ---------------------- | ----------------------------------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_AWS\_149                                      |
| Category - Subcategory | Storage - Encryption                                  |
| Provider               | AWS                                                   |
| Severity               | LOW                                                   |
| Framework              | CloudFormation, Serverless, Terraform, Terraform Plan |
| Mapped CSPM/KSPM Rule  | e6503172-b262-4949-b651-e8ffb3947167                  |

## Impact

This rule ensures that AWS Secrets Manager secrets are encrypted using a customer-managed key (CMK) in AWS Key Management Service (KMS). Using a CMK provides additional control over the encryption keys used to protect your secrets, allowing you to manage key policies, rotation, and usage. This rule checks whether the `KmsKeyId` property is set to a value that does not contain the prefix `aws/` which indicates the use of the default AWS-managed key.

## How to Fix

To fix this issue, ensure that the `KmsKeyId` property in the `AWS::SecretsManager::Secret` resource is set to a customer-managed KMS key ARN or ID.

## Example: \[source,go]

## Resources: MySecretManagerSecret: Type: AWS::SecretsManager::Secret Properties: Name: example-secret KmsKeyId: arn:aws:kms:us-west-2:123456789012:key/example-key-arn ...


---

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