CMP-4011: Document Custom OpenShift Compliance Scans using Compliance Operator CEL

Author: GroceryBoyJr

security/compliance_operator/co-overview.adoc

@@ -54,6 +54,8 @@ xref:../../security/compliance_operator/co-scans/compliance-operator-remediation
 
 xref:../../security/compliance_operator/co-scans/compliance-operator-advanced.adoc#compliance-operator-advanced[Performing advanced Compliance Operator tasks]
 
+xref:../../security/compliance_operator/co-scans/compliance-operator-customrules.adoc#compliance-operator-customrules[Compliance Operator Custom Rules]
+
 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]

security/compliance_operator/co-scans/compliance-operator-customrules.adoc

@@ -0,0 +1,19 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="compliance-operator-customrules_{context}"]
+= Defining CustomRules using the Compliance Operator
+include::_attributes/common-attributes.adoc[]
+:context: compliance-customrules
+
+toc::[]
+
+[role="_abstract"]
+OpenShift Compliance Operator includes a `CustomRule` Custom Resource Definition (CRD) that can create custom compliance checks using Common Expression Language (CEL). This allows Compliance Operator users to create custom scan rules that may not be provided by standardized security profiles. An example shows how to use a `CustomRule` to enforce security checks for `ClusterLogForwarder` resources, ensuring that log data is transmitted securely.
+
+====
+[NOTE]
+For more information on the Kubernetes Common Expression Language (CEL), refer to link:https://kubernetes.io/docs/reference/using-api/cel/[Common Expression Language in Kubernetes]. For production deployments, always test `CustomRule` resources in non-production environments first and follow your organization's change management procedures when deploying `CustomRule` resources.
+====
+
+include::modules/compliance-new-tailored-profiles.adoc[leveloffset=+1]
+
+include::modules/compliance-tailored-profiles.adoc[leveloffset=+1]