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

# Logging at session start enabled on Palo Alto Networks devices misconfiguration detected in code

## Rule Details

|                        |                                            |
| ---------------------- | ------------------------------------------ |
| Cortex AppSec Rule ID  | APPSEC\_PAN\_16                            |
| Category - Subcategory | Public Exposure - Encryption And Protocols |
| Provider               | OTHER                                      |
| Severity               | LOW                                        |
| Framework              | Ansible                                    |

## Impact

This rule detects whether logging at the start of a session is enabled on Palo Alto Networks devices. While logging at session start can provide detailed insights for troubleshooting or monitoring specific long-lived GRE tunnel connections, it typically generates a large volume of logs and can lead to resource consumption issues.

## How to Fix

*Resource:* panos\_security\_rule

* *Attribute:* description

To mitigate this issue, ensure that every panos\_security\_rule resource contains a descriptive description attribute. This description should offer clear and concise information about the rule's purpose, facilitating effective management and documentation of security policies.

Secure Code Example:

## In this example, including meaningful descriptions in your security rules clarity and manageability of your security policies. \[source,go]

* name: Example tasks:
  * name: Example paloaltonetworks.panos.panos\_security\_rule: ...
* ```
     description: "Block traffic from untrusted zones to critical servers"
  ```

***


---

# 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-16.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.