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

# Network firewall encryption does not use a CMK misconfiguration detected in code

## Rule Details

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

## Impact

This rule is checking to ensure that a Network firewall is using encryption via a Customer Master Key (CMK). If a Network firewall is not using a CMK for encryption, it can potentially leave the network vulnerable to unauthorized data access, breaches, and misuse of hosts inside the network. CMKs provide very high levels of security control including key rotation, key usage policies and audit trail, further facilitating secure and controlled access to the network. Thus, not implementing encryption via a CMK for Network firewall can have severe implications for network security.

## How to Fix

*Resource:* 'aws\_networkfirewall\_firewall', 'aws\_networkfirewall\_rule\_group'

* *Arguments:* encryption\_configuration.key\_id

## To fix the issue, you need to create a Customer Managed Key (CMK) and use it for Network Firewall encryption. \[source,go]

## resource "aws\_networkfirewall\_firewall" "example" { name = "example" ... encryption\_configuration { key\_id = aws\_kms\_key.my\_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-345.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.