1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 21:46:22 +01:00

Merge pull request #74381 from rhmdnd/clarify-what-compliance-means

This commit is contained in:
Andrew Taylor
2024-04-11 14:32:30 -04:00
committed by GitHub
2 changed files with 26 additions and 8 deletions

View File

@@ -4,12 +4,21 @@
include::_attributes/common-attributes.adoc[]
:context: co-overview
{product-title} Compliance Operator (CO) runs compliance scans and provides remediations to assist users in meeting compliance standards. For the latest updates, see the xref:../../security/compliance_operator/compliance-operator-release-notes.adoc#compliance-operator-release-notes[Compliance Operator release notes]. If needed, you can engage link:https://access.redhat.com/support/[Red Hat support].
The {product-title} Compliance Operator assists users by automating the
inspection of numerous technical implementations and compares those against
certain aspects of industry standards, benchmarks, and baselines; the
Compliance Operator is not an auditor. In order to be compliant or certified
under these various standards, you need to engage an authorized auditor such as
a Qualified Security Assessor (QSA), Joint Authorization Board (JAB), or other
industry recognized regulatory authority to assess your environment.
[IMPORTANT]
====
The Compliance Operator does not automatically perform remediations. Ensuring compliance standards are met is required by the user.
====
The Compliance Operator makes recommendations based on generally available
information and practices regarding such standards and may assist with
remediations, but actual compliance is your responsibility. You are required to
work with an authorized auditor to achieve compliance with a standard. For the
latest updates, see the
xref:../../security/compliance_operator/compliance-operator-release-notes.adoc#compliance-operator-release-notes[Compliance
Operator release notes]
[discrete]
==== Compliance Operator concepts
@@ -47,4 +56,4 @@ xref:../../security/compliance_operator/co-scans/compliance-operator-advanced.ad
xref:../../security/compliance_operator/co-scans/compliance-operator-troubleshooting.adoc#compliance-operator-troubleshooting[Troubleshooting the Compliance Operator]
xref:../../security/compliance_operator/co-scans/oc-compliance-plug-in-using.adoc#using-oc-compliance-plug-in[Using the oc-compliance plugin]
xref:../../security/compliance_operator/co-scans/oc-compliance-plug-in-using.adoc#using-oc-compliance-plug-in[Using the oc-compliance plugin]

View File

@@ -4,7 +4,16 @@
include::_attributes/common-attributes.adoc[]
:context: compliance-operator-supported-profiles
There are several profiles available as part of the Compliance Operator (CO) installation. While you can use the following profiles to assess gaps in a cluster, usage alone does not infer or guarantee compliance with a particular profile.
There are several profiles available as part of the Compliance Operator (CO)
installation. While you can use the following profiles to assess gaps in a
cluster, usage alone does not infer or guarantee compliance with a particular
profile and is not an auditor.
In order to be compliant or certified under these various standards, you need
to engage an authorized auditor such as a Qualified Security Assessor (QSA),
Joint Authorization Board (JAB), or other industry recognized regulatory
authority to assess your environment. You are required to work with an
authorized auditor to achieve compliance with a standard.
[IMPORTANT]
@@ -18,4 +27,4 @@ include::modules/compliance-supported-profiles.adoc[leveloffset=+1]
[role="_additional-resources"]
== Additional resources
* xref:../../../security/compliance_operator/co-concepts/compliance-operator-understanding.html#compliance_profile_types_understanding-compliance[Compliance Operator profile types]
* xref:../../../security/compliance_operator/co-concepts/compliance-operator-understanding.adoc#compliance_profile_types_understanding-compliance[Compliance Operator profile types]