> 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/possible-use-of-a-networking-driver-for-network-sniffing.md).

# Possible use of a networking driver for network sniffing

### 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)   |
| ATT\&CK Tactic       | Credential Access (TA0006), Discovery (TA0007) |
| ATT\&CK Technique    | Network Sniffing (T1040)                       |
| Severity             | Informational                                  |

### Description

A process wrote a known networking driver with network sniffing capabilities to disk, attackers can use it to sniff passwords and other credentials from the network.

### Attacker's Goals

Enable access to raw network traffic via promiscuous mode, allowing an attacker to sniff credentials and other sensitive data from the organization's network, and in some cases interfere with network communications.

### Investigative actions

* Verify whether the process is expected and recognized by IT or the user.
* Check whether the driver was installed recently. If it was installed using sc.exe, this may indicate malicious activity. Review who executed sc.exe to validate legitimacy.

### Variations

<details>

<summary>Possible use of a networking driver for network sniffing</summary>

**Synopsis**

| Field             | Value                                          |
| ----------------- | ---------------------------------------------- |
| ATT\&CK Tactic    | Credential Access (TA0006), Discovery (TA0007) |
| ATT\&CK Technique | Network Sniffing (T1040)                       |
| Severity          | Medium                                         |

**Description**

A process wrote a known and rare networking driver with network sniffing capabilities to not standard location for drivers on the disk, attackers can use it to sniff passwords and other credentials from the network.

**Attacker's Goals**

Enable access to raw network traffic via promiscuous mode, allowing an attacker to sniff credentials and other sensitive data from the organization's network, and in some cases interfere with network communications.

**Investigative actions**

* Verify whether the process is expected and recognized by IT or the user.
* Check whether the driver was installed recently. If it was installed using sc.exe, this may indicate malicious activity. Review who executed sc.exe to validate legitimacy.

</details>

<details>

<summary>Possible use of a networking driver for network sniffing</summary>

**Synopsis**

| Field             | Value                                          |
| ----------------- | ---------------------------------------------- |
| ATT\&CK Tactic    | Credential Access (TA0006), Discovery (TA0007) |
| ATT\&CK Technique | Network Sniffing (T1040)                       |
| Severity          | Low                                            |

**Description**

A process wrote a known networking driver with network sniffing capabilities to not standard location for drivers on the disk, attackers can use it to sniff passwords and other credentials from the network.

**Attacker's Goals**

Enable access to raw network traffic via promiscuous mode, allowing an attacker to sniff credentials and other sensitive data from the organization's network, and in some cases interfere with network communications.

**Investigative actions**

* Verify whether the process is expected and recognized by IT or the user.
* Check whether the driver was installed recently. If it was installed using sc.exe, this may indicate malicious activity. Review who executed sc.exe to validate legitimacy.

</details>


---

# 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/analytics-alerts/alerts-by-name/possible-use-of-a-networking-driver-for-network-sniffing.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.