> 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/ntds-dit-file-written-by-an-uncommon-executable.md).
# NTDS.dit file written by an uncommon executable
### 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 | OS Credential Dumping (T1003), OS Credential Dumping: NTDS (T1003.003) |
| Severity | Low |
### Description
The Active Directory database file was written by an uncommon process to a non-default location.
### Attacker's Goals
Dump the sensitive contents of the database to masquerade as legitimate domain users.
### Investigative actions
* Investigate the nature of the process writing the sensitive file. Is it a standard backup procedure?
* Check the path the file was written to. Is it local? Are there other relevant artifacts in this location?
### Variations
NTDS.dit file written by a remote actor
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------------------------------------------- |
| ATT\&CK Tactic | Credential Access (TA0006) |
| ATT\&CK Technique | OS Credential Dumping (T1003), OS Credential Dumping: NTDS (T1003.003) |
| Severity | High |
**Description**
The Active Directory database file was written to the disk by a remote actor.
**Attacker's Goals**
Dump the sensitive contents of the database to masquerade as legitimate domain users.
**Investigative actions**
* Investigate the nature of the process writing the sensitive file. Is it a standard backup procedure?
* Check the path the file was written to. Is it local? Are there other relevant artifacts in this location?
NTDS.dit file written by a rare executable to a suspicious path
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------------------------------------------- |
| ATT\&CK Tactic | Credential Access (TA0006) |
| ATT\&CK Technique | OS Credential Dumping (T1003), OS Credential Dumping: NTDS (T1003.003) |
| Severity | High |
**Description**
The Active Directory database file was written by a rare process to a suspicious path.
**Attacker's Goals**
Dump the sensitive contents of the database to masquerade as legitimate domain users.
**Investigative actions**
* Investigate the nature of the process writing the sensitive file. Is it a standard backup procedure?
* Check the path the file was written to. Is it local? Are there other relevant artifacts in this location?
NTDS.dit file written by a rare executable
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------------------------------------------- |
| ATT\&CK Tactic | Credential Access (TA0006) |
| ATT\&CK Technique | OS Credential Dumping (T1003), OS Credential Dumping: NTDS (T1003.003) |
| Severity | Medium |
**Description**
The Active Directory database file was written by a rare process to a non-default location.
**Attacker's Goals**
Dump the sensitive contents of the database to masquerade as legitimate domain users.
**Investigative actions**
* Investigate the nature of the process writing the sensitive file. Is it a standard backup procedure?
* Check the path the file was written to. Is it local? Are there other relevant artifacts in this location?
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/ntds-dit-file-written-by-an-uncommon-executable.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.