> 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-gpo-enumeration.md).

# Possible GPO Enumeration

### 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)     |
| Detection Modules    | Identity Analytics                               |
| Detector Tags        | LDAP Analytics (Client), LDAP Analytics (Server) |
| ATT\&CK Tactic       | Discovery (TA0007)                               |
| ATT\&CK Technique    | Group Policy Discovery (T1615)                   |
| Severity             | Informational                                    |

### Description

A possible GPO enumeration via LDAP was performed. Such enumeration may be used during attacks against the organization.

### Attacker's Goals

An attacker is attempting to enumerate Active Directory.

### Investigative actions

* Investigate the LDAP search query for any suspicious indicators.
* Look for additional LDAP queries the user executed that might be suspicious.
* Determine whether the search query is generic. Wide search queries (often using wildcards) tend to be more suspicious. In our case, we are looking for targeted search queries.
* Check if the process executes LDAP search queries as part of its normal behavior.

### Variations

<details>

<summary>Suspicious GPO Enumeration by an LDAP tool</summary>

**Synopsis**

| Field             | Value                          |
| ----------------- | ------------------------------ |
| ATT\&CK Tactic    | Discovery (TA0007)             |
| ATT\&CK Technique | Group Policy Discovery (T1615) |
| Severity          | Medium                         |

**Description**

A possible GPO enumeration via LDAP was performed. Such enumeration may be used during attacks against the organization.

**Attacker's Goals**

An attacker is attempting to enumerate Active Directory.

**Investigative actions**

* Investigate the LDAP search query for any suspicious indicators.
* Look for additional LDAP queries the user executed that might be suspicious.
* Determine whether the search query is generic. Wide search queries (often using wildcards) tend to be more suspicious. In our case, we are looking for targeted search queries.
* Check if the process executes LDAP search queries as part of its normal behavior.

</details>

<details>

<summary>Possible GPO Enumeration by a Suspicious Process</summary>

**Synopsis**

| Field             | Value                          |
| ----------------- | ------------------------------ |
| ATT\&CK Tactic    | Discovery (TA0007)             |
| ATT\&CK Technique | Group Policy Discovery (T1615) |
| Severity          | Low                            |

**Description**

A possible GPO enumeration via LDAP was performed. Such enumeration may be used during attacks against the organization.

**Attacker's Goals**

An attacker is attempting to enumerate Active Directory.

**Investigative actions**

* Investigate the LDAP search query for any suspicious indicators.
* Look for additional LDAP queries the user executed that might be suspicious.
* Determine whether the search query is generic. Wide search queries (often using wildcards) tend to be more suspicious. In our case, we are looking for targeted search queries.
* Check if the process executes LDAP search queries as part of its normal behavior.

</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/possible-gpo-enumeration.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.