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: modules/customizing-and-automating-your-compliance-scans.adoc
+1-2Lines changed: 1 addition & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,6 @@ By creating a compliance scan schedule, you can customize and automate your comp
13
13
You can only have one schedule that scans the same profile on the same cluster. This means that you cannot create multiple scan schedules for the same profile on a single cluster.
14
14
====
15
15
16
-
17
16
.Prerequisites
18
17
19
18
* You have installed the Compliance Operator version 1.6.0 or later.
@@ -24,7 +23,7 @@ For more information about how to install the Compliance Operator, see "Using th
24
23
====
25
24
** Currently, the compliance feature and the Compliance Operator evaluate only infrastructure and platform compliance.
26
25
27
-
**The compliance feature requires the Compliance Operator to be running and does _not_ support Amazon Elastic Kubernetes Service (EKS).
26
+
**To use the compliance feature, you must run the Compliance Operator on a {osp} cluster.
* xref:../operating/manage-compliance/scheduling-compliance-scans-and-assessing-profile-compliance.adoc#customizing-and-automating-your-compliance-scans_scheduling-scans-and-assessing-profile-compliance[Customizing and automating your compliance scans]
38
+
* xref:../operating/manage-compliance/using-openshift-compliance.adoc#customizing-and-automating-your-compliance-scans_using-openshift-compliance[Customizing and automating your compliance scans]
* link:https://access.redhat.com/documentation/en-us/openshift_container_platform/{ocp-latest-version}/html/security_and_compliance/compliance-operator#understanding-compliance-operator[Understanding the Compliance Operator]
* xref:../operating/manage-compliance/monitoring-workload-and-cluster-compliance.adoc#checking-the-compliance-status-of-your-infrastructure_monitoring-workload-and-cluster-compliance[Checking the compliance status of your infrastructure]
51
-
* xref:../operating/manage-compliance/monitoring-workload-and-cluster-compliance.adoc#viewing-the-compliance-standards-across-your-environment_monitoring-workload-and-cluster-compliance[Viewing the compliance standards across your environment]
52
-
* xref:../operating/manage-compliance/scheduling-compliance-scans-and-assessing-profile-compliance.adoc#assessing-the-profile-compliance-across-clusters_scheduling-scans-and-assessing-profile-compliance[Assessing the profile compliance across clusters]
50
+
* xref:../operating/manage-compliance/using-the-compliance-dashboard.adoc#checking-the-compliance-status-of-your-infrastructure_using-the-compliance-dashboard[Checking the compliance status of your infrastructure]
51
+
* xref:../operating/manage-compliance/using-the-compliance-dashboard.adoc#viewing-the-compliance-standards-across-your-environment_using-the-compliance-dashboard[Viewing the compliance standards across your environment]
52
+
* xref:../operating/manage-compliance/using-openshift-compliance.adoc#assessing-the-profile-compliance-across-clusters_using-openshift-compliance[Assessing the profile compliance across clusters]
Copy file name to clipboardExpand all lines: operating/manage-compliance/compliance-feature-overview.adoc
+20-11Lines changed: 20 additions & 11 deletions
Original file line number
Diff line number
Diff line change
@@ -12,25 +12,34 @@ The feature includes detailed reports and remediation guidance to help administr
12
12
13
13
The compliance feature summarizes information into the following sections:
14
14
15
-
Dashboard:: Formerly known as _Compliance 1.0_, summarizes the compliance information collected from all your clusters. It covers workload and infrastructure compliance.
Formerly known as _Compliance 2.0_, summarizes the compliance information in a single interface after the scheduled scans by using the Compliance Operator.
22
+
17
23
[IMPORTANT]
18
24
====
19
-
By running a compliance scan in {product-title-short}, you can monitor the entire Kubernetes infrastructure and workloads and ensure that they meet the required standards. You can use the compliance dashboard for filtering and detailed reporting.
25
+
* If you have {osp} clusters with the Compliance Operator installed, you can create and manage compliance scan schedules directly in {product-title-short} on the schedules page. The coverage page shows you the scan results associated with a benchmark and profile in a single interface.
20
26
21
-
For more information, see xref:../../operating/manage-compliance/monitoring-workload-and-cluster-compliance.adoc#monitoring-workload-and-cluster-compliance[Monitoring workload and cluster compliance].
27
+
* You can now use the new OpenShift infrastructure compliance feature to assess compliance across your entire OpenShift cluster fleet and ensure consistent adherence to the security policies of your organization. {product-title-short} now generates reports even if some clusters in a scheduled scan fail, so that you can maintain visibility into the compliance status of successfully scanned clusters without data gaps.
28
+
+
29
+
For more information, see xref:../../operating/manage-compliance/using-openshift-compliance.adoc#using-openshift-compliance[Using OpenShift compliance].
22
30
====
23
31
24
-
OpenShift Schedules and OpenShift Coverage:: Formerly known as _Compliance 2.0_, summarizes the compliance information in a single interface after the scheduled scans by using the Compliance Operator.
25
-
+
32
+
[id="dashboard_{context}"]
33
+
== Dashboard (deprecated)
34
+
35
+
Formerly known as _Compliance 1.0_, summarizes the compliance information collected from all your clusters. It covers workload and infrastructure compliance. The dashboard is deprecated in {product-title-short} 4.8 and will be removed in a future release.
36
+
26
37
[IMPORTANT]
27
38
====
28
-
* If you have {osp} clusters with the Compliance Operator installed, you can create and manage compliance scan schedules directly in {product-title-short} on the schedules page. The coverage page shows you the scan results associated with a benchmark and profile in a single interface.
39
+
By running a compliance scan in {product-title-short}, you can monitor the entire Kubernetes infrastructure and workloads and ensure that they meet the required standards. You can use the compliance dashboard for filtering and detailed reporting.
29
40
30
-
* You can now use the new OpenShift Infrastructure Compliance feature to assess compliance across your entire OpenShift cluster fleet and ensure consistent adherence to the security policies of your organization. {product-title-short} now generates reports even if some clusters in a scheduled scan fail, so that you can maintain visibility into the compliance status of successfully scanned clusters without data gaps.
31
-
+
32
-
For more information, see xref:../../operating/manage-compliance/scheduling-compliance-scans-and-assessing-profile-compliance.adoc#scheduling-compliance-scans-and-assessing-profile-compliance[Scheduling compliance scans and assessing profile compliance].
41
+
For more information, see xref:../../operating/manage-compliance/using-the-compliance-dashboard.adoc#using-the-compliance-dashboard[Using the compliance dashboard (deprecated)].
33
42
====
34
43
35
44
//Compliance assessment and reporting by using {product-title-short}
* xref:../../operating/manage-compliance/scheduling-compliance-scans-and-assessing-profile-compliance.adoc#customizing-and-automating-your-compliance-scans_scheduling-scans-and-assessing-profile-compliance[Customizing and automating your compliance scans]
27
+
* xref:../../operating/manage-compliance/using-openshift-compliance.adoc#customizing-and-automating-your-compliance-scans_using-openshift-compliance[Customizing and automating your compliance scans]
* xref:../../operating/compliance-operator-rhacs.adoc#compliance-operator-rhacs[Using the Compliance Operator with {product-title}]
45
-
* xref:../../operating/manage-compliance/scheduling-compliance-scans-and-assessing-profile-compliance.adoc#customizing-and-automating-your-compliance-scans_scheduling-scans-and-assessing-profile-compliance[Customizing and automating your compliance scans]
45
+
* xref:../../operating/manage-compliance/using-openshift-compliance.adoc#customizing-and-automating-your-compliance-scans_using-openshift-compliance[Customizing and automating your compliance scans]
Copy file name to clipboardExpand all lines: operating/view-dashboard.adoc
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -112,6 +112,6 @@ You can use the *Compliance by standard* widget with the Dashboard filter to foc
112
112
====
113
113
The *Compliance* widget shows details only after you run a compliance scan.
114
114
115
-
For more information, see xref:../operating/manage-compliance/monitoring-workload-and-cluster-compliance.adoc#checking-the-compliance-status-of-your-infrastructure_monitoring-workload-and-cluster-compliance[Checking the compliance status of your infrastructure].
115
+
For more information, see xref:../operating/manage-compliance/using-the-compliance-dashboard.adoc#checking-the-compliance-status-of-your-infrastructure_using-the-compliance-dashboard[Checking the compliance status of your infrastructure].
0 commit comments