Microsoft AzureOverview
Microsoft Defender for Azure Cosmos DB scans all incoming network requests for threats to your Azure Cosmos DB resources.
Rationale
In scanning Azure Cosmos DB requests within a subscription, requests are compared to a heuristic list of potential security threats. These threats could be a result of a security breach within your services, thus scanning for them could prevent a potential security threat from being introduced.
Impact
Enabling Microsoft Defender for Azure Cosmos DB requires enabling Microsoft Defender for your subscription. Both will incur additional charges.
Remediation guidance
From Azure Console
- Open Microsoft Defender for Cloud | Environment settings
- Select a subscription
- Under
Settings, selectDefender plans - For
Azure Cosmos DB, selectOnforStatus - Select Save
Using Azure Command Line Interface
az security pricing create -n 'CosmosDbs' --tier 'Standard'
Using Azure PowerShell
Set-AzSecurityPricing -Name 'CosmosDbs' -PricingTier 'Standard'
Default Value
By default, the Microsoft Defender plan is off.
References
- https://azure.microsoft.com/en-us/pricing/details/defender-for-cloud/
- https://learn.microsoft.com/en-us/azure/defender-for-cloud/enable-enhanced-security
- https://learn.microsoft.com/en-us/azure/defender-for-cloud/alerts-overview
- https://learn.microsoft.com/en-us/security/benchmark/azure/baselines/cosmos-db-security-baseline
- https://learn.microsoft.com/en-us/azure/defender-for-cloud/quickstart-enable-database-protections
- 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 Cosmos DB
Connectors
Covered asset types
Expected check: eq []
{
connectors(
where: { pricing_SOME: { name: "CosmosDbs", pricingTier: "Free" } }
) {
...AssetFragment
}
}
