Skip to main content

📝 Azure Subscription Microsoft Defender For Key Vault is not set to On 🟢

  • Contextual name: 📝 Microsoft Defender For Key Vault is not set to On 🟢
  • ID: /ce/ca/azure/subscription/microsoft-defender-for-key-vault
  • Located in: 📁 Azure Subscription

Flags​

Our Metadata​

  • Policy Type: COMPLIANCE_POLICY
  • Policy Category:
    • SECURITY

Similar Policies​

Similar Internal Rules​

RulePoliciesFlags
✉️ dec-x-1a2f62791

Logic​

Description​

Open File

Description​

Turning on Microsoft Defender for Key Vault enables threat detection for Key Vault, providing threat intelligence, anomaly detection, and behavior analytics in the Microsoft Defender for Cloud.

Rationale​

Enabling Microsoft Defender for Key Vault allows for greater defense-in-depth, with threat detection provided by the Microsoft Security Response Center (MSRC).

Impact​

Turning on Microsoft Defender for Key Vault incurs an additional cost per resource.

Audit​

This policy flags an Azure Subscription as INCOMPLIANT if the related Azure Defender Plan for Key Vaults has its Pricing Tier set to Free.

A Subscription is also marked as INCOMPLIANT if the Defender Plan for Key Vaults does not exist in the CMDB.

Default Value​

By default, Microsoft Defender plan is off.

References​

  1. https://docs.microsoft.com/en-us/azure/security-center/security-center-detection-capabilities
  2. https://docs.microsoft.com/en-us/rest/api/securitycenter/pricings/list
  3. https://docs.microsoft.com/en-us/rest/api/securitycenter/pricings/update

... see more

Remediation​

Open File

Remediation​

From Azure Portal​

  1. Go to Microsoft Defender for Cloud.
  2. Under Management, select Environment Settings.
  3. Click on the subscription name.
  4. Select the Defender plans blade.
  5. Select On under Status for Key Vault.
  6. Select Save.

From Azure CLI​

Enable Standard pricing tier for Key Vault:

az security pricing create -n 'KeyVaults' --tier 'Standard'
From PowerShell​

Enable Standard pricing tier for Key Vault:

Set-AzSecurityPricing -Name 'KeyVaults' -PricingTier 'Standard'

policy.yaml​

Open File

Linked Framework Sections​

