ID | Name |
---|---|
T1136.001 | Local Account |
T1136.002 | Domain Account |
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.[1][2][3][4][5]
Adversaries may create accounts that only have access to specific cloud services, which can reduce the chance of detection.
ID | Name | Description |
---|---|---|
S0677 | AADInternals |
AADInternals can create new Azure AD users.[6] |
G0016 | APT29 |
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 |
Collect usage logs from cloud user and 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.