-
Notifications
You must be signed in to change notification settings - Fork 570
[New Rule] Azure Subscription Permission Elevation #1630
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This has been closed due to inactivity. If you feel this is an error, please re-open and include a justifying comment. |
👋🏽 Hey @austinsonger. Thanks for opening this request. After further review and reading a recent Permiso blog, I agree this is a decent signal of privilege escalation into Azure resources if a global admin in Entra ID is compromised. As a result, I've opened a new PR and linked it to this issue. As you are aware, global admins in Entra ID do not always transfer RBAC to Azure subscriptions that may exist as they are intentionally separated. However, a global admin can elevate their privileges to control subscriptions via a simple toggle in Entra ID. While I did not find a great example of this in-the-wild via OSINT - Permiso has a decent blog covering this from red-team perspective - https://permiso.io/blog/azures-apex-permissions-elevate-access-the-logs-security-teams-overlook As a side note, when I replicated this and reviewed telemetry, I noticed this was only logged for us in Entra ID audit logs where the query was
We will keep the query to Entra ID audit logs only for now to allow the opportunity for tuning if necessary on a single data source. |
Uh oh!
There was an error while loading. Please reload this page.
Description
Identifies when a user has been elevated to manage all Azure Subscriptions. This setting could allow an attacker access to Azure subscriptions in your environment.
Required Info
Target indexes
filebeat-*, logs-azure*
Platforms
Azure
Optional Info
Query
New fields required in ECS/data sources for this rule?
Related issues or PRs
False Positives
MITRE
References
The text was updated successfully, but these errors were encountered: