diff --git a/docs/platform/compliance/monitor/frameworks.mdx b/docs/platform/compliance/monitor/frameworks.mdx index 4ac57356b..06c6beec5 100644 --- a/docs/platform/compliance/monitor/frameworks.mdx +++ b/docs/platform/compliance/monitor/frameworks.mdx @@ -89,15 +89,25 @@ import Partial from "../../partials/_editor-owner.mdx"; 2. In the side navigation bar, under **Compliance**, select **Frameworks**. - ![Compliance in the Mondoo Console](/img/platform/compliance/home.png) + ![Compliance in the Mondoo Console](/img/platform/compliance/compliance-empty.png) -3. Select the framework you want to comply with. +3. Select the **SELECT COMPLIANCE FRAMEWORK** button. - ![Compliance framework in the Mondoo Console](/img/platform/compliance/preview.png) + ![Compliance in the Mondoo Console](/img/platform/compliance/frameworks.png) -4. To enable the framework, select the large toggle near the top-right corner of the framework page. +4. Select the framework you want to comply with. -5. Follow the steps in the next section to enable the policies that the framework relies on. + ![Compliance framework in the Mondoo Console](/img/platform/compliance/active-or-preview.png) + +5. Choose how to identify your work on the framework: + + - **ACTIVE** shows your team that you're working toward an upcoming audit based on this framework. + + - **PREVIEW** reflects that you're in the early stages of work toward complying with the framework and not yet striving to pass an audit. + +6. Select the **ADD FRAMEWORK** button. + + ![Compliance framework in the Mondoo Console](/img/platform/compliance/compliance-1fmwk.png) :::tip @@ -113,13 +123,11 @@ Frameworks don't contain checks; they contain controls. Each control maps to one The controls in a framework typically map to checks in many different policies. In the CIS Controls example in the previous section, the single control, _Implement and manage a firewall on end-user devices_, maps to checks in different Ubuntu policies, macOS policies, Windows policies, and more. For the CIS Controls framework to accurately assess the compliance of all these different types of devices, each of those policies must be enabled. -After you enable a framework, Mondoo tells you which policies you must enable in order to measure compliance with that framework. +After you enable a framework, Mondoo recommend policies to enable in order to measure compliance with that framework. ![Recommended policies for a framework](/img/platform/compliance/recommended.png) -To enable a policy, hover over the policy and select the Enable icon. - -![Enable a recommended policy for a framework](/img/platform/compliance/enable-recommended.png) +To enable a policy, hover over the policy and select the Enabled icon. {" "} diff --git a/docs/platform/compliance/monitor/progress.mdx b/docs/platform/compliance/monitor/progress.mdx index a93e62260..17e47cf7b 100644 --- a/docs/platform/compliance/monitor/progress.mdx +++ b/docs/platform/compliance/monitor/progress.mdx @@ -38,8 +38,6 @@ From the Compliance Frameworks page, you can select a framework to learn more ab **COMPLETION** shows overall progress toward compliance. -**CONTROL DISTRIBUTION** shows a high-level view of the state of controls in the framework: enabled, snoozed, and disabled. To learn about control states, read [Customize Compliance](/platform/compliance/customize/overview/). - Using the tabs in the lower portion of the framework page, you can drill down into different details. - The **Controls** tab lists all the controls in the framework. You can see your progress on each control and select a control to see details on the checks it maps to. diff --git a/static/img/platform/compliance/active-or-preview.png b/static/img/platform/compliance/active-or-preview.png new file mode 100644 index 000000000..a43cb96d4 Binary files /dev/null and b/static/img/platform/compliance/active-or-preview.png differ diff --git a/static/img/platform/compliance/compliance-1fmwk.png b/static/img/platform/compliance/compliance-1fmwk.png new file mode 100644 index 000000000..503c55e60 Binary files /dev/null and b/static/img/platform/compliance/compliance-1fmwk.png differ diff --git a/static/img/platform/compliance/compliance-empty.png b/static/img/platform/compliance/compliance-empty.png new file mode 100644 index 000000000..12d7200a3 Binary files /dev/null and b/static/img/platform/compliance/compliance-empty.png differ diff --git a/static/img/platform/compliance/framework.png b/static/img/platform/compliance/framework.png index 6eed02221..6d26bc53d 100644 Binary files a/static/img/platform/compliance/framework.png and b/static/img/platform/compliance/framework.png differ diff --git a/static/img/platform/compliance/frameworks.png b/static/img/platform/compliance/frameworks.png new file mode 100644 index 000000000..afd4b293d Binary files /dev/null and b/static/img/platform/compliance/frameworks.png differ diff --git a/static/img/platform/compliance/home.png b/static/img/platform/compliance/home.png index c4079907f..f9a373b4a 100644 Binary files a/static/img/platform/compliance/home.png and b/static/img/platform/compliance/home.png differ diff --git a/static/img/platform/compliance/preview.png b/static/img/platform/compliance/preview.png deleted file mode 100644 index ea41bf66a..000000000 Binary files a/static/img/platform/compliance/preview.png and /dev/null differ diff --git a/static/img/platform/compliance/recommended.png b/static/img/platform/compliance/recommended.png index d7c255674..8c24d36fa 100644 Binary files a/static/img/platform/compliance/recommended.png and b/static/img/platform/compliance/recommended.png differ diff --git a/static/img/platform/compliance/report-icon.png b/static/img/platform/compliance/report-icon.png index 60c03c66d..edd11c528 100644 Binary files a/static/img/platform/compliance/report-icon.png and b/static/img/platform/compliance/report-icon.png differ