1200kmSECURITY RESEARCH

1200KM / sigma-rule

User Added To Privilege Role — Sigma Rule

Sigma rule 49a268a4-72f4-4e38-8a7b-885be690c5b5. User Added To Privilege Role — Sigma Rule. Detects when a user is added to a privileged role.

Rule metadata and linked tags

Author: Mark Morowczynski '@markmorow', Yochana Henderson, '@Yochana-H'. Source status: test; severity: high. Source dates: 2022-08-06 / not supplied.

{
  "product": "azure",
  "service": "auditlogs"
}

Pinned original Sigma rule · Detection Rule License 1.1

Source SHA-256: d78d3380195de2f36ae8fd4d0a9807fde76ea5b2084f23a30481596b1fc77978

Detection logic

Original source YAML. Source-tag agreement is not proof of complete semantic coverage. This rule has not been compiled for a SIEM backend or validated against live telemetry here.

title: User Added To Privilege Role
id: 49a268a4-72f4-4e38-8a7b-885be690c5b5
status: test
description: Detects when a user is added to a privileged role.
references:
    - https://learn.microsoft.com/en-us/entra/architecture/security-operations-privileged-identity-management#azure-ad-roles-assignment
author: Mark Morowczynski '@markmorow', Yochana Henderson, '@Yochana-H'
date: 2022-08-06
tags:
    - attack.persistence
    - attack.initial-access
    - attack.privilege-escalation
    - attack.stealth
    - attack.t1078.004
logsource:
    product: azure
    service: auditlogs
detection:
    selection:
        properties.message:
            - Add eligible member (permanent)
            - Add eligible member (eligible)
    condition: selection
falsepositives:
    - Legtimate administrator actions of adding members from a role
level: high

Original YAML and metadata in JSON

False positives

  • Legtimate administrator actions of adding members from a role

Source references

Connected ecosystem references

Exact source-tagged techniques

Telemetry review

Read the original logsource above, then inspect the linked detection workspaces for technique-level sensor context. No per-rule telemetry equivalence is inferred.

Pinned research references. No browser attack runner, live simulation result or validated detector is asserted. Source mappings and validation limits are preserved. ATT&CK / Atomic provenance · Detection provenance.