Merge pull request #64016 from sheriff-rh/OCPBUGS-18279

Author: sheriff-rh

modules/compliance-new-tailored-profiles.adoc

@@ -6,15 +6,15 @@
 [id="compliance-new-tailored-profiles_{context}"]
 = Creating a new tailored profile
 
-You can write a tailored profile from scratch using the `TailoredProfile` object. Set an appropriate `title` and `description` and leave the `extends` field empty. Indicate to the Compliance Operator what type of scan will this custom profile generate:
+You can write a tailored profile from scratch by using the `TailoredProfile` object. Set an appropriate `title` and `description` and leave the `extends` field empty. Indicate to the Compliance Operator what type of scan this custom profile will generate:
 
 * Node scan: Scans the Operating System.
-* Platform scan: Scans the OpenShift configuration.
+* Platform scan: Scans the {product-title} configuration.
 
 .Procedure
 
-Set the following annotation on the `TailoredProfile` object:
-+
+* Set the following annotation on the `TailoredProfile` object:
+
 .Example `new-profile.yaml`
 [source,yaml]
 ----
@@ -25,13 +25,20 @@ metadata:
   annotations:
     compliance.openshift.io/product-type: Node <1>
 spec:
-  extends:
-  description: My custom profile <2>
-  title: Custom profile <3>
+  extends: ocp4-cis-node <2>
+  description: My custom profile <3>
+  title: Custom profile <4>
+  enableRules:
+    - name: ocp4-etcd-unique-ca
+      rationale: We really need to enable this
+  disableRules:
+    - name: ocp4-file-groupowner-cni-conf
+      rationale: This does not apply to the cluster
 ----
 <1> Set `Node` or `Platform` accordingly.
-<2> Use the `description` field to describe the function of the new `TailoredProfile` object.
-<3> Give your `TailoredProfile` object a title with the `title` field.
+<2> The `extends` field is optional.
+<3> Use the `description` field to describe the function of the new `TailoredProfile` object.
+<4> Give your `TailoredProfile` object a title with the `title` field.
 +
 [NOTE]
 ====