Skip to main content

🛡️ Azure Subscription Microsoft Defender For Servers is not set to On🟢

  • Contextual name: 🛡️ Microsoft Defender For Servers is not set to On🟢
  • ID: /ce/ca/azure/subscription/microsoft-defender-for-servers
  • Tags:
  • Policy Type: COMPLIANCE_POLICY
  • Policy Categories: SECURITY

Logic​

Similar Policies​

Similar Internal Rules​

RulePoliciesFlags
✉️ dec-x-52ac4ac01

Description​

Open File

Description​

The Defender for Servers plan in Microsoft Defender for Cloud reduces security risk by providing actionable recommendations to improve and remediate machine security posture. Defender for Servers also helps to protect machines against real-time security threats and attacks.

Defender for Servers offers two paid plans:

Plan 1

The following components are enabled by default:

  • Log Analytics agent (deprecated)
  • Endpoint protection

Plan 1 also offers the following components, disabled by default:

  • Vulnerability assessment for machines
  • Guest Configuration agent (preview)

Plan 2

The following components are enabled by default:

  • Log Analytics agent (deprecated)
  • Vulnerability assessment for machines
  • Endpoint protection
  • Agentless scanning for machines

Plan 2 also offers the following components, disabled by default:

  • Guest Configuration agent (preview)
  • File Integrity Monitoring

Rationale​

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

... 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. Click Defender plans in the left pane.
  5. Under Cloud Workload Protection (CWP), locate Server in the Plan column, set Status to On.
  6. Select Save.
  7. Repeat steps 1-6 for each subscription requiring remediation.

From Azure CLI​

Run the following command:

az security pricing create \
    -n VirtualMachines \
    --tier Standard

From PowerShell​

Run the following command:

Set-AzSecurityPricing `
    -Name "VirtualMachines" `
    -PricingTier "Standard"

policy.yaml​

Open File

Linked Framework Sections​

