While the Compliance Operator comes with ready-to-use profiles, they must be modified to fit the organizations’ needs and requirements. The process of modifying a profile is called tailoring.

The Compliance Operator provides the TailoredProfile object to help tailor profiles.

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:

  • Node scan: Scans the Operating System.

  • Platform scan: Scans the OpenShift configuration.


Set the following annotation on the TailoredProfile object:

+ .Example new-profile.yaml

apiVersion: compliance.openshift.io/v1alpha1
kind: TailoredProfile
  name: new-profile
    compliance.openshift.io/product-type: Node (1)
  description: My custom profile (2)
  title: Custom profile (3)
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.

Adding the -node suffix to the name field of the TailoredProfile object is similar to adding the Node product type annotation and generates an Operating System scan.

Using tailored profiles to extend existing ProfileBundles

While the TailoredProfile CR enables the most common tailoring operations, the XCCDF standard allows even more flexibility in tailoring OpenSCAP profiles. In addition, if your organization has been using OpenScap previously, you may have an existing XCCDF tailoring file and can reuse it.

The ComplianceSuite object contains an optional TailoringConfigMap attribute that you can point to a custom tailoring file. The value of the TailoringConfigMap attribute is a name of a config map, which must contain a key called tailoring.xml and the value of this key is the tailoring contents.

  1. Browse the available rules for the Red Hat Enterprise Linux CoreOS (RHCOS) ProfileBundle:

    $ oc get rules.compliance -n openshift-compliance -l compliance.openshift.io/profile-bundle=rhcos4
  2. Browse the available variables in the same ProfileBundle:

    $ oc get variables.compliance -n openshift-compliance -l compliance.openshift.io/profile-bundle=rhcos4
  3. Create a tailored profile named nist-moderate-modified:

    1. Choose which rules you want to add to the nist-moderate-modified tailored profile. This example extends the rhcos4-moderate profile by disabling two rules and changing one value. Use the rationale value to describe why these changes were made:

      Example new-profile-node.yaml
      apiVersion: compliance.openshift.io/v1alpha1
      kind: TailoredProfile
        name: nist-moderate-modified
        extends: rhcos4-moderate
        description: NIST moderate profile
        title: My modified NIST moderate profile
        - name: rhcos4-file-permissions-var-log-messages
          rationale: The file contains logs of error messages in the system
        - name: rhcos4-account-disable-post-pw-expiration
          rationale: No need to check this as it comes from the IdP
        - name: rhcos4-var-selinux-state
          rationale: Organizational requirements
          value: permissive
      Table 1. Attributes for spec variables
      Attribute Description


      Name of the Profile object upon which this TailoredProfile is built.


      Human-readable title of the TailoredProfile.


      A list of name and rationale pairs. Each name refers to a name of a rule object that is to be disabled. The rationale value is human-readable text describing why the rule is disabled.


      A list of name and rationale pairs. When a manual rule is added, the check result status will always be manual and remediation will not be generated. This attribute is automatic and by default has no values when set as a manual rule.


      A list of name and rationale pairs. Each name refers to a name of a rule object that is to be enabled. The rationale value is human-readable text describing why the rule is enabled.


      Human-readable text describing the TailoredProfile.


      A list of name, rationale, and value groupings. Each name refers to a name of the value set. The rationale is human-readable text describing the set. The value is the actual setting.

    2. Add the tailoredProfile.spec.manualRules attribute:

      Example tailoredProfile.spec.manualRules.yaml
      apiVersion: compliance.openshift.io/v1alpha1
      kind: TailoredProfile
        name: ocp4-manual-scc-check
        extends: ocp4-cis
        description: This profile extends ocp4-cis by forcing the SCC check to always return MANUAL
        title: OCP4 CIS profile with manual SCC check
          - name: ocp4-scc-limit-container-allowed-capabilities
            rationale: We use third party software that installs its own SCC with extra privileges
    3. Create the TailoredProfile object:

      $ oc create -n openshift-compliance -f new-profile-node.yaml (1)
      1 The TailoredProfile object is created in the default openshift-compliance namespace.
      Example output
      tailoredprofile.compliance.openshift.io/nist-moderate-modified created
  4. Define the ScanSettingBinding object to bind the new nist-moderate-modified tailored profile to the default ScanSetting object.

    Example new-scansettingbinding.yaml
    apiVersion: compliance.openshift.io/v1alpha1
    kind: ScanSettingBinding
      name: nist-moderate-modified
      - apiGroup: compliance.openshift.io/v1alpha1
        kind: Profile
        name: ocp4-moderate
      - apiGroup: compliance.openshift.io/v1alpha1
        kind: TailoredProfile
        name: nist-moderate-modified
      apiGroup: compliance.openshift.io/v1alpha1
      kind: ScanSetting
      name: default
  5. Create the ScanSettingBinding object:

    $ oc create -n openshift-compliance -f new-scansettingbinding.yaml
    Example output
    scansettingbinding.compliance.openshift.io/nist-moderate-modified created