ATT&CK coverage › Technique

OS Credential Dumping: NTDS T1003.003

Adversaries may attempt to access or create a copy of the Active Directory domain database in order to steal credential information, as well as obtain other information about domain members such as devices, users, and access rights. By default, the NTDS file (NTDS.dit) is located in <code>%SystemRoot%\NTDS\Ntds.dit</code> of a domain controller.

Events covered

10 catalog events are tagged with this technique by at least one rule.

ProviderEvent IDTitle
Sysmon1Process creation
Sysmon11FileCreate
Security-Auditing4688A new process has been created.
Security-Auditing5145A network share object was checked to see whether client can be granted desired access.
ESENT216
ESENT325
ESENT326
ESENT327
PowerShell4103Payload Context: ContextInfo User Data: UserData.
PowerShell4104Creating Scriptblock text (MessageNumber of MessageTotal).

Authoring guide

Patterns shared across the 20 rules above: which fields they filter on, what specific values they look for, and what they exclude. Field names are normalized across vendors so Sigma's Image, Elastic's process.name, and Splunk's process_name collapse into one row. Each rule contributes at most once per row.

Fields filtered most (11 distinct)

The fields most rules look at when detecting this technique. The How column shows the operators authors use (eq, wildcard, regex_match, match) and how often each appears. Sample values are concrete examples to start from, not an exhaustive list.

FieldRulesHowSample values
Image9ends_with 9, match 2\ntdsutil.exe, \pwsh.exe, \wbadmin.exe, \esentutl.exe, \wsl.exe
CommandLine9match 9\windows\ntds\ntds.dit, \Windows\NTDS\NTDS.dit, \config\SYSTEM, /y , \config\security
OriginalFileName5eq 5WBADMIN.EXE, \esentutl.exe, PowerShell.EXE, wmic.exe, pwsh.dll
TargetFilename5ends_with 5, match 1\ntds.dit, \pwdump.exe, \kirbi, \wce_krbtkts, .ntds.cleartext
ParentImage2match 2, ends_with 1\PerfLogs\, \pwsh.exe, \httpd.exe, \tomcat, \Public\
RelativeTargetName2match 2, eq 1SYSTEM32\, .tmp, Windows\NTDS\ntds.dit, \sqldmpr, \hiberfil
ScriptBlockText1match 1).Create(, Win32_ShadowCopy, ClientAccessible
Data1match 1ntds.dit
Provider_Name1eq 1ESENT
ShareName1eq 1\\\\\*\\ADMIN$
Payload1match 1BootKey , Get-ADDBAccount, DatabasePath

Top indicator values (138 distinct)

Specific (field, operator, value) combinations the rules check for, ranked by how many rules under this technique use each one. The Corpus reach column counts how many rules across the entire catalog (any technique) check the same combination. High numbers point to widely-used indicators that are likely noisy on their own; combine them with another condition for useful signal. Blank means the combination is specific to rules under this technique.

FieldKindValueRules (here)Corpus reach
CommandLinematch\windows\ntds\ntds.dit22
Imageends_with\ntdsutil.exe24
TargetFilenameends_with\ntds.dit22
ParentImagematch\PerfLogs\22
ParentImagematch\Temp\22
ParentImagematch\tomcat26
ParentImagematch\Public\22
ParentImagematch\apache22
ParentImagematch\AppData\22
Imageends_with\pwsh.exe2140
Imagematch\Public\22
Imagematch\AppData\29
Imageends_with\powershell.exe2143
Imagematch\PerfLogs\23
Imagematch\Temp\25
OriginalFileNameeqWBADMIN.EXE26
Imageends_with\wbadmin.exe26
CommandLinematch\config\SYSTEM22
CommandLinematch\config\SAM22
CommandLinematch\Windows\NTDS\NTDS.dit22

Rules under this technique

Every rule in the catalog tagged with this technique, grouped by vendor. Click a rule title for its full predicates, exclusions, and indicators.

Sigma 20 rules