Account Manipulation: Additional Cloud Roles T1098.003
Tactics: Persistence, Privilege Escalation
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. 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).
Authoring guide
Patterns shared across the 107 rules above: which fields they filter on, what specific values they look for, and what they exclude. The catalog normalizes field names across vendors so Sigma's Image, Elastic's process.name, and Splunk's process_name collapse into one row. Each rule contributes at most once per row.
Fields filtered most (100 distinct)
The fields most rules look at when detecting this technique. The How column shows the operators authors use (eq, wildcard, regex_match, match) and how often each appears. Sample values are concrete examples to start from, not an exhaustive list.
Top indicator values (308 distinct)
Specific (field, operator, value) combinations the rules check for, ranked by how many rules under this technique use each one. The Corpus reach column counts how many rules across the entire catalog (any technique) check the same combination. High numbers point to widely-used indicators that are likely noisy on their own; combine them with another condition for useful signal. Blank means the combination is specific to rules under this technique. Click a value to expand the rules under this technique that use it.
Exclusions (4 distinct)
Field/operator/value combinations excluded by rules under this technique (top-level not() clauses), sorted by how many rules exclude each. These are the false-positive paths the community has learned to filter out. A new rule that ignores the high-count entries here will likely fire on the same noisy paths. Click a value to expand the rules under this technique that exclude it.
Rules under this technique
Every rule in the catalog tagged with this technique, grouped by vendor. Click a rule title for its full predicates, exclusions, and indicators.
Sigma 9 rules
- App Assigned To Azure RBAC/Microsoft Entra Role
- App Granted Privileged Delegated Or App Permissions
- Github Outside Collaborator Detected
- Google Workspace Application Access Level Modified
- Granting Of Permissions To An Account
- IAM Admin Policy Attached
- IAM Policy Attachment Attempt
- Okta Admin Role Assigned to an User or Group
- User Added to an Administrator's Azure AD Role
Elastic 30 rules
- Administrator Privileges Assigned to an Okta Group
- AWS EC2 Instance Interaction with IAM Service
- AWS IAM AdministratorAccess Policy Attached to Group
- AWS IAM AdministratorAccess Policy Attached to Role
- AWS IAM AdministratorAccess Policy Attached to User
- AWS IAM Assume Role Policy Update
- AWS IAM Login Profile Added to User
- AWS IAM Roles Anywhere Profile Creation
- AWS IAM Roles Anywhere Trust Anchor Created with External CA
- AWS IAM User Addition to Group
- AWS Sensitive IAM Operations Performed via CloudShell
- AWS STS AssumeRoot by Rare User and Member Account
- Azure Event Hub Authorization Rule Created or Updated
- Azure RBAC Built-In Administrator Roles Assigned
- Entra ID Elevated Access to User Access Administrator
- Entra ID Global Administrator Role Assigned
- Entra ID Global Administrator Role Assigned (PIM User)
- Entra ID Privileged Identity Management (PIM) Role Modified
- GCP IAM Custom Role Creation
- GCP Storage Bucket Permissions Modification
- GitHub Owner Role Granted To User
- Google Workspace Admin Role Assigned to a User
- Google Workspace Custom Admin Role Created
- Google Workspace User Organizational Unit Changed
- M365 Exchange Management Group Role Assigned
- M365 Identity Global Administrator Role Assigned
- M365 SharePoint Site Administrator Added
- New GitHub Owner Added
- New User Added To GitHub Organization
- Okta User Assigned Administrator Role
Splunk 19 rules
- Azure AD Admin Consent Bypassed by Service Principal
- Azure AD Application Administrator Role Assigned
- Azure AD FullAccessAsApp Permission Assigned
- Azure AD Global Administrator Role Assigned
- Azure AD PIM Role Assigned
- Azure AD PIM Role Assignment Activated
- Azure AD Privileged Role Assigned
- Azure AD Privileged Role Assigned to Service Principal
- Azure AD Service Principal Privilege Escalation
- Azure AD Tenant Wide Admin Consent Granted
- O365 Admin Consent Bypassed by Service Principal
- O365 Application Available To Other Tenants
- O365 FullAccessAsApp Permission Assigned
- O365 High Privilege Role Granted
- O365 Mailbox Read Access Granted to Application
- O365 Privileged Role Assigned
- O365 Privileged Role Assigned To Service Principal
- O365 Service Principal Privilege Escalation
- O365 Tenant Wide Admin Consent Granted
Kusto 29 rules
- Admin promotion after Role Management Application Permission Grant
- AWS Security Hub - Detect IAM Policies allowing full administrative privileges
- AWSCloudTrail - CloudFormation policy created then used for privilege escalation
- AWSCloudTrail - Created CRUD S3 policy and then privilege escalation
- AWSCloudTrail - Creation of CRUD DynamoDB policy and then privilege escalation
- AWSCloudTrail - Creation of CRUD KMS policy and then privilege escalation
- AWSCloudTrail - Creation of CRUD Lambda policy and then privilege escalation
- AWSCloudTrail - Creation of DataPipeline policy and then privilege escalation
- AWSCloudTrail - Creation of EC2 policy and then privilege escalation
- AWSCloudTrail - Creation of Glue policy and then privilege escalation
- AWSCloudTrail - Creation of Lambda policy and then privilege escalation
- AWSCloudTrail - Creation of new CRUD IAM policy and then privilege escalation
- AWSCloudTrail - Creation of SSM policy and then privilege escalation
- AWSCloudTrail - Policy version set to default
- AWSCloudTrail - Privilege escalation via CloudFormation policy
- AWSCloudTrail - Privilege escalation via CRUD DynamoDB policy
- AWSCloudTrail - Privilege escalation via CRUD IAM policy
- AWSCloudTrail - Privilege escalation via CRUD KMS policy
- AWSCloudTrail - Privilege escalation via CRUD Lambda policy
- AWSCloudTrail - Privilege escalation via CRUD S3 policy
- AWSCloudTrail - Privilege escalation via DataPipeline policy
- AWSCloudTrail - Privilege escalation via EC2 policy
- AWSCloudTrail - Privilege escalation via Glue policy
- AWSCloudTrail - Privilege escalation via Lambda policy
- AWSCloudTrail - Privilege escalation via SSM policy
- AWSCloudTrail - Privilege escalation with admin managed policy
- AWSCloudTrail - Privilege escalation with AdministratorAccess managed policy
- AWSCloudTrail - Privilege escalation with FullAccess managed policy
- Microsoft Entra ID Role Management Permission Grant
YARA-L 9 rules
- Entra ID Add User Outside PIM
- Entra ID Add User To Admin Role
- Entra ID Recently Created User Assigned an Entra ID Role
- GCP Admin Privileged Roles Added To Service Accounts
- Google Workspace Admin Role Assignment
- Google Workspace Custom Admin Role Created
- Google Workspace User Ou Changed
- O365 Add User To Admin Role
- O365 Recently Created Entra ID User Assigned Roles
Panther 11 rules
- Anthropic Primary Owner Transferred
- Azure Privileged or Elevated Role Assignment
- Azure User Elevated to User Access Administrator Role
- Crowdstrike Admin Role Assigned
- Crowdstrike New Admin User Created
- GCP Inbound SSO Profile Created
- GCP Workforce Pool Created or Updated
- GCP Workload Identity Pool Created or Updated
- OpenAI Admin Role Assignment
- Slack User Privilege Escalation
- ZIA Additional Cloud Roles