> 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/the-ca-policy-editflags-was-queried.md).

# The CA policy EditFlags was queried

### 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                                       |
| Detector Tags        | Active Directory Certificate Services Analytics |
| ATT\&CK Tactic       | Privilege Escalation (TA0004)                   |
| ATT\&CK Technique    | Valid Accounts (T1078)                          |
| Severity             | Medium                                          |

### Description

The CA policy EditFlags was queried.

### Attacker's Goals

* Querying this registry value can indicate an attacker is looking for an enabled EDITF\_ATTRIBUTESUBJECTALTNAME2 flag.
* When this flag is enabled, it allows users to request certificates with a Subject Alternate Name(SAN).
* This can allow an attacker to obtain a certificate with higher privileges.

### Investigative actions

* Check if the action was allowed by the user.
* Monitor certificate enrollments with Subject Alternate Names.
* Check for unusual high privilege users certificate authentications.


---

# 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/the-ca-policy-editflags-was-queried.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.