> 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/analytics-alerts/alerts-by-name/unusual-netsh-portproxy-rule.md).
# Unusual Netsh PortProxy rule
### Synopsis
| Field | Value |
| -------------------- | ------------------------------------------------------------------------------------------------- |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | N/A (single event) |
| Deduplication Period | 1 Day |
| Required Data | XDR Agent with eXtended Threat Hunting (XTH) |
| Detector Tags | LOLBIN Execution Analytics |
| ATT\&CK Tactic | Defense Evasion (TA0005), Command and Control (TA0011) |
| ATT\&CK Technique | Impair Defenses: Disable or Modify System Firewall (T1562.004), Proxy: Internal Proxy (T1090.001) |
| Severity | Low |
### Description
Attackers may use Netsh PortProxy rules as part of malicious actions performed in an organizational network (e.g., for tunneling).
### Attacker's Goals
Adding or deleting netsh forwarding rules as a proxy and to avoid possible detection.
### Investigative actions
* Check the connect address and if it's a known IP/domain.
* Check whether the causality group owner (CGO) process is benign and if this was a desired behavior as part of its normal execution flow.
### Variations
Unusual Netsh PortProxy rule by non-netsh process
**Synopsis**
| Field | Value |
| ----------------- | ------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Defense Evasion (TA0005), Command and Control (TA0011) |
| ATT\&CK Technique | Impair Defenses: Disable or Modify System Firewall (T1562.004), Proxy: Internal Proxy (T1090.001) |
| Severity | Medium |
**Description**
Attackers may use Netsh PortProxy rules as part of malicious actions performed in an organizational network (e.g., for tunneling).
**Attacker's Goals**
Adding or deleting netsh forwarding rules as a proxy and to avoid possible detection.
**Investigative actions**
* Check the connect address and if it's a known IP/domain.
* Check whether the causality group owner (CGO) process is benign and if this was a desired behavior as part of its normal execution flow.
Unusual Netsh PortProxy rule by an unsigned causality actor
**Synopsis**
| Field | Value |
| ----------------- | ------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Defense Evasion (TA0005), Command and Control (TA0011) |
| ATT\&CK Technique | Impair Defenses: Disable or Modify System Firewall (T1562.004), Proxy: Internal Proxy (T1090.001) |
| Severity | Medium |
**Description**
Attackers may use Netsh PortProxy rules as part of malicious actions performed in an organizational network (e.g., for tunneling).
**Attacker's Goals**
Adding or deleting netsh forwarding rules as a proxy and to avoid possible detection.
**Investigative actions**
* Check the connect address and if it's a known IP/domain.
* Check whether the causality group owner (CGO) process is benign and if this was a desired behavior as part of its normal execution flow.
---
# 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/analytics-alerts/alerts-by-name/unusual-netsh-portproxy-rule.md?ask=&goal=
```
`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.