> 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-pan-15.md).

# Include ACL (Access Control List) not defined for a security zone in Palo Alto Networks devices with

## Rule Details

|                        |                                    |
| ---------------------- | ---------------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_PAN\_15                    |
| Category - Subcategory | Public Exposure - Ingress Controls |
| Provider               | OTHER                              |
| Severity               | LOW                                |
| Framework              | Ansible                            |

## Impact

This rule detects whether an 'Include ACL' (Access Control List) is defined when User-ID is enabled on a security zone in Palo Alto Networks devices. User-ID is a feature that maps IP addresses to users, allowing for policy enforcement based on user identity. When User-ID is enabled, the 'Include ACL' specifies which traffic should be included for user mapping. If the 'Include ACL' property is not defined, User-ID might incorrectly process or exclude important traffic.

## How to Fix

*Resource:* panos\_security\_rule

* *Attributes:* source\_ip, destination\_ip

To mitigate this risk, ensure that either the source\_ip or destination\_ip (or both) attributes in your panos\_security\_rule resources are configured with specific IP addresses or ranges instead of using any. This approach helps define precise and secure network traffic rules.

Secure Code Example:

## In this example, specifying exact IP addresses or ranges for source\_ip and destination\_ip ensures that the security rule does not unintentionally permit all traffic. \[source,go]

* name: Example tasks:
  * name: Example paloaltonetworks.panos.panos\_security\_rule: name: "example-rule"
* ```
     source_ip: ['any']
  ```
* ```
     destination_ip: ['any']
  ```
* ```
     source_ip: ['192.168.1.0/24']
  ```
* ```
     destination_ip: ['10.1.2.0/24']
  ```

***


---

# 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-pan-15.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.