- Home
- Techniques
- Enterprise
- Create Account
Create Account
Sub-techniques (3)
Adversaries may create an account to maintain access to victim systems. With a sufficient level of access, creating such accounts may be used to establish secondary credentialed access that do not require persistent remote access tools to be deployed on the system.
Accounts may be created on the local system or within a domain or cloud tenant. In cloud environments, adversaries may create accounts that only have access to specific services, which can reduce the chance of detection.
Mitigations
| Mitigation | Description |
|---|---|
| Multi-factor Authentication |
Use multi-factor authentication for user and privileged accounts. |
| Network Segmentation |
Configure access controls and firewalls to limit access to domain controllers and systems used to create and manage accounts. |
| Operating System Configuration |
Protect domain controllers by ensuring proper security configuration for critical servers. |
| Privileged Account Management |
Do not allow domain administrator accounts to be used for day-to-day operations that may expose them to potential adversaries on unprivileged systems. |
Detection
Monitor for processes and command-line parameters associated with account creation, such as net user or useradd. Collect data on account creation within a network. Event ID 4720 is generated when a user account is created on a Windows system and domain controller. [1] Perform regular audits of domain and local system accounts to detect suspicious accounts that may have been created by an adversary.
Collect usage logs from cloud administrator accounts to identify unusual activity in the creation of new accounts and assignment of roles to those accounts. Monitor for accounts assigned to admin roles that go over a certain threshold of known admins.