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

# Disable Server Response Inspection (DSRI) enabled in security policies for Palo Alto Networks device

## Rule Details

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

## Impact

This rule detects whether Disable Server Response Inspection (DSRI) is enabled in security policies for Palo Alto Networks devices. Enabling DSRI disables the inspection of server responses, potentially allowing malicious content to pass through the network unchecked, thereby reducing security.

## How to Fix

**Palo Alto Networks**

* **Resource:** panos\_security\_rule
* **Attribute:** disable\_server\_response\_inspection

To mitigate this issue, ensure that the disable\_server\_response\_inspection attribute is either set to 'false' or omitted in your panos\_security\_rule definitions. Disabling DSRI ensures that server responses are inspected, maintaining the efficacy of security policies.

Secure Code Example:

```yaml
- name: Verify tests
  hosts: all
  connection: local
  tasks:
    - name: Security_rule
      paloaltonetworks.panos.panos_security_rule:
        rule_name: 'Test rule'
        ...
-        disable_server_response_inspection: true
```

In this example, explicitly setting disable\_server\_response\_inspection to 'false' or omitting it ensures that DSRI is disabled, and that server responses are inspected.


---

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