> 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/smb-traffic-from-non-standard-process.md).

# SMB Traffic from Non-Standard Process

### Synopsis

| Field                | Value                             |
| -------------------- | --------------------------------- |
| Activation Period    | 14 Days                           |
| Training Period      | 30 Days                           |
| Test Period          | N/A (single event)                |
| Deduplication Period | 1 Hour                            |
| Required Data        | XDR Agent                         |
| ATT\&CK Tactic       | Discovery (TA0007)                |
| ATT\&CK Technique    | Network Service Discovery (T1046) |
| Severity             | Low                               |

### Description

SMB traffic is usually performed by a standard set of privileged processes through designated ports. The endpoint had a non-standard process communicating over ports normally used by SMB. An attacker might be moving laterally by using tools that implement a custom version of the SMB protocol.

### Attacker's Goals

This might be symptomatic of an attacker's lateral movements. The attacker could be:\* using a custom protocol implementation that offers malicious functionality

* Using the well-known SMB port with a different protocol to evade detection. Either way, the attacker's goal is to gain access to another endpoint on your network. The attacker could also be surveying your network by performing service scans over the well-known SMB or Kerberos ports.

### Investigative actions

* Make sure the process is not a scanner that implements its version of the protocol, and that the scanner use is for sanctioned purposes. For example, nmap enumerating SMB.
* Make sure the process is not a sanctioned security product that creates standalone binaries for its use. For example, Illusive Network honeypots.
* Investigate the process to see if the high-level language used to implement the application is the source of the alert. Some high-level programming languages provide their protocol implementations. For example, Java uses its Kerberos implementation.
* Examine the endpoint to see if it is infected with malware. If the parent-child chain of initiating processes has been infiltrated with a malicious replacement, then that replacement could be known malware.

### Variations

<details>

<summary>SMB Traffic from Non-Standard Process on a sensitive server</summary>

**Synopsis**

| Field             | Value                             |
| ----------------- | --------------------------------- |
| ATT\&CK Tactic    | Discovery (TA0007)                |
| ATT\&CK Technique | Network Service Discovery (T1046) |
| Severity          | Medium                            |

**Description**

SMB traffic is usually performed by a standard set of privileged processes through designated ports. The endpoint had a non-standard process communicating over ports normally used by SMB. An attacker might be moving laterally by using tools that implement a custom version of the SMB protocol.

**Attacker's Goals**

This might be symptomatic of an attacker's lateral movements. The attacker could be:\* using a custom protocol implementation that offers malicious functionality

* Using the well-known SMB port with a different protocol to evade detection. Either way, the attacker's goal is to gain access to another endpoint on your network. The attacker could also be surveying your network by performing service scans over the well-known SMB or Kerberos ports.

**Investigative actions**

* Make sure the process is not a scanner that implements its version of the protocol, and that the scanner use is for sanctioned purposes. For example, nmap enumerating SMB.
* Make sure the process is not a sanctioned security product that creates standalone binaries for its use. For example, Illusive Network honeypots.
* Investigate the process to see if the high-level language used to implement the application is the source of the alert. Some high-level programming languages provide their protocol implementations. For example, Java uses its Kerberos implementation.
* Examine the endpoint to see if it is infected with malware. If the parent-child chain of initiating processes has been infiltrated with a malicious replacement, then that replacement could be known malware.

</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 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/smb-traffic-from-non-standard-process.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.