Detections
Analytics
2.23 Ensure That No Custom Subscription Administrator Roles Exist
Warning! Audit Deprecated
This audit has been deprecated and will be removed in a future update.
View Next Audit VersionInformation
The principle of least privilege should be followed and only necessary privileges should be assigned instead of allowing full administrative access.Rationale:
Custom roles in Azure with administrative access can obfuscate the permissions granted and introduce complexity and blind spots to the management of privileged identities. For less mature security programs without regular identity audits, the creation of Custom roles should be avoided entirely. For more mature security programs with regular identity audits, Custom Roles should be audited for use and assignment, used minimally, and the principle of least privilege should be observed when granting permissions
Impact:
Subscriptions will need to be handled by Administrators with permissions.
Solution
Remediate from Azure PortalFrom Azure Home select the Portal Menu.
Select Subscriptions.
Select a subscription.
Select Access control (IAM).
Select Roles.
Click Type and select Custom role from the drop-down menu.
Check the box next to each role which grants subscription administrator privileges.
Select Delete.
Select Yes.
Remediate from Azure CLI
List custom roles:
az role definition list --custom-role-only True
Check for entries with assignableScope of the subscription, and an 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.
Default Value:
By default, no custom owner roles are created.
See Also
Item Details
Audit Name: CIS Microsoft Azure Foundations v3.0.0 L1
References: CSCv7|4.1
Plugin: microsoft_azure
Control ID: 8af611fbaaaf9ce91e092bfa99fa1057d13dc83ca6f1b6d093473dd68df8da9d