> 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/ldap-traffic-from-non-standard-process.md).
# LDAP 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 Day |
| Required Data | XDR Agent |
| ATT\&CK Tactic | Discovery (TA0007) |
| ATT\&CK Technique | Account Discovery (T1087) |
| Severity | Informational |
### Description
LDAP traffic is usually performed by a standard set of processes. The endpoint had a non-standard process communicating over ports normally used by LDAP. This may be indicative of Active Directory domain enumeration, which may be used during attacks against the organization.
### Attacker's Goals
An attacker is attempting to enumerate Active Directory.
### 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 LDAP.
* 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.
* 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
LDAP traffic from reverse SSH tunnel
**Synopsis**
| Field | Value |
| ----------------- | ------------------------- |
| ATT\&CK Tactic | Discovery (TA0007) |
| ATT\&CK Technique | Account Discovery (T1087) |
| Severity | Medium |
**Description**
LDAP traffic is usually performed by a standard set of processes. The endpoint had a non-standard process communicating over ports normally used by LDAP. This may be indicative of Active Directory domain enumeration, which may be used during attacks against the organization.
**Attacker's Goals**
An attacker is attempting to enumerate Active Directory.
**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 LDAP.
* 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.
* 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.
LDAP traffic from non-standard and uncommon process
**Synopsis**
| Field | Value |
| ----------------- | ------------------------- |
| ATT\&CK Tactic | Discovery (TA0007) |
| ATT\&CK Technique | Account Discovery (T1087) |
| Severity | Low |
**Description**
LDAP traffic is usually performed by a standard set of processes. The endpoint had a non-standard process communicating over ports normally used by LDAP. This may be indicative of Active Directory domain enumeration, which may be used during attacks against the organization.
**Attacker's Goals**
An attacker is attempting to enumerate Active Directory.
**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 LDAP.
* 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.
* 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.
LDAP traffic from non-standard process executed under an unsigned causality actor in a commonly abused directory
**Synopsis**
| Field | Value |
| ----------------- | ------------------------- |
| ATT\&CK Tactic | Discovery (TA0007) |
| ATT\&CK Technique | Account Discovery (T1087) |
| Severity | Low |
**Description**
LDAP traffic is usually performed by a standard set of processes. The endpoint had a non-standard process communicating over ports normally used by LDAP. This may be indicative of Active Directory domain enumeration, which may be used during attacks against the organization.
**Attacker's Goals**
An attacker is attempting to enumerate Active Directory.
**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 LDAP.
* 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.
* 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.
LDAP traffic from an injected thread within a non-standard process
**Synopsis**
| Field | Value |
| ----------------- | ------------------------- |
| ATT\&CK Tactic | Discovery (TA0007) |
| ATT\&CK Technique | Account Discovery (T1087) |
| Severity | Low |
**Description**
LDAP traffic is usually performed by a standard set of processes. The endpoint had a non-standard process communicating over ports normally used by LDAP. This may be indicative of Active Directory domain enumeration, which may be used during attacks against the organization.
**Attacker's Goals**
An attacker is attempting to enumerate Active Directory.
**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 LDAP.
* 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.
* 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.
---
# 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/ldap-traffic-from-non-standard-process.md?ask=&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.