> 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/public-exposure/appsec-aws-352.md).

# NACL ingress allows all ports misconfiguration detected in code

## Rule Details

|                        |                                   |
| ---------------------- | --------------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_AWS\_352                  |
| Category - Subcategory | Public Exposure - Sensitive Ports |
| Provider               | AWS                               |
| Severity               | HIGH                              |
| Framework              | Terraform, Terraform Plan         |

## Impact

This rule is checking to ensure that Network Access Control Lists (NACLs) in AWS do not allow ingress (incoming traffic) on all ports. This is a basic security measure aiming to reduce the potential exposure of your system. Allowing all ports for ingress can expose your system to unwanted or malicious traffic from any port, potentially opening the door for a cyber attack or system compromise. It's a good practise to limit the ports exposed to only those necessary for your system's operations to manage the security risks.

## How to Fix

*Resource:* aws\_network\_acl\_rule

* *Arguments:* from\_port

## To fix this issue, specify the ports whenever you are creating a NACL ingress rule. Avoid using "-1" or "0" as the 'from\_port' or 'to\_port' as these denote all ports. \[source,go]

## resource "aws\_network\_acl\_rule" "example" { network\_acl\_id = aws\_network\_acl.example.id rule\_number = 200 egress = false protocol = "tcp" rule\_action = "allow" cidr\_block = "0.0.0.0/0" from\_port = 80 to\_port = 80 }


---

# 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/public-exposure/appsec-aws-352.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.