ID | Name |
---|---|
T1098.001 | Additional Cloud Credentials |
T1098.002 | Additional Email Delegate Permissions |
T1098.003 | Additional Cloud Roles |
T1098.004 | SSH Authorized Keys |
T1098.005 | Device Registration |
An adversary may add additional roles or permissions to an adversary-controlled cloud account to maintain persistent access to a tenant. For example, they may update IAM policies in cloud-based environments or add a new global administrator in Office 365 environments.[1][2][3][4] With sufficient permissions, a compromised account can gain almost unlimited access to data and settings (including the ability to reset the passwords of other admins).[5][4]
This account modification may immediately follow Create Account or other malicious account activity. Adversaries may also modify an existing Valid Accounts that they have compromised. This could lead to privilege escalation, particularly if the roles added allow for lateral movement to additional accounts. For example, in Azure AD environments, an adversary with the Application Administrator role can add Additional Cloud Credentials to their application's service principal. In doing so the adversary would be able to gain the service principal’s roles and permissions, which may be different from those of the Application Administrator.[6]
ID | Name | Description |
---|---|---|
G0016 | APT29 |
APT29 has granted |
ID | Mitigation | Description |
---|---|---|
M1032 | Multi-factor Authentication |
Use multi-factor authentication for user and privileged accounts. |
M1026 | Privileged Account Management |
Ensure that all accounts use the least privileges they require. |
ID | Data Source | Data Component |
---|---|---|
DS0002 | User Account | User Account Modification |
Collect activity logs from IAM services and cloud administrator accounts to identify unusual activity in the assignment of roles to those accounts. Monitor for accounts assigned to admin roles that go over a certain threshold of known admins.