You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/governance/policy/samples/cmmc-l3.md
+7-4Lines changed: 7 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,14 +1,14 @@
1
1
---
2
2
title: Regulatory Compliance details for CMMC Level 3
3
3
description: Details of the CMMC Level 3 Regulatory Compliance built-in initiative. Each control is mapped to one or more Azure Policy definitions that assist with assessment.
4
-
ms.date: 03/14/2022
4
+
ms.date: 04/01/2022
5
5
ms.topic: sample
6
6
ms.custom: generated
7
7
---
8
8
# Details of the CMMC Level 3 Regulatory Compliance built-in initiative
9
9
10
10
The following article details how the Azure Policy Regulatory Compliance built-in initiative
11
-
definition maps to **compliance domains** and **controls** in CMMC Level 3.
11
+
definition maps to **compliance domains** and **controls** in Cybersecurity Maturity Model Certification (CMMC) Level 3.
12
12
For more information about this compliance standard, see
13
13
[CMMC Level 3](https://www.acq.osd.mil/cmmc/documentation.html). To understand
14
14
_Ownership_, see [Azure Policy policy definition](../concepts/definition-structure.md#type) and
@@ -22,6 +22,9 @@ Then, find and select the **CMMC Level 3** Regulatory Compliance built-in
22
22
initiative definition.
23
23
24
24
> [!IMPORTANT]
25
+
> This policy initiative was built to CMMC version 1.0 and will be updated in the future".
26
+
> CMMC Level 2 under CMMC 2.0 is similar to CMMC Level 3 under CMMC 1.0, but has different control mappings.
27
+
>
25
28
> Each control below is associated with one or more [Azure Policy](../overview.md) definitions.
26
29
> These policies may help you [assess compliance](../how-to/get-compliance-data.md) with the
27
30
> control; however, there often is not a one-to-one or complete match between a control and one or
@@ -31,7 +34,7 @@ initiative definition.
31
34
> definitions at this time. Therefore, compliance in Azure Policy is only a partial view of your
32
35
> overall compliance status. The associations between compliance domains, controls, and Azure Policy
33
36
> definitions for this compliance standard may change over time. To view the change history, see the
0 commit comments