Detections
Analytics
1.24 Ensure a Custom Role is Assigned Permissions for Administering Resource Locks
Warning! Audit Deprecated
This audit has been deprecated and will be removed in a future update.
View Next Audit VersionInformation
Resource locking is a powerful protection mechanism that can prevent inadvertent modification/deletion of resources within Azure subscriptions/Resource Groups and is a recommended NIST configuration.Rationale:
Given the resource lock functionality is outside of standard Role Based Access Control(RBAC), it would be prudent to create a resource lock administrator role to prevent inadvertent unlocking of resources.
Impact:
By adding this role, specific permissions may be granted for managing just resource locks rather than needing to provide the wide Owner or User Access Administrator role, reducing the risk of the user being able to do unintentional damage.
NOTE: Nessus has not performed this check. Please review the benchmark to ensure target compliance.
Solution
From Azure PortalIn the Azure portal, open a subscription or resource group where you want the custom role to be assigned.
Select Access control (IAM).
Click Add.
Select Add custom role.
In the Custom Role Name field enter Resource Lock Administrator.
In the Description field enter Can Administer Resource Locks.
For Baseline permissions select Start from scratch
Select next.
In the Permissions tab select Add permissions.
In the Search for a permission box, type in Microsoft.Authorization/locks to search for permissions.
Select the check box next to the permission Microsoft.Authorization/locks.
Select Add.
Select Review + create.
Select Create.
Assign the newly created role to the appropriate user.
From PowerShell:
Below is a power shell definition for a resource lock administrator role created at an Azure Management group level
Import-Module Az.Accounts
Connect-AzAccount
$role = Get-AzRoleDefinition 'User Access Administrator'
$role.Id = $null
$role.Name = 'Resource Lock Administrator'
$role.Description = 'Can Administer Resource Locks'
$role.Actions.Clear()
$role.Actions.Add('Microsoft.Authorization/locks/*')
$role.AssignableScopes.Clear()
* Scope at the Management group level Management group
$role.AssignableScopes.Add('/providers/Microsoft.Management/managementGroups/MG-Name')
New-AzRoleDefinition -Role $role
Get-AzureRmRoleDefinition 'Resource Lock Administrator'
See Also
Item Details
Audit Name: CIS Microsoft Azure Foundations v2.0.0 L2
References: CSCv7|14.6
Plugin: microsoft_azure
Control ID: e358cdc87d4c9c40004363390cf7d8607889bbbb2d6e17532341c42d96fb6a91