> 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/networking/appsec-aws-344.md).

# Network firewalls do not have deletion protection enabled misconfiguration detected in code

## Rule Details

|                        |                                    |
| ---------------------- | ---------------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_AWS\_344                   |
| Category - Subcategory | Public Exposure - Ingress Controls |
| Provider               | AWS                                |
| Severity               | HIGH                               |
| Framework              | Terraform, Terraform Plan          |

## Impact

This rule is checking to ensure that Network firewalls have deletion protection enabled. It's crucial for maintaining the integrity and security of the system. If deletion protection is not enabled, there is potential risk that essential firewall settings could be accidentally or maliciously deleted leading to an increased vulnerability to attacks. Therefore, this rule helps to safeguard critical network configurations against unintentional deletions.

## How to Fix

*Resource:* aws\_networkfirewall\_firewall

* *Arguments:* delete\_protection

To fix this issue, you need to enable deletion protection on your network firewalls.

## In AWS, you can achieve this by setting the `delete_protection` argument to `true` in the `aws_networkfirewall_firewall` resource block. \[source,go]

## resource "aws\_networkfirewall\_firewall" "example" { name = "example" firewall\_policy\_arn = aws\_networkfirewall\_firewall\_policy.example.arn vpc\_id = aws\_vpc.example.id subnet\_mapping { subnet\_id = aws\_subnet.example.id } delete\_protection = true }


---

# 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/networking/appsec-aws-344.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.