Create Account

Sub-techniques (1)

A threat actor using credentials with appropriate permissions is able to create an account within an AWS organization that will use the payment method registered to the management or payer account. The theat actor will then be able to create resources and workloads within the newly created account that may not be subject to existing detections. By default, Service Control Policies are not assigned to new accounts during the creation of the account within an organization.

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. (Citation: Microsoft User Creation Event) 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.

References

Technique Information

ID: T1136
Aliases: T1136
Sub-techniques:
Tactics:
  • Persistence
Platforms:
  • Windows
  • Azure AD
  • Office 365
  • IaaS
  • Linux
  • macOS
  • Google Workspace
  • Network
  • Containers
  • SaaS
  • Amazon Web Services (AWS)
Created: 12 Sep 2024
Last Modified: 03 Jun 2025