> 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/logging/appsec-pan-9.md).

# Log Forwarding Profile not selected for a Palo Alto Networks device security policy rule misconfigur

## Rule Details

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

## Impact

This rule detects whether all security policy rules in Palo Alto Networks devices are associated with a Log Forwarding Profile. These profiles are essential for monitoring, troubleshooting, and auditing, as they determine which logs are forwarded and their destination for analysis and storage.

## How to Fix

**Palo Alto Networks**

* **Resource:** panos\_security\_rule
* **Attribute:** log\_setting

To mitigate this issue, ensure that the `log_setting` attribute in your `panos_security_rule` resources is defined, and points to an existing Log Forwarding Profile. This setup ensures that activity logs for each rule are captured and forwarded correctly, facilitating effective monitoring and analysis.

Secure Code Example:

```yaml
- name: Example
  tasks:
    - name: Example
      paloaltonetworks.panos.panos_security_rule:
        ...
+        log_setting: 'default'
```

In this example, configuring the `log_setting` attribute with a valid Log Forwarding Profile name for each security rule ensures that logging is properly implemented for security monitoring and analysis.


---

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