Detections
Analytics
1.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:
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 which were not intended.
Impact:
Subscriptions will need to be handled by Administrators with permissions.
NOTE: Nessus has not performed this check. Please review the benchmark to ensure target compliance.
Solution
From Azure PortalFrom Azure Home select the Portal Menu.
Select Subscriptions.
Select Access control (IAM).
Select Roles.
Click Type and select CustomRole from the drop down menu.
Check the box next to each role which 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 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 v2.0.0 L1
References: CSCv7|4.1
Plugin: microsoft_azure
Control ID: 51a656f3feb0840c51395f062f1153e0531d5065e3c30409ccb23f1ac61a2356