Skip to content
StrikeOps

OAuth Applications Granted High-Risk Permissions

HighTypical severity Cloud and Microsoft 365CWE-250ATT&CK T1528

01Description

A review of enterprise applications found service principals holding high-risk Microsoft Graph permissions, including application permissions that apply to every user in the tenant, such as Mail.ReadWrite, Files.ReadWrite.All, Directory.ReadWrite.All or RoleManagement.ReadWrite.Directory. Several had no identified business owner, or had not signed in for an extended period.

02Impact

Application permissions do not depend on a signed-in user or MFA. Anyone who obtains the credentials of such an application, or compromises the vendor behind it, can read every mailbox, download every file or, with directory or role management permissions, grant themselves Global Administrator. Consent phishing campaigns and supply chain compromises target exactly these grants.

03Severity

Typically

High

Typically High. High where unknown, unused or poorly governed applications hold tenant-wide permissions such as reading all mail or writing to the directory. Medium where the permissions are broad but the applications are known, current and owned.

04How to verify

  1. 1In the Entra admin center, open Identity > Applications > Enterprise applications, select each application and review Permissions for admin-consented and user-consented grants.
  2. 2Enumerate grants with Microsoft Graph PowerShell: Get-MgOauth2PermissionGrant for delegated permissions and Get-MgServicePrincipalAppRoleAssignment for application permissions.
  3. 3Compare high-risk grants against sign-in activity (Service principal sign-ins in the sign-in logs) and the organization's list of approved applications.

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. 1Remove permissions, or the whole application, where there is no current business need or identifiable owner.
  2. 2Reduce remaining applications to least privilege, for example using Sites.Selected or application access policies in Exchange Online to scope mailbox access.
  3. 3Assign an accountable owner to every application with application permissions and review grants on a set schedule.
  4. 4Restrict user consent and enable the admin consent workflow so new high-risk grants require review.
  5. 5Where licensed, use Microsoft Defender for Cloud Apps app governance to alert on overprivileged and unusual application activity.

06References

Draft findings like this from your own evidence

Book a demo
Book a demo