> 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/a-process-queried-the-adfs-database-decryption-key-via-ldap.md).
# A process queried the ADFS database decryption key via LDAP
### 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), Active Directory Federation Services Analytics |
| ATT\&CK Tactic | Credential Access (TA0006) |
| ATT\&CK Technique | Steal or Forge Authentication Certificates (T1649) |
| Severity | Low |
### Description
A process queried the ADFS database decryption key (DKM key) via LDAP.
### Attacker's Goals
* An attacker wanting to perform a golden SAML attack will want to steal the ADFS token-signing certificates.
* To steal the token-signing certificates, the attacker will need to access the ADFS database
* To access the encrypted ADFS database, an attacker will attempt to retrieve the decryption key via an LDAP query.
### Investigative actions
* Check if the LDAP search query was allowed for the user (logged on at event time) or process.
* Check for unusual ADFS logins.
* Check the process that initiated the query.
* Investigate the LDAP search query for any suspicious indicators.
### Variations
LDAP query explicitly queried the ADFS database decryption key (DKM key)
**Synopsis**
| Field | Value |
| ----------------- | -------------------------------------------------- |
| ATT\&CK Tactic | Credential Access (TA0006) |
| ATT\&CK Technique | Steal or Forge Authentication Certificates (T1649) |
| Severity | Medium |
**Description**
A process queried the ADFS database decryption key (DKM key) via LDAP.
**Attacker's Goals**
* An attacker wanting to perform a golden SAML attack will want to steal the ADFS token-signing certificates.
* To steal the token-signing certificates, the attacker will need to access the ADFS database
* To access the encrypted ADFS database, an attacker will attempt to retrieve the decryption key via an LDAP query.
**Investigative actions**
* Check if the LDAP search query was allowed for the user (logged on at event time) or process.
* Check for unusual ADFS logins.
* Check the process that initiated the query.
* Investigate the LDAP search query for any suspicious indicators.
A process explicitly queried the ADFS database decryption key (DKM key) via LDAP
**Synopsis**
| Field | Value |
| ----------------- | -------------------------------------------------- |
| ATT\&CK Tactic | Credential Access (TA0006) |
| ATT\&CK Technique | Steal or Forge Authentication Certificates (T1649) |
| Severity | Medium |
**Description**
A process queried the ADFS database decryption key (DKM key) via LDAP.
**Attacker's Goals**
* An attacker wanting to perform a golden SAML attack will want to steal the ADFS token-signing certificates.
* To steal the token-signing certificates, the attacker will need to access the ADFS database
* To access the encrypted ADFS database, an attacker will attempt to retrieve the decryption key via an LDAP query.
**Investigative actions**
* Check if the LDAP search query was allowed for the user (logged on at event time) or process.
* Check for unusual ADFS logins.
* Check the process that initiated the query.
* Investigate the LDAP search query for any suspicious indicators.
LDAP query queried the ADFS database decryption key (DKM key)
**Synopsis**
| Field | Value |
| ----------------- | -------------------------------------------------- |
| ATT\&CK Tactic | Credential Access (TA0006) |
| ATT\&CK Technique | Steal or Forge Authentication Certificates (T1649) |
| Severity | Low |
**Description**
A process queried the ADFS database decryption key (DKM key) via LDAP.
**Attacker's Goals**
* An attacker wanting to perform a golden SAML attack will want to steal the ADFS token-signing certificates.
* To steal the token-signing certificates, the attacker will need to access the ADFS database
* To access the encrypted ADFS database, an attacker will attempt to retrieve the decryption key via an LDAP query.
**Investigative actions**
* Check if the LDAP search query was allowed for the user (logged on at event time) or process.
* Check for unusual ADFS logins.
* Check the process that initiated the query.
* Investigate the LDAP search query for any suspicious indicators.
---
# 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/a-process-queried-the-adfs-database-decryption-key-via-ldap.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.