> 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/a-user-executed-multiple-ldap-enumeration-queries.md).
# A user executed multiple LDAP enumeration queries
### Synopsis
| Field | Value |
| -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | 10 Minutes |
| Deduplication Period | 1 Day |
| Required Data | XDR Agent with eXtended Threat Hunting (XTH) |
| Detection Modules | Identity Analytics |
| Detector Tags | LDAP Analytics (Server) |
| ATT\&CK Tactic | Discovery (TA0007) |
| ATT\&CK Technique | Account Discovery (T1087), Permission Groups Discovery: Domain Groups (T1069.002), Domain Trust Discovery (T1482), Remote System Discovery (T1018), System Network Configuration Discovery (T1016) |
| Severity | Informational |
### Description
A user executed multiple LDAP enumeration queries.
### Attacker's Goals
An adversary may utilize the LDAP protocol to gain information on the Active Directory environment and plan its lateral movement over the network.
### Investigative actions
* Where possible, check the legitimacy of the process that executed these LDAP queries.
* Investigate the LDAP search query for any suspicious indicators.
* Determine whether the search query is generic, those search queries (often using wildcards) tend to be more suspicious.
### Variations
A user executed suspicious LDAP enumeration queries
**Synopsis**
| Field | Value |
| ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Discovery (TA0007) |
| ATT\&CK Technique | Account Discovery (T1087), Permission Groups Discovery: Domain Groups (T1069.002), Domain Trust Discovery (T1482), Remote System Discovery (T1018), System Network Configuration Discovery (T1016) |
| Severity | Low |
**Description**
A user executed multiple LDAP enumeration queries.
**Attacker's Goals**
An adversary may utilize the LDAP protocol to gain information on the Active Directory environment and plan its lateral movement over the network.
**Investigative actions**
* Where possible, check the legitimacy of the process that executed these LDAP queries.
* Investigate the LDAP search query for any suspicious indicators.
* Determine whether the search query is generic, those search queries (often using wildcards) tend to be more suspicious.
---
# 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/a-user-executed-multiple-ldap-enumeration-queries.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.