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

# Security Rule in Palo Alto Networks devices with overly broad Source and Destination IPs misconfigur

## Rule Details

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

## Impact

This rule detects whether security rules in Palo Alto Networks devices use 'any' for both 'source\_ip' and 'destination\_ip' simultaneously. Configuring both source and destination IPs to 'any' in a security rule can lead to overly broad permissions, potentially exposing the network to unintended traffic. At least one of these attributes, either source\_ip or destination\_ip, should be set to a specific value other than 'any' to enforce more granular and secure traffic filtering.

## How to Fix

**Palo Alto Networks**

* **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:

```yaml
- 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']
```

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.


---

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