final fixes to sanity

Author: ElazarK

articles/defender-for-cloud/concept-regulatory-compliance-standards.md

@@ -3,7 +3,7 @@ title: Regulatory compliance standards in Microsoft Defender for Cloud
 description: Learn about regulatory compliance standards in Microsoft Defender for Cloud
 ms.topic: conceptual
 ms.custom: ignite-2022
-ms.date: 01/10/2023
+ms.date: 11/27/2023
 ---
 
 # Regulatory compliance standards
@@ -61,7 +61,7 @@ You can drill down into controls to get information about resources that have pa
 By default, when you enable Defender for Cloud, the following standards are enabled:
 
 - **Azure**: The [Microsoft Cloud Security Benchmark (MCSB)](concept-regulatory-compliance.md) is enabled for Azure subscriptions.
-- **AWS**: AWS accounts get the [AWS Foundational Security Best Practices standard](https://docs.aws.amazon.com/securityhub/latest/userguide/fsbp-standard.html) assigned. This standard contains AWS-specific guidelines for security and compliance best practices based on common compliance frameworks. AWS accounts also have MCSB assigned by default.
+- **AWS**: AWS accounts get the [AWS Foundational Security Best Practices standard](https://docs.aws.amazon.com/securityhub/latest/userguide/fsbp-standard.html) and [Microsoft Cloud Security Benchmark (MCSB)](concept-regulatory-compliance.md) assigned by default. AWS Foundational Security Best Practices standard contains AWS-specific guidelines for security and compliance best practices based on common compliance frameworks.
 - **GCP**: GCP projects get the GCP Default standard assigned.
 
 

articles/defender-for-cloud/custom-security-policies.md

@@ -3,7 +3,7 @@ title: Create custom security standards for Azure resources in Microsoft Defende
 description: Learn how to create custom security standards for Azure resources in Microsoft Defender for Cloud
 ms.topic: how-to
 ms.custom: ignite-2023
-ms.date: 11/21/2023
+ms.date: 11/27/2023
 zone_pivot_groups: manage-asc-initiatives
 ---
 

articles/defender-for-cloud/manage-mcsb.md

@@ -24,6 +24,8 @@ This article describes how you can manage recommendations provided by MCSB.
 
 - **Enforce** lets you take advantage of the **DeployIfNotExist** effect in Azure Policy, and automatically remediate non-compliant resources upon creation.
 
+    > [!NOTE]
+    > Enforce and Deny are applicable to Azure recommendations and are supported on a subset of recommendations.
 
 To review which recommendations you can deny and enforce, in the **Security policies** page, on the **Standards** tab, select **Microsoft cloud security benchmark** and drill into a recommendation to see if the deny/enforce actions are available.
 

articles/defender-for-cloud/secure-score-security-controls.md

@@ -2,7 +2,7 @@
 title: Secure score in Microsoft Defender for Cloud
 description: Learn about the Microsoft Cloud Security Benchmark secure score in Microsoft Defender for Cloud
 ms.topic: conceptual
-ms.date: 11/16/2023
+ms.date: 11/27/2023
 ---
 
 # Secure score

articles/defender-for-cloud/security-policy-concept.md

@@ -2,7 +2,7 @@
 title: Security policies, standards, and recommendations in Microsoft Defender for Cloud 
 description: Learn about security policies, standards, and recommendations in Microsoft Defender for Cloud.
 ms.topic: conceptual
-ms.date: 01/24/2023
+ms.date: 11/27/2023
 ---
 
 # Security policies in Defender for Cloud
@@ -21,7 +21,7 @@ Security standards in Defender for Cloud come from a couple of sources:
 - **Regulatory compliance standards**. In addition to MCSB, when you enable one or more [Defender for Cloud plans](defender-for-cloud-introduction.md) you can add standards from a wide range of predefined regulatory compliance programs. [Learn more](regulatory-compliance-dashboard.md).
 - **Custom standards**. You can create custom security standards in Defender for Cloud, and add built-in and custom recommendations to those custom standards as needed.
 
-Security standards in Defender for Cloud are based on the Defender for Cloud platform, or on [Azure Policy](../governance/policy/overview.md) [initiatives](../governance/policy/concepts/initiative-definition-structure.md). At the time of writing (November 2023) AWS and GCP standards are Defender for Cloud platform-based, and Azure standards are currently based on Azure Policy.
+Security standards in Defender for Cloud are based on [Azure Policy](../governance/policy/overview.md) [initiatives](../governance/policy/concepts/initiative-definition-structure.md) or on the Defender for Cloud native platform. At the time of writing (November 2023) AWS and GCP standards are Defender for Cloud platform-based, and Azure standards are currently based on Azure Policy.
 
 Security standards in Defender for Cloud simplify the complexity of Azure Policy. In most cases, you can work directly with security standards and recommendations in the Defender for Cloud portal, without needing to directly configure Azure Policy.