> 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/compute/appsec-aws-384.md).

# Hard-coded secrets found in Parameter Store values misconfiguration detected in code

## Rule Details

|                       |                  |
| --------------------- | ---------------- |
| Cortex AppSec Rule ID | APPSEC\_AWS\_384 |
| Category              | Compute          |
| Provider              | AWS              |
| Severity              | MEDIUM           |
| Framework             | CloudFormation   |

## Impact

This rule checks for hard-coded secrets within AWS Parameter Store values. Hard-coded secrets can pose significant security risks because they may expose sensitive information, such as API keys, passwords, or access tokens, directly in configuration files or code. If an attacker gains access to these secrets, they can exploit them to gain unauthorized access to systems, compromise data integrity, or initiate other malicious activities.

Ensuring that no hard-coded secrets exist helps maintain a secure environment by encouraging the use of more secure practices, such as environment variables, secret management tools, or vault services, which provide better protection and management for sensitive information.

## How to Fix

## Do not add plaintext secrets to your Parameter Store values in CloudFormation. Instead, consider using secrets management systems such as AWS Secrets Manager, or leverage environment variables for sensitive information. \[source,go]

Resources:

* FailAPIKey:
* Type: 'AWS::SSM::Parameter'
* Properties:
* Name: '/myapp/api\_key'
* Type: 'String'
* Value: 'hardcoded\_secret\_value'

***


---

# 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/compute/appsec-aws-384.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.