> 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/pkinit-tgt-authentication-request.md).
# PKINIT TGT authentication request
### 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 | Lateral Movement (TA0008), Privilege Escalation (TA0004) |
| ATT\&CK Technique | Use Alternate Authentication Material (T1550), Valid Accounts (T1078) |
| Severity | Informational |
### Description
A Kerberos TGT was requested using PKINIT. This may indicate an attack on Active Directory Certificate Services (AD CS), such as shadow credential exploitation or certificate-based authentication abuse.
### Attacker's Goals
Gain unauthorized access to high-privilege accounts by abusing certificate-based authentication mechanisms.
### Investigative actions
* Verify if Windows Hello for Business (WHfB) is deployed and actively used in the environment, as it may explain the PKINIT activity.
* Inspect the Key Credentials attribute of the target account for recent modifications.
* Review associated service tickets or lateral movement activities tied to the target account.
* Investigate unusual certificate issuance or PKI activities.
### Variations
Suspicious PKINIT TGT authentication request
**Synopsis**
| Field | Value |
| ----------------- | --------------------------------------------------------------------- |
| ATT\&CK Tactic | Lateral Movement (TA0008), Privilege Escalation (TA0004) |
| ATT\&CK Technique | Use Alternate Authentication Material (T1550), Valid Accounts (T1078) |
| Severity | Medium |
**Description**
A Kerberos TGT was requested using PKINIT. This may indicate an attack on Active Directory Certificate Services (AD CS), such as shadow credential exploitation or certificate-based authentication abuse.
**Attacker's Goals**
Gain unauthorized access to high-privilege accounts by abusing certificate-based authentication mechanisms.
**Investigative actions**
* Verify if Windows Hello for Business (WHfB) is deployed and actively used in the environment, as it may explain the PKINIT activity.
* Inspect the Key Credentials attribute of the target account for recent modifications.
* Review associated service tickets or lateral movement activities tied to the target account.
* Investigate unusual certificate issuance or PKI activities.
Abnormal PKINIT TGT authentication request
**Synopsis**
| Field | Value |
| ----------------- | --------------------------------------------------------------------- |
| ATT\&CK Tactic | Lateral Movement (TA0008), Privilege Escalation (TA0004) |
| ATT\&CK Technique | Use Alternate Authentication Material (T1550), Valid Accounts (T1078) |
| Severity | Low |
**Description**
A Kerberos TGT was requested using PKINIT. This may indicate an attack on Active Directory Certificate Services (AD CS), such as shadow credential exploitation or certificate-based authentication abuse.
**Attacker's Goals**
Gain unauthorized access to high-privilege accounts by abusing certificate-based authentication mechanisms.
**Investigative actions**
* Verify if Windows Hello for Business (WHfB) is deployed and actively used in the environment, as it may explain the PKINIT activity.
* Inspect the Key Credentials attribute of the target account for recent modifications.
* Review associated service tickets or lateral movement activities tied to the target account.
* Investigate unusual certificate issuance or PKI activities.
---
# 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/pkinit-tgt-authentication-request.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.