CIS Microsoft Azure Foundations Benchmark v1.4.0/Other Security Considerations/102 of 115
8.5Ensure that Resource Locks are set for Mission Critical Azure Resources
Control family: Other Security Considerations
Control description
Resource Manager Locks provide a way for administrators to lock down Azure resources to prevent deletion of, or modifications to, a resource. These locks sit outside of the Role Based Access Controls (RBAC) hierarchy and, when applied, will place restrictions on the resource for all users. These locks are very useful when there is an important resource in a subscription that users should not be able to delete or change. Locks can help prevent accidental and malicious changes or deletion.
How to implement
ResponsibilityCustomerYou configure and operate this in your own cloud accounts.
A resource lock stops anyone, even an Owner, from deleting (or, with a read-only lock, changing) a resource until the lock is removed. On mission-critical resources such as production databases, key vaults and networks, it prevents one mistaken click or script from causing an outage.
Mostly process: the steps under "Before you start" are the work. The cloud tabs cover only where the cloud helps.
Before you start
The same on every cloud, before the steps in the tabs.
- List the mission-critical resources and their owners.
- Decide who may remove a lock (see 1.22) and how removal is approved.
Evidence
- The list of mission-critical resources
On Azure the tasks add locks to each mission-critical resource, then review the locks across the subscription.
Task 1Lock a mission-critical resource
- Sign in to the Azure portal at portal.azure.com and open the resource or its resource group.
- Select Settings > Locks, then + Add.
- Enter a Lock name, choose Lock type Delete (or Read-only where changes must be blocked too, knowing it can stop some operations), and add a note naming the owner.
- Select OK.
- Check it: trying to delete the resource is refused with a lock error.
Task 2Review the locks across the subscription
- Open Subscriptions, then the subscription, and select Settings > Resource locks.
- Compare the locks with the list of mission-critical resources.
- Add any missing lock, and ask about any lock removed since the last review.
Evidence
- The Locks page of each mission-critical resource
- The subscription's resource locks list, matching the critical resource list
Not applicable. This benchmark covers Azure only.
Not applicable. This benchmark covers Azure only.
Console steps as of 5 November 2026. Not every step has been confirmed in a live console yet, and menus and labels can move between releases, so look for the nearest match if one has changed.