> 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/unusual-access-to-the-windows-internal-database-on-an-adfs-server.md).

# Unusual access to the Windows Internal Database on an ADFS server

### 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) |
| ATT\&CK Tactic       | Credential Access (TA0006)                   |
| ATT\&CK Technique    | Credentials from Password Stores (T1555)     |
| Severity             | Informational                                |

### Description

The Windows Internal Database (WID) was queried in an unusual way on an ADFS server.

### Attacker's Goals

* Attackers can attempt to extract and decrypt the ADFS certificate that is used to sign SAML tokens, and fabricate a new SAML token.

### Investigative actions

* See whether this was a legitimate action.
* Follow the causality chain/user/host activities.
* Monitor suspicious LDAP queries to the ADFS container in Active Directory.
* Check the possibility of a compromised ADFS server.
* Check for unusual Azure AD authentications.
* Check for unusual logins.

### Variations

<details>

<summary>Suspicious access to the Windows Internal Database on an ADFS server</summary>

**Synopsis**

| Field             | Value                                    |
| ----------------- | ---------------------------------------- |
| ATT\&CK Tactic    | Credential Access (TA0006)               |
| ATT\&CK Technique | Credentials from Password Stores (T1555) |
| Severity          | Low                                      |

**Description**

The Windows Internal Database (WID) was queried in an unusual way on an ADFS server.

**Attacker's Goals**

* Attackers can attempt to extract and decrypt the ADFS certificate that is used to sign SAML tokens, and fabricate a new SAML token.

**Investigative actions**

* See whether this was a legitimate action.
* Follow the causality chain/user/host activities.
* Monitor suspicious LDAP queries to the ADFS container in Active Directory.
* Check the possibility of a compromised ADFS server.
* Check for unusual Azure AD authentications.
* Check for unusual logins.

</details>


---

# 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/unusual-access-to-the-windows-internal-database-on-an-adfs-server.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.