Skip to content

Commit 66d940d

Browse files
prmerger-automator[bot]prmerger-automator[bot]
authored
Merge pull request #274314 from ElazarK/WI231303-231305
moved upcoming notes to release notes
2 parents fcdb565 + bda10ce commit 66d940d

File tree

3 files changed

+86
-92
lines changed

3 files changed

+86
-92
lines changed

‎articles/defender-for-cloud/release-notes-archive.md

Lines changed: 28 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: A description of what's new and changed in Microsoft Defender for C
44
author: dcurwin
55
ms.author: dacurwin
66
ms.topic: reference
7-
ms.date: 01/29/2024
7+
ms.date: 05/05/2024
88
---
99

1010
# Archive for what's new in Defender for Cloud?
@@ -16,6 +16,7 @@ This page provides you with information about features, fixes, and deprecations
1616

1717
|Date |Update |
1818
|----------|----------|
19+
| September 30 | [Change to the Log Analytics daily cap](#change-to-the-log-analytics-daily-cap) |
1920
| September 27 | [Data security dashboard available in public preview](#data-security-dashboard-available-in-public-preview) |
2021
| September 21 | [Preview release: New autoprovisioning process for SQL Server on machines plan](#preview-release-new-autoprovisioning-process-for-sql-server-on-machines-plan) |
2122
| September 20 | [GitHub Advanced Security for Azure DevOps alerts in Defender for Cloud](#github-advanced-security-for-azure-devops-alerts-in-defender-for-cloud) |
@@ -26,6 +27,32 @@ This page provides you with information about features, fixes, and deprecations
2627
| September 5 | [Sensitive data discovery for PaaS databases (Preview)](#sensitive-data-discovery-for-paas-databases-preview) |
2728
| September 1 | [General Availability (GA): malware scanning in Defender for Storage](#general-availability-ga-malware-scanning-in-defender-for-storage)|
2829

30+
### Change to the Log Analytics daily cap
31+
32+
Azure monitor offers the capability to [set a daily cap](../azure-monitor/logs/daily-cap.md) on the data that is ingested on your Log analytics workspaces. However, Defenders for Cloud security events are currently not supported in those exclusions.
33+
34+
The Log Analytics Daily Cap no longer exclude the following set of data types:
35+
36+
- WindowsEvent
37+
- SecurityAlert
38+
- SecurityBaseline
39+
- SecurityBaselineSummary
40+
- SecurityDetection
41+
- SecurityEvent
42+
- WindowsFirewall
43+
- MaliciousIPCommunication
44+
- LinuxAuditLog
45+
- SysmonEvent
46+
- ProtectionStatus
47+
- Update
48+
- UpdateSummary
49+
- CommonSecurityLog
50+
- Syslog
51+
52+
All billable data types will be capped if the daily cap is met. This change improves your ability to fully contain costs from higher-than-expected data ingestion.
53+
54+
Learn more about [workspaces with Microsoft Defender for Cloud](../azure-monitor/logs/daily-cap.md#workspaces-with-microsoft-defender-for-cloud).
55+
2956
### Data security dashboard available in public preview
3057

3158
September 27, 2023

‎articles/defender-for-cloud/release-notes.md

Lines changed: 58 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -326,13 +326,22 @@ The Defender for Cloud Containers Vulnerability Assessment powered by Qualys is
326326

327327
|Date | Update |
328328
|----------|----------|
329+
| February 28 | [Microsoft Security Code Analysis (MSCA) is no longer operational](#microsoft-security-code-analysis-msca-is-no-longer-operational) |
329330
| February 28 | [Updated security policy management expands support to AWS and GCP](#updated-security-policy-management-expands-support-to-aws-and-gcp) |
330331
| February 26 | [Cloud support for Defender for Containers](#cloud-support-for-defender-for-containers) |
331332
| February 20 | [New version of Defender sensor for Defender for Containers](#new-version-of-defender-sensor-for-defender-for-containers) |
332333
| February 18| [Open Container Initiative (OCI) image format specification support](#open-container-initiative-oci-image-format-specification-support) |
333334
| February 13 | [AWS container vulnerability assessment powered by Trivy retired](#aws-container-vulnerability-assessment-powered-by-trivy-retired) |
334335
| February 8 | [Recommendations released for preview: four recommendations for Azure Stack HCI resource type](#recommendations-released-for-preview-four-recommendations-for-azure-stack-hci-resource-type) |
335336

337+
## Microsoft Security Code Analysis (MSCA) is no longer operational
338+
339+
February 28, 2024
340+
341+
MSCA is no longer operational.
342+
343+
Customers can get the latest DevOps security tooling from Defender for Cloud through [Microsoft Security DevOps](azure-devops-extension.yml) and more security tooling through [GitHub Advanced Security for Azure DevOps](https://azure.microsoft.com/products/devops/github-advanced-security).
344+
336345
### Updated security policy management expands support to AWS and GCP
337346

338347
February 28, 2024
@@ -525,6 +534,7 @@ See the [list of security recommendations](recommendations-reference.md).
525534

526535
| Date | Update |
527536
|--|--|
537+
| December 30 | [Consolidation of Defender for Cloud's Service Level 2 names](#consolidation-of-defender-for-clouds-service-level-2-names) |
528538
| December 24 | [Defender for Servers at the resource level available as GA](#defender-for-servers-at-the-resource-level-available-as-ga) |
529539
| December 21 | [Retirement of Classic connectors for multicloud](#retirement-of-classic-connectors-for-multicloud) |
530540
| December 21 | [Release of the Coverage workbook](#release-of-the-coverage-workbook) |
@@ -536,6 +546,54 @@ See the [list of security recommendations](recommendations-reference.md).
536546
| December 12 | [Container vulnerability assessment powered by Microsoft Defender Vulnerability Management now supports Google Distroless](#container-vulnerability-assessment-powered-by-microsoft-defender-vulnerability-management-now-supports-google-distroless) |
537547
| December 4 | [Defender for Storage alert released for preview: malicious blob was downloaded from a storage account](#defender-for-storage-alert-released-for-preview-malicious-blob-was-downloaded-from-a-storage-account) |
538548

549+
### Consolidation of Defender for Cloud's Service Level 2 names
550+
551+
December 30, 2023
552+
553+
We're consolidating the legacy Service Level 2 names for all Defender for Cloud plans into a single new Service Level 2 name, **Microsoft Defender for Cloud**.
554+
555+
Today, there are four Service Level 2 names: Azure Defender, Advanced Threat Protection, Advanced Data Security, and Security Center. The various meters for Microsoft Defender for Cloud are grouped across these separate Service Level 2 names, creating complexities when using Cost Management + Billing, invoicing, and other Azure billing-related tools.
556+
557+
The change simplifies the process of reviewing Defender for Cloud charges and provides better clarity in cost analysis.
558+
559+
To ensure a smooth transition, we've taken measures to maintain the consistency of the Product/Service name, SKU, and Meter IDs. Impacted customers will receive an informational Azure Service Notification to communicate the changes.
560+
561+
Organizations that retrieve cost data by calling our APIs, will need to update the values in their calls to accommodate the change. For example, in this filter function, the values will return no information:
562+
563+
```json
564+
"filter": {
565+
"dimensions": {
566+
"name": "MeterCategory",
567+
"operator": "In",
568+
"values": [
569+
"Advanced Threat Protection",
570+
"Advanced Data Security",
571+
"Azure Defender",
572+
"Security Center"
573+
]
574+
}
575+
}
576+
```
577+
578+
| OLD Service Level 2 name | NEW Service Level 2 name | Service Tier - Service Level 4 (No change) |
579+
|--|--|--|
580+
|Advanced Data Security |Microsoft Defender for Cloud|Defender for SQL|
581+
|Advanced Threat Protection|Microsoft Defender for Cloud|Defender for Container Registries |
582+
|Advanced Threat Protection|Microsoft Defender for Cloud|Defender for DNS |
583+
|Advanced Threat Protection|Microsoft Defender for Cloud|Defender for Key Vault|
584+
|Advanced Threat Protection|Microsoft Defender for Cloud|Defender for Kubernetes|
585+
|Advanced Threat Protection|Microsoft Defender for Cloud|Defender for MySQL|
586+
|Advanced Threat Protection|Microsoft Defender for Cloud|Defender for PostgreSQL|
587+
|Advanced Threat Protection|Microsoft Defender for Cloud|Defender for Resource Manager|
588+
|Advanced Threat Protection|Microsoft Defender for Cloud|Defender for Storage|
589+
|Azure Defender |Microsoft Defender for Cloud|Defender for External Attack Surface Management|
590+
|Azure Defender |Microsoft Defender for Cloud|Defender for Azure Cosmos DB|
591+
|Azure Defender |Microsoft Defender for Cloud|Defender for Containers|
592+
|Azure Defender |Microsoft Defender for Cloud|Defender for MariaDB|
593+
|Security Center |Microsoft Defender for Cloud|Defender for App Service|
594+
|Security Center |Microsoft Defender for Cloud|Defender for Servers|
595+
|Security Center |Microsoft Defender for Cloud|Defender CSPM |
596+
539597
### Defender for Servers at the resource level available as GA
540598

541599
December 24, 2023

‎articles/defender-for-cloud/upcoming-changes.md

Lines changed: 0 additions & 91 deletions
Original file line numberDiff line numberDiff line change
@@ -34,18 +34,15 @@ If you're looking for the latest release notes, you can find them in the [What's
3434
| [Deprecating of virtual machine recommendation](#deprecating-of-virtual-machine-recommendation) | April 2, 2024 | April 30, 2024 |
3535
| [General Availability of Unified Disk Encryption recommendations](#general-availability-of-unified-disk-encryption-recommendations) | March 28, 2024 | April 30, 2024 |
3636
| [Changes in where you access Compliance offerings and Microsoft Actions](#changes-in-where-you-access-compliance-offerings-and-microsoft-actions) | March 3, 2024 | September 30, 2025 |
37-
| [Microsoft Security Code Analysis (MSCA) is no longer operational](#microsoft-security-code-analysis-msca-is-no-longer-operational) | February 26, 2024 | February 26, 2024 |
3837
| [Decommissioning of Microsoft.SecurityDevOps resource provider](#decommissioning-of-microsoftsecuritydevops-resource-provider) | February 5, 2024 | March 6, 2024 |
3938
| [Change in pricing for multicloud container threat detection](#change-in-pricing-for-multicloud-container-threat-detection) | January 30, 2024 | April 2024 |
4039
| [Enforcement of Defender CSPM for Premium DevOps Security Capabilities](#enforcement-of-defender-cspm-for-premium-devops-security-value) | January 29, 2024 | March 2024 |
4140
| [Update to agentless VM scanning built-in Azure role](#update-to-agentless-vm-scanning-built-in-azure-role) |January 14, 2024 | February 2024 |
4241
| [Defender for Servers built-in vulnerability assessment (Qualys) retirement path](#defender-for-servers-built-in-vulnerability-assessment-qualys-retirement-path) | January 9, 2024 | May 2024 |
4342
| [Upcoming change for the Defender for Cloud’s multicloud network requirements](#upcoming-change-for-the-defender-for-clouds-multicloud-network-requirements) | January 3, 2024 | May 2024 |
4443
| [Deprecation of two DevOps security recommendations](#deprecation-of-two-devops-security-recommendations) | November 30, 2023 | January 2024 |
45-
| [Consolidation of Defender for Cloud's Service Level 2 names](#consolidation-of-defender-for-clouds-service-level-2-names) | November 1, 2023 | December 2023 |
4644
| [Changes to how Microsoft Defender for Cloud's costs are presented in Microsoft Cost Management](#changes-to-how-microsoft-defender-for-clouds-costs-are-presented-in-microsoft-cost-management) | October 25, 2023 | November 2023 |
4745
| [Replacing the "Key Vaults should have purge protection enabled" recommendation with combined recommendation "Key Vaults should have deletion protection enabled"](#replacing-the-key-vaults-should-have-purge-protection-enabled-recommendation-with-combined-recommendation-key-vaults-should-have-deletion-protection-enabled) | | June 2023|
48-
| [Change to the Log Analytics daily cap](#change-to-the-log-analytics-daily-cap) | | September 2023 |
4946
| [DevOps Resource Deduplication for Defender for DevOps](#devops-resource-deduplication-for-defender-for-devops) | | November 2023 |
5047
| [Deprecating two security incidents](#deprecating-two-security-incidents) | | November 2023 |
5148
| [Defender for Cloud plan and strategy for the Log Analytics agent deprecation](#defender-for-cloud-plan-and-strategy-for-the-log-analytics-agent-deprecation) | | August 2024 |
@@ -179,16 +176,6 @@ The table that lists the compliance status of Microsoft's products (accessed fro
179176

180177
For a subset of controls, Microsoft Actions was accessible from the **Microsoft Actions (Preview)** button in the controls details pane. After this button is removed, you can view Microsoft Actions by visiting Microsoft’s [Service Trust Portal for FedRAMP](https://servicetrust.microsoft.com/viewpage/FedRAMP) and accessing the Azure System Security Plan document.
181178

182-
## Microsoft Security Code Analysis (MSCA) is no longer operational
183-
184-
**Announcement date: February 26, 2024**
185-
186-
**Estimated date for change: February 26, 2024**
187-
188-
In February 2021, the deprecation of the MSCA task was communicated to all customers and has been past end of life support since [March 2022](https://devblogs.microsoft.com/premier-developer/microsoft-security-code-analysis/). As of February 26, 2024, MSCA is officially no longer operational.
189-
190-
Customers can get the latest DevOps security tooling from Defender for Cloud through [Microsoft Security DevOps](azure-devops-extension.yml) and more security tooling through [GitHub Advanced Security for Azure DevOps](https://azure.microsoft.com/products/devops/github-advanced-security).
191-
192179
## Decommissioning of Microsoft.SecurityDevOps resource provider
193180

194181
**Announcement date: February 5, 2024**
@@ -315,58 +302,6 @@ This means instead of a singular recommendation for all discovered misconfigurat
315302

316303
For more information, see the [new recommendations](recommendations-reference-devops.md).
317304

318-
## Consolidation of Defender for Cloud's Service Level 2 names
319-
320-
**Announcement date: November 1, 2023**
321-
322-
**Estimated date for change: December 2023**
323-
324-
We're consolidating the legacy Service Level 2 names for all Defender for Cloud plans into a single new Service Level 2 name, **Microsoft Defender for Cloud**.
325-
326-
Today, there are four Service Level 2 names: Azure Defender, Advanced Threat Protection, Advanced Data Security, and Security Center. The various meters for Microsoft Defender for Cloud are grouped across these separate Service Level 2 names, creating complexities when using Cost Management + Billing, invoicing, and other Azure billing-related tools.
327-
328-
The change simplifies the process of reviewing Defender for Cloud charges and provides better clarity in cost analysis.
329-
330-
To ensure a smooth transition, we've taken measures to maintain the consistency of the Product/Service name, SKU, and Meter IDs. Impacted customers will receive an informational Azure Service Notification to communicate the changes.
331-
332-
Organizations that retrieve cost data by calling our APIs, will need to update the values in their calls to accommodate the change. For example, in this filter function, the values will return no information:
333-
334-
```json
335-
"filter": {
336-
"dimensions": {
337-
"name": "MeterCategory",
338-
"operator": "In",
339-
"values": [
340-
"Advanced Threat Protection",
341-
"Advanced Data Security",
342-
"Azure Defender",
343-
"Security Center"
344-
]
345-
}
346-
}
347-
```
348-
349-
The change is planned to go into effect on December 1, 2023.
350-
351-
| OLD Service Level 2 name | NEW Service Level 2 name | Service Tier - Service Level 4 (No change) |
352-
|--|--|--|
353-
|Advanced Data Security |Microsoft Defender for Cloud|Defender for SQL|
354-
|Advanced Threat Protection|Microsoft Defender for Cloud|Defender for Container Registries |
355-
|Advanced Threat Protection|Microsoft Defender for Cloud|Defender for DNS |
356-
|Advanced Threat Protection|Microsoft Defender for Cloud|Defender for Key Vault|
357-
|Advanced Threat Protection|Microsoft Defender for Cloud|Defender for Kubernetes|
358-
|Advanced Threat Protection|Microsoft Defender for Cloud|Defender for MySQL|
359-
|Advanced Threat Protection|Microsoft Defender for Cloud|Defender for PostgreSQL|
360-
|Advanced Threat Protection|Microsoft Defender for Cloud|Defender for Resource Manager|
361-
|Advanced Threat Protection|Microsoft Defender for Cloud|Defender for Storage|
362-
|Azure Defender |Microsoft Defender for Cloud|Defender for External Attack Surface Management|
363-
|Azure Defender |Microsoft Defender for Cloud|Defender for Azure Cosmos DB|
364-
|Azure Defender |Microsoft Defender for Cloud|Defender for Containers|
365-
|Azure Defender |Microsoft Defender for Cloud|Defender for MariaDB|
366-
|Security Center |Microsoft Defender for Cloud|Defender for App Service|
367-
|Security Center |Microsoft Defender for Cloud|Defender for Servers|
368-
|Security Center |Microsoft Defender for Cloud|Defender CSPM |
369-
370305
## Changes to how Microsoft Defender for Cloud's costs are presented in Microsoft Cost Management
371306

372307
**Announcement date: October 26, 2023**
@@ -391,32 +326,6 @@ The `Key Vaults should have purge protection enabled` recommendation is deprecat
391326

392327
See the [full index of Azure Policy built-in policy definitions for Key Vault](../key-vault/policy-reference.md).
393328

394-
## Change to the Log Analytics daily cap
395-
396-
Azure monitor offers the capability to [set a daily cap](../azure-monitor/logs/daily-cap.md) on the data that is ingested on your Log analytics workspaces. However, Defenders for Cloud security events are currently not supported in those exclusions.
397-
398-
Starting on September 18, 2023 the Log Analytics Daily Cap will no longer exclude the following set of data types:
399-
400-
- WindowsEvent
401-
- SecurityAlert
402-
- SecurityBaseline
403-
- SecurityBaselineSummary
404-
- SecurityDetection
405-
- SecurityEvent
406-
- WindowsFirewall
407-
- MaliciousIPCommunication
408-
- LinuxAuditLog
409-
- SysmonEvent
410-
- ProtectionStatus
411-
- Update
412-
- UpdateSummary
413-
- CommonSecurityLog
414-
- Syslog
415-
416-
At that time, all billable data types will be capped if the daily cap is met. This change improves your ability to fully contain costs from higher-than-expected data ingestion.
417-
418-
Learn more about [workspaces with Microsoft Defender for Cloud](../azure-monitor/logs/daily-cap.md#workspaces-with-microsoft-defender-for-cloud).
419-
420329
## DevOps Resource Deduplication for Defender for DevOps
421330

422331
**Estimated date for change: November 2023**

0 commit comments

Comments
 (0)