MITRE ATT&CKsub-technique

T1078.001 Default Accounts

Published 2020-03-13 Modified 2026-05-12 Official page ↗
Domain
enterprise
Tactics
Stealth, Persistence, Privilege Escalation, Initial Access
Platforms
Containers, ESXi, IaaS, Identity Provider, Linux, macOS, Network Devices, Office Suite, SaaS, Windows
Version
2.0
Created
2020-03-13

Description

Adversaries may obtain and abuse credentials of a default account as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Default accounts are those that are built-into an OS, such as the Guest or Administrator accounts on Windows systems. Default accounts also include default factory/provider set accounts on other types of systems, software, or devices, including the root user account in AWS, the root user account in ESXi, and the default service account in Kubernetes. Default accounts are not limited to client machines; rather, they also include accounts that are preset for equipment such as network devices and computer applications, whether they are internal, open source, or commercial. Appliances that come preset with a username and password combination pose a serious threat to organizations that do not change it post installation, as they are easy targets for an adversary. Similarly, adversaries may also utilize publicly disclosed or stolen Private Keys or credential materials to legitimately connect to remote environments via Remote Services. Default accounts may be created on a system after initial setup by connecting or integrating it with another application. For example, when an ESXi server is connected to a vCenter server, a default privileged account called `vpxuser` is created on the ESXi server. If a threat actor is able to compromise this account’s credentials (for example, via Exploitation for Credential Access on the vCenter host), they will then have access to the ESXi server.

Related

Subtechnique of · MITRE ATT&CK (1)

  • T1078 Valid Accounts technique

Tactic · MITRE ATT&CK (4)

Referenced by MITRE ATT&CK · mitigates (2)

  • M1032 Multi-factor Authentication mitigation
  • M1027 Password Policies mitigation

Referenced by MITRE ATT&CK · uses (7)

  • G1048 UNC3886 group
  • C0038 HomeLand Justice campaign
  • G1016 FIN13 group
  • G1003 Ember Bear group
  • S0603 Stuxnet software (malware)
  • S0537 HyperStack software (malware)
  • G0059 Magic Hound group

Referenced by CAPEC · att&ck technique (1)

  • CAPEC-70 Try Common or Default Usernames and Passwords attack pattern

Referenced by Compliance · mitigates (18)

  • CIS-4.7 Manage Default Accounts on Enterprise Assets and Software CIS Safeguard v8.1
  • CIS-5.2 Use Unique Passwords CIS Safeguard v8.1
  • CIS-5.3 Disable Dormant Accounts CIS Safeguard v8.1
  • CIS-6.5 Require MFA for Administrative Access CIS Safeguard v8.1
  • NIST-AC-2 Account Management NIST 800-53 control
  • NIST-AC-5 Separation of Duties NIST 800-53 control
  • NIST-AC-6 Least Privilege NIST 800-53 control
  • NIST-CA-7 Continuous Monitoring NIST 800-53 control
  • NIST-SA-10 Developer Configuration Management NIST 800-53 control
  • NIST-SA-11 Developer Testing and Evaluation NIST 800-53 control
  • NIST-SA-15 Development Process, Standards, and Tools NIST 800-53 control
  • NIST-SA-16 Developer-provided Training NIST 800-53 control
  • NIST-SA-17 Developer Security and Privacy Architecture and Design NIST 800-53 control
  • NIST-SA-3 System Development Life Cycle NIST 800-53 control
  • NIST-SA-4 Acquisition Process NIST 800-53 control
  • NIST-SA-8 Security and Privacy Engineering Principles NIST 800-53 control
  • NIST-SC-28 Protection of Information at Rest NIST 800-53 control
  • NIST-SI-4 System Monitoring NIST 800-53 control

References