Skip to content

T1136.003 Cloud Account

Adversaries may create a cloud account to maintain access to victim systems. With a sufficient level of access, such accounts may be used to establish secondary credentialed access that does not require persistent remote access tools to be deployed on the system.15234

Adversaries may create accounts that only have access to specific cloud services, which can reduce the chance of detection.

Once an adversary has created a cloud account, they can then manipulate that account to ensure persistence and allow access to additional resources - for example, by adding Additional Cloud Credentials or assigning Additional Cloud Roles.

Item Value
ID T1136.003
Sub-techniques T1136.001, T1136.002, T1136.003
Tactics TA0003
Platforms Azure AD, Google Workspace, IaaS, Office 365, SaaS
Version 1.3
Created 29 January 2020
Last Modified 06 March 2023

Procedure Examples

ID Name Description
S0677 AADInternals AADInternals can create new Azure AD users.6
G0016 APT29 APT29 can create new users through Azure AD.7
G1004 LAPSUS$ LAPSUS$ has created global admin accounts in the targeted organization’s cloud instances to gain persistence.8


ID Mitigation Description
M1032 Multi-factor Authentication Use multi-factor authentication for user and privileged accounts.
M1030 Network Segmentation Configure access controls and firewalls to limit access to critical systems and domain controllers. Most cloud environments support separate virtual private cloud (VPC) instances that enable further segmentation of cloud systems.
M1026 Privileged Account Management Do not allow privileged accounts to be used for day-to-day operations that may expose them to potential adversaries on unprivileged systems.


ID Data Source Data Component
DS0002 User Account User Account Creation