Updates to docs for RHCOS scanning with Scanner V4

Author: kcarmichael08

modules/rhcos-analyse-detect.adoc

@@ -11,3 +11,4 @@ The Compliance container was already a part of earlier {product-title-short} ver
 However, the Node-inventory container is new with {product-title-short} 4.0 and works only with {ocp} cluster nodes.
 
 Upon start-up, the Compliance and Node-inventory containers begin the first inventory scan of {op-system-first} software components within five minutes. Next, the Node-inventory container scans the node's file system to identify installed RPM packages and report on {op-system} software components. Afterward, inventory scanning occurs at periodic intervals, typically every four hours. You can customize the default interval by configuring the ROX_NODE_SCANNING_INTERVAL environment variable for the Compliance container.
+//needs updating for 4.6?

modules/rhcos-enable-node-scan-scannerv4.adoc

@@ -0,0 +1,19 @@
+// Module included in the following assemblies:
+//
+// * operating/manage-vulnerabilities/scan-rhcos-node-host.adoc
+// * cloud_service/upgrading-cloud/upgrade-cloudsvc-roxctl.adoc
+:_mod-docs-content-type: PROCEDURE
+[id="rhcos-enable-node-scan-scannerv4_{context}"]
+= Enabling {op-system} node scanning with Scanner V4
+
+[role="_abstract"]
+If you use {ocp}, you can enable scanning of {op-system-first} nodes for vulnerabilities by using {rh-rhacs-first}.
+
+:FeatureName: RHCOS node scanning with Scanner V4
+include::snippets/technology-preview.adoc[]
+
+.Prerequisites
+* For scanning {op-system} node hosts of the secured cluster, you must have installed Secured Cluster services on {ocp} {ocp-supported-version} or later. For information about supported platforms and architecture, see the link:https://access.redhat.com/articles/7045053[{product-title} Support Matrix]. For life cycle support information for {product-title-short}, see the link:https://access.redhat.com/support/policy/updates/rhacs[{product-title} Support Policy].
+//what action does user have to take to enable Scanner V4 for node scanning?
+
+.Procedure

modules/rhcos-enable-node-scan.adoc

@@ -4,13 +4,13 @@
 // * cloud_service/upgrading-cloud/upgrade-cloudsvc-roxctl.adoc
 :_mod-docs-content-type: PROCEDURE
 [id="rhcos-enable-node-scan_{context}"]
-= Enabling {op-system} node scanning
+= Enabling {op-system} node scanning with the StackRox Scanner
 
 [role="_abstract"]
 If you use {ocp}, you can enable scanning of {op-system-first} nodes for vulnerabilities by using {rh-rhacs-first}.
 
 .Prerequisites
-* For scanning {op-system} node hosts of the Secured cluster, you must have installed Secured cluster on {ocp} {ocp-supported-version} or later. For information about supported platforms and architecture, see the link:https://access.redhat.com/articles/7045053[{product-title} Support Matrix]. For life cycle support information for {product-title-short}, see the link:https://access.redhat.com/support/policy/updates/rhacs[{product-title} Support Policy].
+* For scanning {op-system} node hosts of the secured cluster, you must have installed Secured Cluster services on {ocp} {ocp-supported-version} or later. For information about supported platforms and architecture, see the link:https://access.redhat.com/articles/7045053[{product-title} Support Matrix]. For life cycle support information for {product-title-short}, see the link:https://access.redhat.com/support/policy/updates/rhacs[{product-title} Support Policy].
 
 .Procedure
 . Run one of the following commands to update the compliance container.

modules/rhcos-environment-variables.adoc

@@ -8,6 +8,8 @@
 [role="_abstract"]
 You can use the following environment variables to configure {op-system} node scanning on {product-title-short}.
 
+//needs updating for 4.6 with new variables?
+
 .Node-inventory configuration
 [options="header", cols="1m,2"]
 |====

modules/rhcos-match-vulnerability.adoc

@@ -9,3 +9,4 @@
 Central services, which include Central and Scanner, perform vulnerability matching. Scanner uses Red{nbsp}Hat's Open Vulnerability and Assessment Language (OVAL) v2 security data streams to match vulnerabilities on {op-system-first} software components.
 
 Unlike the earlier versions, {product-title-short} 4.0 no longer uses the Kubernetes node metadata to find the kernel and container runtime versions. Instead, it uses the installed {op-system} RPMs to assess that information.
+//changes made in https://github.com/openshift/openshift-docs/pull/83406 for 4.6

operating/manage-vulnerabilities/scan-rhcos-node-host.adoc

@@ -7,9 +7,11 @@ include::modules/common-attributes.adoc[]
 toc::[]
 
 [role="_abstract"]
-For {ocp}, {op-system-first} is the only supported operating system for control plane. Whereas, for node hosts, {ocp} supports both {op-system} and {op-system-base-full}.
+For {ocp}, {op-system-first} is the only supported operating system for control plane. For node hosts, {ocp} supports both {op-system} and {op-system-base-full}.
 With {rh-rhacs-first}, you can scan {op-system} nodes for vulnerabilities and detect potential security threats.
 
+//Any changes needed for 4.6 Scanner V4 for RHCOS nodes?
+
 {product-title-short} scans {op-system} RPMs installed on the node host, as part of the {op-system} installation, for any known vulnerabilities.
 
 First, {product-title-short} analyzes and detects {op-system} components. Then it matches vulnerabilities for identified components by using {op-system-base} and OpenShift 4.X Open Vulnerability and Assessment Language (OVAL) v2 security data streams.
@@ -25,6 +27,8 @@ First, {product-title-short} analyzes and detects {op-system} components. Then i
 
 include::modules/rhcos-enable-node-scan.adoc[leveloffset=+1]
 
+include::modules/rhcos-enable-node-scan-scannerv4.adoc[leveloffset=+1]
+
 include::modules/rhcos-analyse-detect.adoc[leveloffset=+1]
 
 include::modules/rhcos-match-vulnerability.adoc[leveloffset=+1]