Microsoft AzureOverview
Turning on Microsoft Defender for SQL Servers on machines enables threat detection for SQL Servers on machines, providing threat intelligence, anomaly detection, and behavior analytics in the Microsoft Defender for Cloud.
Rationale
Enabling Microsoft Defender for SQL Servers on machines allows for greater defense-in-depth, with threat detection provided by the Microsoft Security Response Center (MSRC).
Impact
Turning on Microsoft Defender for SQL Servers on machines incurs an additional cost per resource.
Remediation guidance
From Azure Console
- Open Microsoft Defender for Cloud | Environment settings
- Select a subscription
- Under
Settings, selectDefender plans - Under
Databases, expandSelect types > - For
SQL servers on machines, selectOn - Select Save
Using Azure Command Line Interface
az security pricing create -n 'SqlServerVirtualMachines' --tier 'Standard'
Using Azure PowerShell
Set-AzSecurityPricing -Name 'SqlServerVirtualMachines' -PricingTier 'Standard'
Default Value
By default, the Microsoft Defender plan is off.
References
- https://learn.microsoft.com/en-us/azure/security-center/security-center-detection-capabilities
- https://learn.microsoft.com/en-us/rest/api/securitycenter/pricings/list
- https://learn.microsoft.com/en-us/rest/api/securitycenter/pricings/update
- https://learn.microsoft.com/en-us/powershell/module/az.security/get-azsecuritypricing
- https://learn.microsoft.com/en-us/security/benchmark/azure/security-controls-v3-data-protection#dp-3-monitor-for-unauthorized-transfer-of-sensitive-data
- https://learn.microsoft.com/en-us/security/benchmark/azure/security-controls-v3-logging-threat-detection#lt-1-enable-threat-detection-capabilities
Service-wide remediation
Recommended when many resources are affected: fix the platform baseline first so new resources inherit the secure setting, then remediate the existing flagged resources in batches.
Azure
Use management group or subscription Azure Policy assignments, remediation tasks where supported, landing-zone standards, and IaC modules so drift is prevented at scale.
Operational rollout
- Fix the baseline first at the account, subscription, project, cluster, or tenant scope that owns this control.
- Remediate the currently affected resources in batches, starting with internet-exposed and production assets.
- Re-scan and track approved exceptions with an owner and expiry date.
Query logic
These are the stored checks tied to this control.
Azure Subscriptions without Microsoft Defender for SQL Servers on Machines
Connectors
Covered asset types
Expected check: eq []
{
connectors(
where: {
pricing_SOME: { name: "SqlServerVirtualMachines", pricingTier: "Free" }
}
) {
...AssetFragment
}
}
