T1098.003 CrowdStrike LogScale · LogScale

Detect Additional Cloud Roles in CrowdStrike LogScale

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. This account modification may immediately follow account creation or other malicious account activity. Adversaries may also modify existing valid accounts that they have compromised, potentially leading to privilege escalation and lateral movement to additional accounts. In some cases, adversaries may add roles to adversary-controlled accounts outside the victim cloud tenant, allowing external accounts to perform actions inside the victim tenant. Threat groups such as Scattered Spider, LAPSUS$, and Storm-0501 have used this technique to gain persistent administrative access to cloud environments.

MITRE ATT&CK

Tactic
Persistence Privilege Escalation
Technique
T1098 Account Manipulation
Sub-technique
T1098.003 Additional Cloud Roles
Canonical reference
https://attack.mitre.org/techniques/T1098/003/

LogScale Detection Query

CrowdStrike LogScale (LogScale)
cql
// CrowdStrike LogScale — Azure AD / O365 Cloud Role Assignment Detection (T1098.003)
// Requires Azure audit and O365 management activity ingested via Falcon LogScale Data Connector or equivalent
// Adjust tag/repository filters to match your ingestion configuration
operation := coalesce(operationName, Operation, OperationName, "")
| initiated_by := coalesce(initiatedByUserPrincipalName, UserId, caller, ActorID, "")
| target_user := coalesce(targetUserPrincipalName, TargetObjectID, ObjectId, "")
| role_assigned := coalesce(newRoleValue, roleDisplayName, ModifiedProperties_NewValue, "")
| source_ip := coalesce(initiatedByIPAddress, callerIpAddress, ClientIP, "")
| result := coalesce(resultType, ResultStatus, ActivityStatus, "")
| operation = /(?i)(add member to role|add eligible member|roleAssignments\/write|elevateAccess|assign directory role|roledefinitions\/write)/
| test(result = /(?i)(^success|^succeeded|^$)/)
| is_high_privilege := if(
    test(role_assigned = /(?i)(global administrator|company administrator|privileged role administrator|security administrator|exchange administrator|sharepoint administrator|user access administrator|privileged authentication administrator|hybrid identity administrator|application administrator|cloud application administrator|owner|contributor)/),
    "true",
    "false"
  )
| table([_time, operation, initiated_by, target_user, role_assigned, source_ip, is_high_privilege, result])
| sort(by=_time, order=desc)
| sort(by=is_high_privilege, order=desc)
high severity medium confidence

CrowdStrike LogScale (Humio CQL) query detecting cloud role assignment events from Microsoft Azure AD audit, Azure Activity, and Office 365 management activity data ingested into LogScale. Uses coalesce to normalize field names across differing source schemas and applies regex matching for operation type and high-privilege role name classification. Field names may require adjustment based on customer-specific ingestion pipeline configuration.

Data Sources

Azure Audit Logs ingested via Falcon LogScale Data ConnectorOffice 365 Management Activity ingested via Falcon LogScale Data ConnectorAzure Activity Logs ingested via Falcon LogScale Data Connector

Required Tables

LogScale repositories or indexes containing Microsoft Azure or O365 log data — exact repository names vary by deployment

False Positives & Tuning

  • Service account role assignments executed by IaC pipelines such as Terraform or Ansible during automated Azure resource provisioning
  • Privileged Identity Management PIM role activations by authorized administrators with a legitimate and documented need for temporary elevation
  • Bulk role assignments performed during Azure tenant migration projects or enterprise-scale SaaS application integration initiatives
  • Microsoft Entra ID Lifecycle Workflow automatic role grants triggered by HR system joiner or mover events via SCIM provisioning
Download portable Sigma rule (.yml)

Other platforms for T1098.003


Testing Methodology

Validate this detection against 4 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.

  1. Test 1Assign Global Administrator Role to User via Azure AD PowerShell

    Expected signal: Azure AD AuditLogs: OperationName 'Add member to role' with TargetResources containing the target UPN and RoleName 'Global Administrator'. InitiatedBy will show the executing account's UPN and IP address. Event appears in AuditLogs within 5-15 minutes. Unified Audit Log: RecordType 8, Operation 'Add member to role.' with similar details.

  2. Test 2Assign Azure Subscription Owner Role via Az PowerShell (RBAC Escalation)

    Expected signal: AzureActivity log: OperationNameValue 'Microsoft.Authorization/roleAssignments/write' with ActivityStatusValue 'Success', Caller set to the executing account, ResourceId containing the subscription scope and roleAssignment GUID. Event appears in AzureActivity within 2-5 minutes.

  3. Test 3Use elevateAccess API to Gain User Access Administrator at Root Scope

    Expected signal: AzureActivity log: OperationNameValue 'Microsoft.Authorization/elevateAccess/action' with ActivityStatusValue 'Success', Caller set to the Global Admin account. A second event 'Microsoft.Authorization/roleAssignments/write' at scope '/' will also appear as the role is auto-assigned.

  4. Test 4Add External Guest Account to Privileged Role via Microsoft Graph API

    Expected signal: Azure AD AuditLogs: OperationName 'Add member to role' with TargetResources showing the guest account UPN (ending in #EXT# or external domain) and RoleName 'Security Administrator'. InitiatedBy shows the account that executed the Graph API call with its IP address. Graph API calls appear as 'Microsoft Graph' in the InitiatedBy.app field when authenticated via service principal.

Unlock Pro Content

Get the full detection package for T1098.003 including response playbook, investigation guide, and atomic red team tests.

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections