Has run nltest.exe /domain_trusts on compromised systems to discover domain relationships.1
Domain Trust Discovery T1482
- Tactic
- Discovery
- Platform
- Windows
- Version
- 1.2
- Created
- 14 February 2019
- Last modified
- 12 May 2026
- Contributors
- Dave Westgard; Elia Florio, Microsoft; Mnemonic; RedHuntLabs, @redhuntlabs; ExtraHop
Adversaries may attempt to gather information on domain trust relationships that may be used to identify lateral movement opportunities in Windows multi-domain/forest environments. Domain trusts provide a mechanism for a domain to allow access to resources based on the authentication procedures of another domain.[1] Domain trusts allow the users of the trusted domain to access resources in the trusting domain. The information discovered may help the adversary conduct SID-History Injection, Pass the Ticket, and Kerberoasting.[2][3] Domain trusts can be enumerated using the DSEnumerateDomainTrusts() Win32 API call, .NET methods, and LDAP.[3] The Windows utility Nltest is known to be used by adversaries to enumerate domain trusts.[4]
Domain Trust Discovery MITRE reference T1482
10 groups have been recorded using this technique. Newest first; each entry carries MITRE’s procedure text and a link to the group’s full record. Click a name to filter the rules below.
Has used Windows native utility Nltest nltest.exe for discovery.1
Has enumerated domain accounts and access during intrusions.1
Enumerated Active Directory information and trust relationships during operations.12
Uses the built-in Nltest utility or tools such as AdFind to enumerate Active Directory trusts in victim environments.1
Has used Nltest to obtain information about domain controllers.1
All 10 groups for this technique · 6 newest in this preview
3 campaigns have been recorded using this technique. Listed newest first; dates are year-granularity and attribution is MITRE’s.
Leviathan performed Active Directory enumeration of victim environments during Leviathan Australian Intrusions.1
During C0015, the threat actors used the command nltest /domain_trusts /all_trusts to enumerate domain trusts.1
During the SolarWinds Compromise, APT29 used the Get-AcceptedDomain PowerShell cmdlet to enumerate accepted domains through an Exchange Management Shell.1 They also used AdFind to enumerate domains and to discover trust between federated domains.23
All 3 campaigns for this technique
20 software entries are documented implementing this technique. MITRE files each as a tool or as malware; newest first, then by how many groups carry them.
Can gather Active Directory domain information.1
Can run C:\Windows\System32\cmd.exe /c nltest /domain_trusts to discover domain trusts.12
Can identify Active Directory information and related items.1
Includes modules for collecting information on local domain users and permissions.1
Will gather information concerning the Windows Domain the victim machine is a member of during execution.1
Can profile compromised systems to identify domain trust relationships.12
All 20 software entries for this technique · 6 newest in this preview
Offense vs defense T1482
Is defensive coverage keeping up with adversary use? Eight counts, each ranked against all 697 ATT&CK techniques. Attack sits left, defense right, so a shape leaning left means adversaries are better documented here than defenders are equipped. Hover any spoke for its percentile and the share of techniques that have more. The timeline below shows when each side arrived.
How it got here
Adversary activity (campaign spans) over cumulative rule output. Each source is plotted independently from zero, so neither line includes the other. Campaign dates are year-granularity.
Domain Trust Discovery detection strategy DET0007
MITRE names one behaviour worth catching for this technique and breaks it into 1 analytic, one per platform. Each carries the log sources it needs and the fields you tune per environment.
Detection of Domain Trust Discovery via API, Script, and CLI Enumeration
AN0016 · Windows
Adversary uses nltest, PowerShell, or Win32/.NET API to enumerate domain trust relationships (via DSEnumerateDomainTrusts, GetAllTrustRelationships, or LDAP queries), followed by discovery or authentication staging.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| Module LoadDC0016 | WinEventLog:Sysmon | EventCode=7 |
| Process CreationDC0032 | WinEventLog:Sysmon | EventCode=1 |
| Process AccessDC0035 | WinEventLog:Sysmon | EventCode=10 |
| Command ExecutionDC0064 | WinEventLog:PowerShell | Get-ADTrust|GetAllTrustRelationships |
| Active Directory Object AccessDC0071 | WinEventLog:Security | EventCode=4662 |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| ParentImage | Tune based on expected script hosts or authorized administrators invoking trust enumeration. |
| TimeWindow | Correlate enumeration + subsequent Kerberos activity or DC interaction within a bounded window. |
| UserContext | Prioritize detection for non-admin or unexpected user accounts performing enumeration. |
| API_Name | Flag uncommon or low-prevalence API calls like DSEnumerateDomainTrusts for inspection. |
Map the trusts within existing domains/forests and keep trust relationships to a minimum.
Employ network segmentation for sensitive domains..
Tests from Atomic Red Team (MIT licence) · technique definition