1200KM / sigma-rule
Roles Activated Too Frequently — Sigma Rule
Sigma rule 645fd80d-6c07-435b-9e06-7bc1b5656cba. Roles Activated Too Frequently — Sigma Rule. Identifies when the same privilege role has multiple activations by the same user.
Rule metadata and linked tags
Author: Mark Morowczynski '@markmorow', Gloria Lee, '@gleeiamglo'. Source status: test; severity: high. Source dates: 2023-09-14 / not supplied.
{
"product": "azure",
"service": "pim"
}Pinned original Sigma rule · Detection Rule License 1.1
Source SHA-256: eef78dd6024d83728dc464c492bcb1ed624d2ccfa50bb87ee7f853805e106de6
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: Roles Activated Too Frequently
id: 645fd80d-6c07-435b-9e06-7bc1b5656cba
status: test
description: Identifies when the same privilege role has multiple activations by the same user.
references:
- https://learn.microsoft.com/en-us/entra/id-governance/privileged-identity-management/pim-how-to-configure-security-alerts#roles-are-being-activated-too-frequently
author: Mark Morowczynski '@markmorow', Gloria Lee, '@gleeiamglo'
date: 2023-09-14
tags:
- attack.initial-access
- attack.stealth
- attack.t1078
- attack.persistence
- attack.privilege-escalation
logsource:
product: azure
service: pim
detection:
selection:
riskEventType: 'sequentialActivationRenewalsAlertIncident'
condition: selection
falsepositives:
- Investigate where if active time period for a role is set too short.
level: high
False positives
- Investigate where if active time period for a role is set too short.
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.