SectionSub SectionsInternal RulesPoliciesFlagsCompliance
💼 APRA CPG 234 → 💼 16a vulnerability and threat management;1010no data
💼 APRA CPG 234 → 💼 16e security testing, including penetration testing;99no data
💼 APRA CPG 234 → 💼 36g vulnerability management controls — which identify and address information security vulnerabilities in a timely manner;1010no data
💼 APRA CPG 234 → 💼 36k response controls — to manage information security incidents and feedback mechanisms to address control deficiencies;99no data
💼 APRA CPG 234 → 💼 39a implement mechanisms that access and analyse timely threat intelligence regarding vulnerabilities, threats, methods of attack and countermeasures;1010no data
💼 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 access1010no data
💼 APRA CPG 234 → 💼 52e monitoring for unauthorised software and hardware (e.g. key loggers, password cracking software, wireless access points, business implemented technology solutions);99no data
💼 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.99no data
💼 APRA CPG 234 → 💼 67c sensors that provide an alert when a measure breaches a defined threshold(s) (e.g. device, server and network activity);99no data
💼 APRA CPG 234 → 💼 68 Monitoring processes and tools remain in step with the evolving nature of threats and contemporary industry practices.99no data
💼 APRA CPG 234 → 💼 73a detection of an information security event through the use of automated sensors and manual review;99no data
💼 APRA CPG 234 → 💼 73b identification and analysis to determine if it is an incident or an event;99no data
💼 APRA CPG 234 → 💼 73d containment to minimise the damage caused, and reduce the possibility of further damage;99no data
💼 APRA CPG 234 → 💼 73e eradication which involves the removal of the source of the information security compromise (typically malware);99no data
💼 CIS Azure v1.3.0 → 💼 2.1 Ensure that Azure Defender is set to On for Servers - Level 2 (Manual)11no data
💼 CIS Azure v1.4.0 → 💼 2.1 Ensure that Microsoft Defender for Servers is set to 'On' - Level 2 (Manual)11no data
💼 CIS Azure v1.5.0 → 💼 2.1.1 Ensure That Microsoft Defender for Servers Is Set to 'On' - Level 2 (Manual)11no data
💼 CIS Azure v2.0.0 → 💼 2.1.1 Ensure That Microsoft Defender for Servers Is Set to 'On' - Level 2 (Manual)11no data
💼 CIS Azure v2.1.0 → 💼 2.1.1 Ensure That Microsoft Defender for Servers Is Set to 'On' - Level 2 (Automated)11no data
💼 CIS Azure v3.0.0 → 💼 3.1.3.1 Ensure That Microsoft Defender for Servers Is Set to 'On' (Automated)1no data
💼 CIS Azure v4.0.0 → 💼 9.1.3.1 Ensure that Defender for Servers is set to 'On' (Automated)1no data
💼 CIS Azure v5.0.0 → 💼 8.1.3.1 Ensure that Defender for Servers is set to 'On' (Automated)1no data
💼 Cloudaware Framework → 💼 Microsoft Defender Configuration29no data
💼 FedRAMP High Security Controls → 💼 IR-6(1) Automated Reporting (M)(H)810no data
💼 FedRAMP High Security Controls → 💼 RA-3 Risk Assessment (L)(M)(H)177no data
💼 FedRAMP High Security Controls → 💼 RA-5 Vulnerability Monitoring and Scanning (L)(M)(H)678no data
💼 FedRAMP High Security Controls → 💼 SI-2 Flaw Remediation (L)(M)(H)2723no data
💼 FedRAMP High Security Controls → 💼 SI-3 Malicious Code Protection (L)(M)(H)77no data
💼 FedRAMP Low Security Controls → 💼 RA-3 Risk Assessment (L)(M)(H)17no data
💼 FedRAMP Low Security Controls → 💼 RA-5 Vulnerability Monitoring and Scanning (L)(M)(H)28no data
💼 FedRAMP Low Security Controls → 💼 SI-2 Flaw Remediation (L)(M)(H)23no data
💼 FedRAMP Low Security Controls → 💼 SI-3 Malicious Code Protection (L)(M)(H)7no data
💼 FedRAMP Moderate Security Controls → 💼 IR-6(1) Automated Reporting (M)(H)10no data
💼 FedRAMP Moderate Security Controls → 💼 RA-3 Risk Assessment (L)(M)(H)17no data
💼 FedRAMP Moderate Security Controls → 💼 RA-5 Vulnerability Monitoring and Scanning (L)(M)(H)48no data
💼 FedRAMP Moderate Security Controls → 💼 SI-2 Flaw Remediation (L)(M)(H)223no data
💼 FedRAMP Moderate Security Controls → 💼 SI-3 Malicious Code Protection (L)(M)(H)7no data
💼 ISO/IEC 27001:2013 → 💼 A.12.2.1 Controls against malware77no data
💼 ISO/IEC 27001:2013 → 💼 A.12.6.1 Management of technical vulnerabilities77no data
💼 ISO/IEC 27001:2022 → 💼 8.1 User end point devices813no data
💼 ISO/IEC 27001:2022 → 💼 8.7 Protection against malware11no data
💼 ISO/IEC 27001:2022 → 💼 8.8 Management of technical vulnerabilities810no data
💼 NIST CSF v1.1 → 💼 DE.AE-4: Impact of events is determined1314no data
💼 NIST CSF v1.1 → 💼 DE.CM-4: Malicious code is detected77no data
💼 NIST CSF v1.1 → 💼 DE.CM-8: Vulnerability scans are performed77no data
💼 NIST CSF v1.1 → 💼 DE.DP-3: Detection processes are tested1314no data
💼 NIST CSF v1.1 → 💼 DE.DP-4: Event detection information is communicated2933no data
💼 NIST CSF v1.1 → 💼 DE.DP-5: Detection processes are continuously improved1316no data
💼 NIST CSF v1.1 → 💼 ID.RA-1: Asset vulnerabilities are identified and documented1316no data
💼 NIST CSF v1.1 → 💼 ID.RA-3: Threats, both internal and external, are identified and documented77no data
💼 NIST CSF v1.1 → 💼 ID.RA-4: Potential business impacts and likelihoods are identified77no data
💼 NIST CSF v1.1 → 💼 ID.RA-5: Threats, vulnerabilities, likelihoods, and impacts are used to determine risk77no data
💼 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 process77no data
💼 NIST CSF v1.1 → 💼 PR.AT-1: All users are informed and trained77no data
💼 NIST CSF v1.1 → 💼 PR.DS-6: Integrity checking mechanisms are used to verify software, firmware, and information integrity2227no data
💼 NIST CSF v1.1 → 💼 PR.IP-12: A vulnerability management plan is developed and implemented79no data
💼 NIST CSF v1.1 → 💼 RS.CO-3: Information is shared consistent with response plans1618no data
💼 NIST CSF v1.1 → 💼 RS.MI-1: Incidents are contained77no data
💼 NIST CSF v1.1 → 💼 RS.MI-2: Incidents are mitigated77no data
💼 NIST CSF v1.1 → 💼 RS.MI-3: Newly identified vulnerabilities are mitigated or documented as accepted risks77no data
💼 NIST CSF v2.0 → 💼 DE.AE-04: The estimated impact and scope of adverse events are understood14no data
💼 NIST CSF v2.0 → 💼 DE.AE-06: Information on adverse events is provided to authorized staff and tools33no data
💼 NIST CSF v2.0 → 💼 DE.CM-01: Networks and network services are monitored to find potentially adverse events180no data
💼 NIST CSF v2.0 → 💼 DE.CM-09: Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events181no data
💼 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 considered7no data
💼 NIST CSF v2.0 → 💼 GV.SC-03: Cybersecurity supply chain risk management is integrated into cybersecurity and enterprise risk management, risk assessment, and improvement processes10no data
💼 NIST CSF v2.0 → 💼 GV.SC-04: Suppliers are known and prioritized by criticality7no data
💼 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 relationship26no data
💼 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 parties59no data
💼 NIST CSF v2.0 → 💼 ID.IM-03: Improvements are identified from execution of operational processes, procedures, and activities60no data
💼 NIST CSF v2.0 → 💼 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded46no data
💼 NIST CSF v2.0 → 💼 ID.RA-03: Internal and external threats to the organization are identified and recorded7no data
💼 NIST CSF v2.0 → 💼 ID.RA-04: Potential impacts and likelihoods of threats exploiting vulnerabilities are identified and recorded7no data
💼 NIST CSF v2.0 → 💼 ID.RA-05: Threats, vulnerabilities, likelihoods, and impacts are used to understand inherent risk and inform risk response prioritization7no data
💼 NIST CSF v2.0 → 💼 ID.RA-06: Risk responses are chosen, prioritized, planned, tracked, and communicated7no data
💼 NIST CSF v2.0 → 💼 ID.RA-10: Critical suppliers are assessed prior to acquisition26no data
💼 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 mind8no data
💼 NIST CSF v2.0 → 💼 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected187no data
💼 NIST CSF v2.0 → 💼 RS.CO-02: Internal and external stakeholders are notified of incidents31no data
💼 NIST CSF v2.0 → 💼 RS.CO-03: Information is shared with designated internal and external stakeholders19no data
💼 NIST CSF v2.0 → 💼 RS.MI-01: Incidents are contained7no data
💼 NIST CSF v2.0 → 💼 RS.MI-02: Incidents are eradicated7no data
💼 NIST SP 800-53 Revision 5 → 💼 SI-7(12) Software, Firmware, and Information Integrity _ Integrity Verification1921no data
💼 PCI DSS v3.2.1 → 💼 5.1 Deploy anti-virus software on all systems commonly affected by malicious software.244no data
💼 PCI DSS v3.2.1 → 💼 11.4 Use intrusion-detection and/or intrusion-prevention techniques to detect and/or prevent intrusions into the network.113no data
💼 PCI DSS v4.0.1 → 💼 5.2.1 An anti-malware solution(s) is deployed on all system components.4no data
💼 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.113no data
💼 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.13no data
💼 PCI DSS v4.0.1 → 💼 11.6.1 A change- and tamper-detection mechanism is deployed.13no data
💼 PCI DSS v4.0 → 💼 5.2.1 An anti-malware solution(s) is deployed on all system components.44no data
💼 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.1813no data
💼 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.813no data
💼 PCI DSS v4.0 → 💼 11.6.1 A change- and tamper-detection mechanism is deployed.13no data
💼 SOC 2 → 💼 CC7.2-3 Implements Filters to Analyze Anomalies918no data