💼 6.2 Ensure that Resource Locks are set for Mission-Critical Azure Resources (Manual)

• ID: /frameworks/cis-azure-v7.0.0/06/02

Stats

not available

Description

Resource Manager locks restrict deletion or modification of a subscription, resource group, or resource for all users, regardless of their role assignments. A CanNotDelete lock lets authorized users read and modify a resource but not delete it; a ReadOnly lock lets them read it but not modify or delete it, similar to the Reader role. While an automated assessment procedure exists for this recommendation, the assessment status remains manual. Determining resources that require resource locks depends on the context and requirements of each organization and environment.

Similar

• Sections
  • /frameworks/cis-azure-v6.0.0/06/02

Similar Sections (Take Policies From)

Section	Sub Sections	Internal Rules	Policies	Flags	Compliance
💼 CIS Azure v6.0.0 → 💼 6.2 Ensure that Resource Locks are set for Mission-Critical Azure Resources (Manual)			1		no data

Similar Sections (Give Policies To)

Section	Sub Sections	Internal Rules	Policies	Flags	Compliance
💼 CIS Azure v6.0.0 → 💼 6.2 Ensure that Resource Locks are set for Mission-Critical Azure Resources (Manual)			1		no data

Sub Sections

Section	Sub Sections	Internal Rules	Policies	Flags	Compliance

Policies (1)

Policy	Logic Count	Flags	Compliance
🛡️ Azure Resource Lock is not enabled for mission-critical resources🟢⚪		🟢 x2, ⚪ x1	no data