Account Manipulation: Additional Cloud Roles
- ID
- T1098.003
- Tactics
- TA0003 Persistence, TA0004 Privilege Escalation
- Sub-technique of
- T1098 Account Manipulation
- Platforms
- IaaS, Identity Provider, Office Suite, SaaS
- Data sources
- User Account Modification
- Source
- attack.mitre.org
- MITRE last modified
- 25 Oct 2025
An adversary may add additional roles or permissions to an adversary-controlled cloud account to maintain persistent access to a tenant. For example, adversaries may update IAM policies in cloud-based environments or add a new global administrator in Office 365 environments.[2][3][4][5] 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).[6]
[5]
This account modification may immediately follow Create Account or other malicious account activity. Adversaries may also modify 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 AWS environments, an adversary with appropriate permissions may be able to use the CreatePolicyVersion API to define a new version of an IAM policy or the AttachUserPolicy API to attach an IAM policy with additional or distinct permissions to a compromised user account.[7]
In some cases, adversaries may add roles to adversary-controlled accounts outside the victim cloud tenant. This allows these external accounts to perform actions inside the victim tenant without requiring the adversary to Create Account or modify a victim-owned account.[8]
Detection
- DET0277 Detection Strategy for Role Addition to Cloud Accounts
Data components: User Account Modification
Mitigations (3)
- M1018 User Account Management
Ensure that low-privileged user accounts do not have permissions to add permissions to accounts or update IAM policies.
- M1026 Privileged Account Management
Ensure that all accounts use the least privileges they require. In Azure AD environments, consider using Privileged Identity Management (PIM) to define roles that require two or more approvals before assignment to users.[1]
- M1032 Multi-factor Authentication
Use multi-factor authentication for user and privileged accounts.
Groups (3)
References
- Microsoft Requests for Azure AD Roles in Privileged Identity Management
- AWS IAM Policies and Permissions
- Google Cloud IAM Policies
- Microsoft Support O365 Add Another Admin, October 2019
- Microsoft O365 Admin Roles
- Expel AWS Attacker
- Rhino Security Labs AWS Privilege Escalation
- Invictus IR DangerDev 2024
