Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Modifying out-of-the-box component templates

During the installation of Compliance Content libraries, groups of out-of-the-box component templates are saved in BMC Server Automation. These templates contain compliance rules for regulatory standards and best practice policies (HIPAA, PCI, SOX, DISA, and CIS), and were designed specifically for analyzing compliance with these policies.

For a full list of Compliance Content component templates, see Overview-of-Compliance-Content-add-ons.

If necessary, you can modify and refine the Compliance Content component templates to suit your unique needs. For procedures for editing and modifying component templates, see Editing-a-component-template.

When editing these templates, note their special characteristics:

  • On the General tab of all Compliance Content component templates, only the Discover and Compliance operations are allowed. Remediation of compliance results is also allowed, but not auto-remediation.
  • On the Discover tab, the signature is designed to discover components that run a specific operating system and sometimes a specific OS version.
  • Multiple compliance rules are grouped together in rule groups on the Compliance tab. Reference numbers for these rule groups and rules follow a decimal (or scientific) numbering system, to enable easy navigation of the rules. You can open any rule to view its description on the General tab in the Rule Editor. Some rules include remediation options on the Remediation tab in the Rule Editor. The rule itself appears on the Rule Definition tab in the Rule Editor, and should be modified only by expert users who are highly proficient in both the regulatory standard or policy and in the task of defining compliance rules.

    For full instructions on defining or modifying compliance rules, see Adding-or-editing-a-compliance-rule.

Note

After you edit the component templates and tailor them to your needs, you might want to export them from one BMC Server Automation system and import them to multiple other BMC Server Automation systems. For information about exporting and importing BMC Server Automation objects, see Import-and-export-concepts.

To successfully use the imported component templates, note the following limitations in the export and import of Compliance Content:

  • The batch-type Scale Jobs provided by BMC Server Automation Compliance Content are not exported and imported along with the component templates. You must export and import them separately.
  • The following directories, which contain NSH scripts used by the compliance rules, must be copied manually to the target BMC Server Automation systems:
    • appserverInstallDirectory/share/sensors on the Application Server
    • appserverInstallDirectory/storage/extended_objects on the file server

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*