Merge pull request #45101 from stevsmit/GH44721

Replaces CSO Operator with Red hat Quay CS Operator

Author: stevsmit

_attributes/common-attributes.adoc

@@ -126,3 +126,5 @@ endif::[]
 :productwinc: Red Hat OpenShift support for Windows Containers
 // IBM zSystems
 :ibmzProductName: IBM Z
+// Red Hat Quay Container Security Operator
+:rhq-cso: Red Hat Quay Container Security Operator

modules/security-container-content-inside.adoc

@@ -30,5 +30,5 @@ scanning features, used directly from {op-system-base} or added to {product-titl
 can alert you when
 an image you are using has vulnerabilities. OpenSCAP image scanning is
 available in {op-system-base} and the
-link:https://access.redhat.com/documentation/en-us/red_hat_quay/3/html-single/manage_red_hat_quay/index#container-security-operator-setup[Container Security Operator] can be added
+link:https://access.redhat.com/documentation/en-us/red_hat_quay/3/html-single/manage_red_hat_quay/index#container-security-operator-setup[{rhq-cso}] can be added
 to check container images used in {product-title}.

modules/security-container-content-scanning.adoc

@@ -14,15 +14,15 @@ link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/ht
 For example, you can integrate static code analysis tools that test for security
 flaws in your source code and software composition analysis tools that identify
 open source libraries to provide metadata on those libraries such as
-known vulnerabilities. 
+known vulnerabilities.
 
 [id="quay-security-scan_{context}"]
 == Scanning OpenShift images
 
 For the container images that are running in {product-title}
 and are pulled from Red Hat Quay registries, you can use an Operator to list the
 vulnerabilities of those images. The
-link:https://access.redhat.com/documentation/en-us/red_hat_quay/3/html-single/manage_red_hat_quay/index#container-security-operator-setup[Container Security Operator]
+link:https://access.redhat.com/documentation/en-us/red_hat_quay/3/html-single/manage_red_hat_quay/index#container-security-operator-setup[{rhq-cso}]
 can be added to {product-title} to provide vulnerability reporting
 for images added to selected namespaces.
 
@@ -31,4 +31,3 @@ link:https://access.redhat.com/documentation/en-us/red_hat_quay/3/html-single/ma
 In Red Hat Quay, Clair can search for and report vulnerabilities in
 images built from {op-system-base}, CentOS, Oracle, Alpine, Debian, and Ubuntu
 operating system software.
-

modules/security-pod-scan-cso.adoc

@@ -4,9 +4,9 @@
 
 :_content-type: PROCEDURE
 [id="security-pod-scan-cso_{context}"]
-= Running the Container Security Operator
+= Running the {rhq-cso}
 
-You can start the Container Security Operator from the {product-title}
+You can start the {rhq-cso} from the {product-title}
 web console by selecting and installing that Operator from the Operator Hub,
 as described here.
 

modules/security-pod-scan-query-cli.adoc

@@ -6,10 +6,10 @@
 [id="security-pod-scan-query-cli_{context}"]
 = Querying image vulnerabilities from the CLI
 Using the `oc` command, you can display information about
-vulnerabilities detected by the Container Security Operator.
+vulnerabilities detected by the {rhq-cso}.
 
 .Prerequisites
-* Be running the Container Security Operator on your
+* Be running the {rhq-cso} on your
 {product-title} instance
 
 .Procedure

modules/security-registries-quay.adoc

@@ -42,6 +42,6 @@ Ongoing integration of Red Hat Quay with {product-title} continues,
 with several {product-title} Operators of particular interest.
 The link:https://access.redhat.com/documentation/en-us/red_hat_quay/3/html-single/manage_red_hat_quay/index#quay-bridge-operator[Quay Bridge Operator]
 lets you replace the internal {product-title} registry with Red Hat Quay.
-The link:https://access.redhat.com/documentation/en-us/red_hat_quay/3/html-single/manage_red_hat_quay/index#container-security-operator-setup[Quay Container Security Operator]
+The link:https://access.redhat.com/documentation/en-us/red_hat_quay/3/html-single/manage_red_hat_quay/index#container-security-operator-setup[{rhq-cso}]
 lets you check vulnerabilities of images running in {product-title} that were
 pulled from Red Hat Quay registries.

security/index.adoc

@@ -65,7 +65,7 @@ You can xref:../security/encrypting-etcd.adoc#encrypting-etcd[enable etcd encryp
 [id="vulnerability-scanning"]
 === Vulnerability scanning
 
-Administrators can use the Container Security Operator (CSO) to run xref:../security/pod-vulnerability-scan.adoc#pod-vulnerability-scan[vulnerability scans] and review information about detected vulnerabilities.
+Administrators can use the {rhq-cso} to run xref:../security/pod-vulnerability-scan.adoc#pod-vulnerability-scan[vulnerability scans] and review information about detected vulnerabilities.
 
 [id="compliance-overview"]
 == Compliance overview

security/pod-vulnerability-scan.adoc

@@ -6,7 +6,7 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
-Using the Container Security Operator (CSO), you can access vulnerability
+Using the {rhq-cso}, you can access vulnerability
 scan results from the {product-title} web console for container images
 used in active pods on the cluster. The CSO: