Skip to main content

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

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

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. 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-v3.0.0/10/01
    • /frameworks/cis-azure-v4.0.0/07/02

Similar Sections (Take Policies From)

SectionSub SectionsInternal RulesPoliciesFlagsCompliance
💼 CIS Azure v3.0.0 → 💼 10.1 Ensure that Resource Locks are set for Mission-Critical Azure Resources (Manual)no data
💼 CIS Azure v4.0.0 → 💼 7.2 Ensure that Resource Locks are set for Mission-Critical Azure Resources (Manual)no data

Sub Sections

SectionSub SectionsInternal RulesPoliciesFlagsCompliance

Policies (1)

PolicyLogic CountFlagsCompliance
🛡️ Azure Resource Lock is not enabled for mission-critical resources🟢⚪🟢 x2, ⚪ x1no data