Microsoft AzureOverview
The principle of least privilege should be followed, and only necessary privileges should be assigned instead of allowing full administrative access.
Rationale
Classic subscription admin roles offer basic access management and include Account Administrator, Service Administrator, and Co-Administrators. It is recommended the least necessary permissions be given initially. Permissions can be added as needed by the account holder. This ensures the account holder cannot perform actions that were not intended.
Impact
Subscriptions will need to be handled by Administrators with permission.
Default Value
By default, no custom owner roles are created.
Remediation guidance
From Azure Portal
- Open the subscription using the
Open in Azureoption and go toAccess control (IAM). - Select
Roles. - Click
Typeand selectCustomRolefrom the drop-down menu. - Check the box next to each role that grants subscription administrator privileges.
- Select
Remove. - Select
Yes.
From Azure CLI
List custom roles:
az role definition list --custom-role-only True
Check for entries with assignableScope of / or the subscription and action of *. To remove a violating role:
az role definition delete --name <role_name>
Note that any role assignments must be removed before a custom role can be deleted. Ensure impact is assessed before deleting a custom role granting subscription administrator privileges.
Service-wide remediation
Recommended when many resources are affected: fix the platform baseline first so new resources inherit the secure setting, then remediate the existing flagged resources in batches.
Azure
Use management group or subscription Azure Policy assignments, remediation tasks where supported, landing-zone standards, and IaC modules so drift is prevented at scale.
Operational rollout
- Fix the baseline first at the account, subscription, project, cluster, or tenant scope that owns this control.
- Remediate the currently affected resources in batches, starting with internet-exposed and production assets.
- Re-scan and track approved exceptions with an owner and expiry date.
Query logic
These are the stored checks tied to this control.
Azure Custom Subscription Administrator Roles
Connectors
Covered asset types
Expected check: eq []
query ($subscriptionResourceId: String!) {
iamRoles(
where: {
type: "CustomRole"
permissions_INCLUDES: "*"
assignableScopes_INCLUDES: $subscriptionResourceId
}
) {
...AssetFragment
}
}
