Skip to main content

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

  • Contextual name: 💼 10.1 Ensure that Resource Locks are set for Mission-Critical Azure Resources - Level 2 (Manual)
  • ID: /frameworks/cis-azure-v2.1.0/10/01
  • Located in: 💼 10.0 Miscellaneous

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.

Similar​

  • Sections
    • /frameworks/cis-azure-v3.0.0/10/01
  • Internal
    • ID: dec-c-be76d3c2

Similar Sections (Take Policies From)​

SectionSub SectionsInternal RulesPoliciesFlags
💼 CIS Azure v3.0.0 → 💼 10.1 Ensure that Resource Locks are set for Mission-Critical Azure Resources (Manual)1

Similar Sections (Give Policies To)​

SectionSub SectionsInternal RulesPoliciesFlags
💼 CIS Azure v3.0.0 → 💼 10.1 Ensure that Resource Locks are set for Mission-Critical Azure Resources (Manual)1

Sub Sections​

SectionSub SectionsInternal RulesPoliciesFlags

Policies (1)​

PolicyLogic CountFlags
📝 Azure Resource Lock is not enabled for mission-critical resources 🟢🟢 x3