> 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/privileged-certificate-request-via-certificate-template.md).
# Privileged certificate request via certificate template
### Synopsis
| Field | Value |
| -------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | N/A (single event) |
| Deduplication Period | 1 Day |
| Required Data | Requires one of the following data sources:
Windows Event Collector OR XDR Agent with eXtended Threat Hunting (XTH)
|
| Detection Modules | Identity Analytics |
| Detector Tags | Active Directory Certificate Services Analytics |
| ATT\&CK Tactic | Privilege Escalation (TA0004) |
| ATT\&CK Technique | Valid Accounts: Domain Accounts (T1078.002) |
| Severity | Informational |
### Description
A privileged certificate was requested via certificate template.
### Attacker's Goals
An attacker may attempt to exploit the Active Directory Certificate Services to escalate privileges to a domain controller or privileged account.
### Investigative actions
* Check if this is a legitimate certificate request.
* Check if the certificate issued was used to request a Kerberos ticket.
* Investigate actions done with the issued certificate and its owner.
* Check for possible NTLM relay alerts.
### Variations
Suspicious privileged certificate request denied via certificate template
**Synopsis**
| Field | Value |
| ----------------- | ------------------------------------------- |
| ATT\&CK Tactic | Privilege Escalation (TA0004) |
| ATT\&CK Technique | Valid Accounts: Domain Accounts (T1078.002) |
| Severity | Medium |
**Description**
A suspicious privileged certificate request was denied via certificate template.
**Attacker's Goals**
An attacker may attempt to exploit the Active Directory Certificate Services to escalate privileges to a domain controller or privileged account.
**Investigative actions**
* Check if this is a legitimate certificate request.
* Check if the certificate issued was used to request a Kerberos ticket.
* Investigate actions done with the issued certificate and its owner.
* Check for possible NTLM relay alerts.
Suspicious privileged certificate request via certificate template
**Synopsis**
| Field | Value |
| ----------------- | ------------------------------------------- |
| ATT\&CK Tactic | Privilege Escalation (TA0004) |
| ATT\&CK Technique | Valid Accounts: Domain Accounts (T1078.002) |
| Severity | Low |
**Description**
A suspicious privileged certificate was requested via certificate template.
**Attacker's Goals**
An attacker may attempt to exploit the Active Directory Certificate Services to escalate privileges to a domain controller or privileged account.
**Investigative actions**
* Check if this is a legitimate certificate request.
* Check if the certificate issued was used to request a Kerberos ticket.
* Investigate actions done with the issued certificate and its owner.
* Check for possible NTLM relay alerts.
---
# 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/privileged-certificate-request-via-certificate-template.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.