Valid Accounts: Domain Accounts
- ID
- T1078.002
- Tactics
- TA0001 Initial Access, TA0003 Persistence, TA0004 Privilege Escalation, TA0005 Stealth
- Sub-technique of
- T1078 Valid Accounts
- Platforms
- ESXi, Linux, macOS, Windows
- Data sources
- Logon Session Metadata, Process Creation, Network Connection Creation, User Account Authentication
- Source
- attack.mitre.org
- MITRE last modified
- 12 May 2026
Adversaries may obtain and abuse credentials of a domain account as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion.[1] Domain accounts are those managed by Active Directory Domain Services where access and permissions are configured across systems and services that are part of that domain. Domain accounts can cover users, administrators, and services.[2]
Adversaries may compromise domain accounts, some with a high level of privileges, through various means such as OS Credential Dumping or password reuse, allowing access to privileged resources of the domain.
Detection
- DET0210 Abuse of Domain Accounts
Data components: Logon Session Metadata, Process Creation, Network Connection Creation, User Account Authentication
Mitigations (5)
- M1017 User Training
Applications may send push notifications to verify a login as a form of multi-factor authentication (MFA). Train users to only accept valid push notifications and to report suspicious push notifications.
- M1018 User Account Management
Regularly review and manage domain accounts to ensure that only active, necessary accounts exist. Remove or disable inactive and unnecessary accounts to reduce the risk of adversaries abusing these accounts to gain unauthorized access or move laterally within the network.
- M1026 Privileged Account Management
Audit domain account permission levels routinely to look for situations that could allow an adversary to gain wide access by obtaining credentials of a privileged account. Do not put user or admin domain accounts in the local administrator groups across systems unless they are tightly controlled and use of accounts is segmented, as this is often equivalent to having a local administrator account with the same password on all systems. Follow best practices for design and administration of an enterprise network to limit privileged account use across administrative tiers. Limit credential overlap across systems to prevent access if account credentials are obtained.
- M1027 Password Policies
Implement and enforce strong password policies for domain accounts to ensure passwords are complex, unique, and regularly rotated. This reduces the likelihood of password guessing, credential stuffing, and other attack methods that rely on weak or static credentials.
- M1032 Multi-factor Authentication
Integrating multi-factor authentication (MFA) as part of organizational policy can greatly reduce the risk of an adversary gaining control of valid credentials that may be used for additional tactics such as initial access, lateral movement, and collecting information. MFA can also be used to restrict access to cloud resources and APIs.
Groups (21)
- G0019 Naikon
- G0022 APT3
- G0028 Threat Group-1314
- G0034 Sandworm Team
- G0049 OilRig
- G0059 Magic Hound
- G0092 TA505
- G0102 Wizard Spider
- G0114 Chimera
- G0119 Indrik Spider
- G0143 Aquatic Panda
- G1017 Volt Typhoon
- G1021 Cinnamon Tempest
- G1022 ToddyCat
- G1023 APT5
- G1030 Agrius
- G1040 Play
- G1043 BlackByte
- G1055 VOID MANTICORE
- G1057 ShinyHunters
- G1059 NIMBUS MANTICORE
