> 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/key-credential-attribute-modification.md).
# Key credential attribute modification
### 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 | Credential Access (TA0006) |
| ATT\&CK Technique | Modify Authentication Process (T1556) |
| Severity | Informational |
### Description
A user modified the msDS-KeyCredentialLink attribute for an account, which may indicate a shadow credentials attack.
### Attacker's Goals
An attacker may be attempting to add shadow credentials to an account, gaining persistent unauthorized access.
### Investigative actions
* Follow further PKINIT authentication activity by the modified identity.\* Verify if Windows Hello for Business is enabled, as this is a common benign cause for this activity.\* Check if the modified credential maps to an existing device ID in Entra ID.\* Examine recent activity from the user account, including logon patterns and privilege changes.
### Variations
Possible shadow credentials addition
**Synopsis**
| Field | Value |
| ----------------- | ------------------------------------- |
| ATT\&CK Tactic | Credential Access (TA0006) |
| ATT\&CK Technique | Modify Authentication Process (T1556) |
| Severity | Medium |
**Description**
A user modified the msDS-KeyCredentialLink attribute for an account, which may indicate a shadow credentials attack.
**Attacker's Goals**
An attacker may be attempting to add shadow credentials to an account, gaining persistent unauthorized access.
**Investigative actions**
* Follow further PKINIT authentication activity by the modified identity.\* Verify if Windows Hello for Business is enabled, as this is a common benign cause for this activity.\* Check if the modified credential maps to an existing device ID in Entra ID.\* Examine recent activity from the user account, including logon patterns and privilege changes.
Key credential attribute addition
**Synopsis**
| Field | Value |
| ----------------- | ------------------------------------- |
| ATT\&CK Tactic | Credential Access (TA0006) |
| ATT\&CK Technique | Modify Authentication Process (T1556) |
| Severity | Low |
**Description**
A user modified the msDS-KeyCredentialLink attribute for an account, which may indicate a shadow credentials attack.
**Attacker's Goals**
An attacker may be attempting to add shadow credentials to an account, gaining persistent unauthorized access.
**Investigative actions**
* Follow further PKINIT authentication activity by the modified identity.\* Verify if Windows Hello for Business is enabled, as this is a common benign cause for this activity.\* Check if the modified credential maps to an existing device ID in Entra ID.\* Examine recent activity from the user account, including logon patterns and privilege changes.
---
# 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/key-credential-attribute-modification.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.