🛡️ Azure Subscription Resource Lock Administrator Custom Role does not exist🟢⚪

• Contextual name: 🛡️ Resource Lock Administrator Custom Role does not exist🟢⚪
• ID: /ce/ca/azure/subscription/resource-lock-administrator-custom-role
• Tags:
  • ⚪ Impossible policy
  • 🟢 Policy with categories
  • 🟢 Policy with type
• Policy Type: COMPLIANCE_POLICY
• Policy Categories: SECURITY

Similar Policies

• Cloud Conformity: Resource Locking Administrator Role

Description

Open File

Description

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),s 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.

Audit

From Azure Portal

1. In the Azure portal, open a subscription or resource group where you want to view assigned roles.
2. Select Access control (IAM).
3. Select Roles.
4. Search for the custom role named "role_name" e.g. from remediation Resource Lock Administrator.
5. Ensure that the role is assigned to the appropriate users.

References

... see more

Remediation

Open File

Remediation

From Azure Portal

1. In the Azure portal, open a subscription or resource group where you want the custom role to be assigned.
2. Select Access control (IAM).
3. Click Add.
4. Select Add custom role.
5. In the Custom Role Name field enter Resource Lock Administrator.
6. In the Description field enter Can Administer Resource Locks.
7. For Baseline permissions select Start from scratch
8. Select Next.
9. In the Permissions tab select Add permissions.
10. In the Search for a permission box, type in Microsoft.Authorization/locks to search for permissions.
11. Click on the result.
12. Check the box next to Permission.
13. Select Add.
14. Select Review + create.
15. Select Create.
16. 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 more](remediation.md)

policy.yaml

Open File

Linked Framework Sections

Section	Sub Sections	Internal Rules	Policies	Flags	Compliance
💼 CIS Azure v2.1.0 → 💼 1.23 Ensure a Custom Role is Assigned Permissions for Administering Resource Locks - Level 2 (Manual)			1		no data
💼 CIS Azure v3.0.0 → 💼 2.24 Ensure a Custom Role is Assigned Permissions for Administering Resource Locks (Manual)			1		no data
💼 CIS Azure v4.0.0 → 💼 6.24 Ensure that a custom role is assigned permissions for administering resource locks (Manual)			1		no data
💼 Cloudaware Framework → 💼 Role-Based Access Control (RBAC) Management			14		no data