SectionSub SectionsInternal RulesPoliciesFlags
💼 APRA CPG 234 → 💼 16a vulnerability and threat management;1010
💼 APRA CPG 234 → 💼 16e security testing, including penetration testing;99
💼 APRA CPG 234 → 💼 36g vulnerability management controls — which identify and address information security vulnerabilities in a timely manner;1010
💼 APRA CPG 234 → 💼 36k response controls — to manage information security incidents and feedback mechanisms to address control deficiencies;99
💼 APRA CPG 234 → 💼 39a implement mechanisms that access and analyse timely threat intelligence regarding vulnerabilities, threats, methods of attack and countermeasures;1010
💼 APRA CPG 234 → 💼 39d implement mechanisms to disrupt the various phases of an attack. Example phases include reconnaissance, vulnerability exploitation, malware installation, privilege escalation, and unauthorised access1010
💼 APRA CPG 234 → 💼 52e monitoring for unauthorised software and hardware (e.g. key loggers, password cracking software, wireless access points, business implemented technology solutions);99
💼 APRA CPG 234 → 💼 66 Under CPS 234, an APRA-regulated entity is required to have robust mechanisms in place to detect and respond to actual or potential compromises of information security in a timely manner. The term ‘potential’ is used to highlight that information security incidents are commonly identified when an event occurs (e.g. unauthorised access notification, customer complaint) requiring further investigation in order to ascertain whether an actual security compromise has occurred.99
💼 APRA CPG 234 → 💼 67c sensors that provide an alert when a measure breaches a defined threshold(s) (e.g. device, server and network activity);99
💼 APRA CPG 234 → 💼 68 Monitoring processes and tools remain in step with the evolving nature of threats and contemporary industry practices.99
💼 APRA CPG 234 → 💼 73a detection of an information security event through the use of automated sensors and manual review;99
💼 APRA CPG 234 → 💼 73b identification and analysis to determine if it is an incident or an event;99
💼 APRA CPG 234 → 💼 73d containment to minimise the damage caused, and reduce the possibility of further damage;99
💼 APRA CPG 234 → 💼 73e eradication which involves the removal of the source of the information security compromise (typically malware);99
💼 CIS Azure v1.3.0 → 💼 2.8 Ensure that Azure Defender is set to On for Key Vault - Level 2 (Manual)11
💼 CIS Azure v1.4.0 → 💼 2.8 Ensure that Microsoft Defender for Key Vault is set to 'On' - Level 2 (Manual)11
💼 CIS Azure v1.5.0 → 💼 2.1.10 Ensure That Microsoft Defender for Key Vault Is Set To 'On' - Level 2 (Manual)11
💼 CIS Azure v2.0.0 → 💼 2.1.10 Ensure That Microsoft Defender for Key Vault Is Set To 'On' - Level 2 (Manual)11
💼 CIS Azure v2.1.0 → 💼 2.1.9 Ensure That Microsoft Defender for Key Vault Is Set To 'On' - Level 2 (Automated)11
💼 CIS Azure v3.0.0 → 💼 3.1.8.1 Ensure That Microsoft Defender for Key Vault Is Set To 'On' (Automated)1
💼 CIS Azure v4.0.0 → 💼 9.1.8.1 Ensure That Microsoft Defender for Key Vault Is Set To 'On' (Automated)1
💼 Cloudaware Framework → 💼 Microsoft Defender Configuration26
💼 FedRAMP High Security Controls → 💼 IR-6(1) Automated Reporting (M)(H)810
💼 FedRAMP High Security Controls → 💼 RA-3 Risk Assessment (L)(M)(H)177
💼 FedRAMP High Security Controls → 💼 RA-5 Vulnerability Monitoring and Scanning (L)(M)(H)677
💼 FedRAMP High Security Controls → 💼 SI-2 Flaw Remediation (L)(M)(H)2710
💼 FedRAMP High Security Controls → 💼 SI-3 Malicious Code Protection (L)(M)(H)77
💼 FedRAMP Low Security Controls → 💼 RA-3 Risk Assessment (L)(M)(H)17
💼 FedRAMP Low Security Controls → 💼 RA-5 Vulnerability Monitoring and Scanning (L)(M)(H)27
💼 FedRAMP Low Security Controls → 💼 SI-2 Flaw Remediation (L)(M)(H)10
💼 FedRAMP Low Security Controls → 💼 SI-3 Malicious Code Protection (L)(M)(H)7
💼 FedRAMP Moderate Security Controls → 💼 IR-6(1) Automated Reporting (M)(H)10
💼 FedRAMP Moderate Security Controls → 💼 RA-3 Risk Assessment (L)(M)(H)17
💼 FedRAMP Moderate Security Controls → 💼 RA-5 Vulnerability Monitoring and Scanning (L)(M)(H)47
💼 FedRAMP Moderate Security Controls → 💼 SI-2 Flaw Remediation (L)(M)(H)210
💼 FedRAMP Moderate Security Controls → 💼 SI-3 Malicious Code Protection (L)(M)(H)7
💼 ISO/IEC 27001:2013 → 💼 A.12.2.1 Controls against malware77
💼 ISO/IEC 27001:2013 → 💼 A.12.6.1 Management of technical vulnerabilities77
💼 ISO/IEC 27001:2022 → 💼 8.8 Management of technical vulnerabilities810
💼 NIST CSF v1.1 → 💼 DE.AE-4: Impact of events is determined1313
💼 NIST CSF v1.1 → 💼 DE.CM-4: Malicious code is detected77
💼 NIST CSF v1.1 → 💼 DE.CM-8: Vulnerability scans are performed77
💼 NIST CSF v1.1 → 💼 DE.DP-3: Detection processes are tested1313
💼 NIST CSF v1.1 → 💼 DE.DP-4: Event detection information is communicated2932
💼 NIST CSF v1.1 → 💼 DE.DP-5: Detection processes are continuously improved1315
💼 NIST CSF v1.1 → 💼 ID.RA-1: Asset vulnerabilities are identified and documented1315
💼 NIST CSF v1.1 → 💼 ID.RA-3: Threats, both internal and external, are identified and documented77
💼 NIST CSF v1.1 → 💼 ID.RA-4: Potential business impacts and likelihoods are identified77
💼 NIST CSF v1.1 → 💼 ID.RA-5: Threats, vulnerabilities, likelihoods, and impacts are used to determine risk77
💼 NIST CSF v1.1 → 💼 ID.SC-2: Suppliers and third party partners of information systems, components, and services are identified, prioritized, and assessed using a cyber supply chain risk assessment process77
💼 NIST CSF v1.1 → 💼 PR.AT-1: All users are informed and trained77
💼 NIST CSF v1.1 → 💼 PR.DS-6: Integrity checking mechanisms are used to verify software, firmware, and information integrity2226
💼 NIST CSF v1.1 → 💼 PR.IP-12: A vulnerability management plan is developed and implemented79
💼 NIST CSF v1.1 → 💼 RS.CO-3: Information is shared consistent with response plans1617
💼 NIST CSF v1.1 → 💼 RS.MI-1: Incidents are contained77
💼 NIST CSF v1.1 → 💼 RS.MI-2: Incidents are mitigated77
💼 NIST CSF v1.1 → 💼 RS.MI-3: Newly identified vulnerabilities are mitigated or documented as accepted risks77
💼 NIST CSF v2.0 → 💼 DE.AE-04: The estimated impact and scope of adverse events are understood13
💼 NIST CSF v2.0 → 💼 DE.AE-06: Information on adverse events is provided to authorized staff and tools32
💼 NIST CSF v2.0 → 💼 DE.CM-01: Networks and network services are monitored to find potentially adverse events115
💼 NIST CSF v2.0 → 💼 DE.CM-09: Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events134
💼 NIST CSF v2.0 → 💼 GV.OC-02: Internal and external stakeholders are understood, and their needs and expectations regarding cybersecurity risk management are understood and considered7
💼 NIST CSF v2.0 → 💼 GV.SC-03: Cybersecurity supply chain risk management is integrated into cybersecurity and enterprise risk management, risk assessment, and improvement processes10
💼 NIST CSF v2.0 → 💼 GV.SC-04: Suppliers are known and prioritized by criticality7
💼 NIST CSF v2.0 → 💼 GV.SC-07: The risks posed by a supplier, their products and services, and other third parties are understood, recorded, prioritized, assessed, responded to, and monitored over the course of the relationship26
💼 NIST CSF v2.0 → 💼 ID.IM-02: Improvements are identified from security tests and exercises, including those done in coordination with suppliers and relevant third parties33
💼 NIST CSF v2.0 → 💼 ID.IM-03: Improvements are identified from execution of operational processes, procedures, and activities34
💼 NIST CSF v2.0 → 💼 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded26
💼 NIST CSF v2.0 → 💼 ID.RA-03: Internal and external threats to the organization are identified and recorded7
💼 NIST CSF v2.0 → 💼 ID.RA-04: Potential impacts and likelihoods of threats exploiting vulnerabilities are identified and recorded7
💼 NIST CSF v2.0 → 💼 ID.RA-05: Threats, vulnerabilities, likelihoods, and impacts are used to understand inherent risk and inform risk response prioritization7
💼 NIST CSF v2.0 → 💼 ID.RA-06: Risk responses are chosen, prioritized, planned, tracked, and communicated7
💼 NIST CSF v2.0 → 💼 ID.RA-10: Critical suppliers are assessed prior to acquisition26
💼 NIST CSF v2.0 → 💼 PR.AT-01: Personnel are provided with awareness and training so that they possess the knowledge and skills to perform general tasks with cybersecurity risks in mind8
💼 NIST CSF v2.0 → 💼 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected114
💼 NIST CSF v2.0 → 💼 RS.CO-02: Internal and external stakeholders are notified of incidents30
💼 NIST CSF v2.0 → 💼 RS.CO-03: Information is shared with designated internal and external stakeholders18
💼 NIST CSF v2.0 → 💼 RS.MI-01: Incidents are contained7
💼 NIST CSF v2.0 → 💼 RS.MI-02: Incidents are eradicated7
💼 NIST SP 800-53 Revision 5 → 💼 SI-7(12) Software, Firmware, and Information Integrity _ Integrity Verification1921
💼 PCI DSS v3.2.1 → 💼 11.4 Use intrusion-detection and/or intrusion-prevention techniques to detect and/or prevent intrusions into the network.18
💼 PCI DSS v4.0.1 → 💼 11.5.1 Intrusion-detection and/or intrusion-prevention techniques are used to detect and/or prevent intrusions into the network.18
💼 PCI DSS v4.0.1 → 💼 11.5.1.1 Intrusion-detection and/or intrusion-prevention techniques detect, alert on/prevent, and address covert malware communication channels.8
💼 PCI DSS v4.0.1 → 💼 11.6.1 A change- and tamper-detection mechanism is deployed.8
💼 PCI DSS v4.0 → 💼 11.5.1 Intrusion-detection and/or intrusion-prevention techniques are used to detect and/or prevent intrusions into the network.188
💼 PCI DSS v4.0 → 💼 11.5.1.1 Intrusion-detection and/or intrusion-prevention techniques detect, alert on/prevent, and address covert malware communication channels.88
💼 PCI DSS v4.0 → 💼 11.6.1 A change- and tamper-detection mechanism is deployed.8
💼 SOC 2 → 💼 CC7.2-3 Implements Filters to Analyze Anomalies918