Skip to content
StrikeOps

Privileged Roles Permanently Assigned (PIM Not Used)

MediumTypical severity Cloud and Microsoft 365CWE-250

01Description

Privileged Entra ID roles, such as Global Administrator, Exchange Administrator and Privileged Role Administrator, were assigned to accounts as permanent active assignments. Privileged Identity Management (PIM) was either not in use or was configured with active rather than eligible assignments.

02Impact

Every account with a standing privileged role is a full-privilege target at all times. If any of those accounts is phished or its session token stolen, the attacker immediately holds administrative control of the tenant, with no activation step, approval or justification to slow them down or raise an alert.

03Severity

Typically

Medium

Typically Medium. Medium by default where the tenant is licensed for Privileged Identity Management but roles are permanently active. Raise to High where many accounts hold Global Administrator or Privileged Role Administrator permanently. Report as an improvement where the tenant lacks Entra ID P2.

04How to verify

  1. 1In the Entra admin center, open Identity governance > Privileged Identity Management > Microsoft Entra roles > Assignments and compare Eligible and Active assignments for privileged roles.
  2. 2Use Microsoft Graph PowerShell to list standing assignments (Get-MgRoleManagementDirectoryRoleAssignment) and eligible assignments (Get-MgRoleManagementDirectoryRoleEligibilitySchedule).
  3. 3Review role settings for activation requirements such as MFA, justification, approval and maximum activation duration.

Testing note: only test systems you are authorized to test, within the agreed scope and rules of engagement. Verification steps are written for professional testers and avoid destructive techniques.

05Remediation

  1. 1Convert standing privileged role assignments to eligible assignments in PIM, keeping only the emergency access accounts as permanent Global Administrators. PIM requires Entra ID P2 or Microsoft Entra ID Governance.
  2. 2Configure role settings to require MFA (or an authentication context requiring phishing-resistant MFA), a justification, and approval for the most sensitive roles, with a short activation window.
  3. 3Enable PIM notifications so role activations are reported to the security team.
  4. 4Schedule access reviews of privileged roles at least quarterly.

06References

Draft findings like this from your own evidence

Book a demo
Book a demo