Skip to content

Commit c84f59b

Browse files
Merge pull request #250190 from AlizaBernstein/WI-154393-release-update-cis-name-regulatory
WI-154393-release-update-cis-name-regulatory
2 parents d09efec + d6b03e6 commit c84f59b

File tree

2 files changed

+24
-24
lines changed

2 files changed

+24
-24
lines changed

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

Lines changed: 23 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -24,9 +24,28 @@ If you're looking for items older than six months, you can find them in the [Arc
2424

2525
|Date |Update |
2626
|----------|----------|
27+
| September 6 | [Updated naming format of Center for Internet Security (CIS) standards in regulatory compliance](#updated-naming-format-of-center-for-internet-security-cis-standards-in-regulatory-compliance) |
2728
| September 5 | [Sensitive data discovery for PaaS databases (Preview)](#sensitive-data-discovery-for-paas-databases-preview) |
2829
| September 1 | [General Availability (GA): malware scanning in Defender for Storage](#general-availability-ga-malware-scanning-in-defender-for-storage)|
2930

31+
### Updated naming format of Center for Internet Security (CIS) standards in regulatory compliance
32+
33+
September 6, 2023
34+
35+
The naming format of CIS (Center for Internet Security) foundations benchmarks in the compliance dashboard is changed from `[Cloud] CIS [version number]` to `CIS [Cloud] Foundations v[version number]`. Refer to the following table:
36+
37+
| Current Name | New Name |
38+
|--|--|
39+
| Azure CIS 1.1.0 | CIS Azure Foundations v1.1.0 |
40+
| Azure CIS 1.3.0 | CIS Azure Foundations v1.3.0 |
41+
| Azure CIS 1.4.0 | CIS Azure Foundations v1.4.0 |
42+
| AWS CIS 1.2.0 | CIS AWS Foundations v1.2.0 |
43+
| AWS CIS 1.5.0 | CIS AWS Foundations v1.5.0 |
44+
| GCP CIS 1.1.0 | CIS GCP Foundations v1.1.0 |
45+
| GCP CIS 1.2.0 | CIS GCP Foundations v1.2.0 |
46+
47+
Learn how to [improve your regulatory compliance](regulatory-compliance-dashboard.md).
48+
3049
### Sensitive data discovery for PaaS databases (Preview)
3150

3251
September 5, 2023
@@ -55,11 +74,11 @@ Malware scanning is now generally available (GA) as an add-on to Defender for St
5574

5675
Learn more about [malware scanning in Defender for Storage](defender-for-storage-malware-scan.md).
5776

58-
Malware scanning is priced according to your data usage and budget. Billing begins on September 3, 2023. Visit the [pricing page](https://azure.microsoft.com/pricing/details/defender-for-cloud/) for more information.
77+
Malware scanning is priced according to your data usage and budget. Billing begins on September 3, 2023. Visit the [pricing page](https://azure.microsoft.com/pricing/details/defender-for-cloud/) for more information.
5978

60-
If you're using the previous plan (now renamed "Microsoft Defender for Storage (classic)"), you'll need to proactively [migrate to the new plan](defender-for-storage-classic-migrate.md) in order to enable malware scanning.
79+
If you're using the previous plan (now renamed "Microsoft Defender for Storage (classic)"), you'll need to proactively [migrate to the new plan](defender-for-storage-classic-migrate.md) in order to enable malware scanning.
6180

62-
Read the [Microsoft Defender for Cloud announcement blog post](https://techcommunity.microsoft.com/t5/microsoft-defender-for-cloud/malware-scanning-for-cloud-storage-ga-pre-announcement-prevent/ba-p/3884470).
81+
Read the [Microsoft Defender for Cloud announcement blog post](https://techcommunity.microsoft.com/t5/microsoft-defender-for-cloud/malware-scanning-for-cloud-storage-ga-pre-announcement-prevent/ba-p/3884470).
6382

6483
## August 2023
6584

@@ -85,7 +104,7 @@ We're excited to introduce to Defender For Containers: Agentless discovery for K
85104
- Kubernetes-specific security insights
86105
- Enhanced risk hunting with Cloud Security Explorer
87106

88-
Agentless discovery for Kubernetes is now available to all Defender For Containers customers. You can start using these advanced capabilities today. We encourage you to update your subscriptions to have the full set of extensions enabled, and benefit from the latest additions and features. Visit the **Environment and settings** pane of your Defender for Containers subscription to enable the extension.
107+
Agentless discovery for Kubernetes is now available to all Defender For Containers customers. You can start using these advanced capabilities today. We encourage you to update your subscriptions to have the full set of extensions enabled, and benefit from the latest additions and features. Visit the **Environment and settings** pane of your Defender for Containers subscription to enable the extension.
89108

90109
> [!NOTE]
91110
> Enabling the latest additions won't incur new costs to active Defender for Containers customers.

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

Lines changed: 1 addition & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Important upcoming changes
33
description: Upcoming changes to Microsoft Defender for Cloud that you might need to be aware of and for which you might need to plan
44
ms.topic: overview
5-
ms.date: 08/22/2023
5+
ms.date: 09/04/2023
66
---
77

88
# Important upcoming changes to Microsoft Defender for Cloud
@@ -26,7 +26,6 @@ If you're looking for the latest release notes, you can find them in the [What's
2626
|--|--|
2727
| [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|
2828
| [Changes to the Defender for DevOps recommendations environment source and resource ID](#changes-to-the-defender-for-devops-recommendations-environment-source-and-resource-id) | August 2023 |
29-
| [Update naming format of Azure Center for Internet Security standards in regulatory compliance](#update-naming-format-of-azure-center-for-internet-security-standards-in-regulatory-compliance) | August 2023 |
3029
| [Preview alerts for DNS servers to be deprecated](#preview-alerts-for-dns-servers-to-be-deprecated) | August 2023 |
3130
| [Deprecate and replace recommendations App Service Client Certificates](#deprecate-and-replace-recommendations-app-service-client-certificates) | August 2023 |
3231
| [Classic connectors for multicloud will be retired](#classic-connectors-for-multicloud-will-be-retired) | September 2023 |
@@ -177,24 +176,6 @@ Additionally, customers that have created custom queries using the DevOps workbo
177176

178177
The experience on the recommendations page will be impacted and require customers to query under "All recommendations" to view the new DevOps recommendations. For Azure DevOps, deprecated assessments may continue to show for a maximum of 14 days if new pipelines are not run. Refer to [Defender for DevOps Common questions](/azure/defender-for-cloud/faq-defender-for-devops#why-don-t-i-see-recommendations-for-findings-) for details.
179178

180-
### Update naming format of Azure Center for Internet Security standards in regulatory compliance
181-
182-
**Estimated date for change: August 2023**
183-
184-
The naming format of Azure CIS (Center for Internet Security) foundations benchmarks in the compliance dashboard is set for change from `[Cloud] CIS [version number]` to `CIS [Cloud] Foundations v[version number]`. Refer to the following table:
185-
186-
| Current Name | New Name |
187-
|--|--|
188-
| Azure CIS 1.1.0 | CIS Azure Foundations v1.1.0 |
189-
| Azure CIS 1.3.0 | CIS Azure Foundations v1.3.0 |
190-
| Azure CIS 1.4.0 | CIS Azure Foundations v1.4.0 |
191-
| AWS CIS 1.2.0 | CIS AWS Foundations v1.2.0 |
192-
| AWS CIS 1.5.0 | CIS AWS Foundations v1.5.0 |
193-
| GCP CIS 1.1.0 | CIS GCP Foundations v1.1.0 |
194-
| GCP CIS 1.2.0 | CIS GCP Foundations v1.2.0 |
195-
196-
Learn how to [improve your regulatory compliance](regulatory-compliance-dashboard.md).
197-
198179
### Preview alerts for DNS servers to be deprecated
199180

200181
**Estimated date for change: August 2023**

0 commit comments

Comments
 (0)