Customizing compliance results
You must have the Comply Report Content Administrator role to customize compliance results. For more information about Comply roles, see User role requirements.
A profile defines a set of rules to be evaluated and the parameters for those rules. Custom profiles allow you to specify just a subset of the checks available in a benchmark to be deployed.
You can either create a custom profile or upload one from a tailoring file.
Create a new custom profile
- Click Create Profile.
- On the New Custom Profile page, enter a Title and Description.
- In the Rules section, select a benchmark from the Benchmark drop-down list.
- Select each rule you would like to include in your custom profile.
- Click Add Selection To Profile to move the selected rules to the Selected Rules section. You can click Remove Selection From Profile to remove any rules you have added.
- Click Create to create the new custom profile.
You can also modify some rule values within your custom profile. If a rule value is customizable, a value of true displays in the Can Customize column along with the default value for the rule in the Default Values column.
Customize a rule value
- Select the rule and click Modify Rule Value.
- In the Modify Custom Profile Value window, enter a Custom Rule Title and change the Custom value field.
- Click Save. The new value will appear in the User-defined Values column. You can return to the Default Value of a rule by clicking Use Default.
Rule titles occasionally include the value used in the rule. Customize the title of rules for which values have been changed. The customized rule titles will then show up in report results, question answers, and report exports. For example, If you provide a new value for the rule (L1) Ensure 'Enforce password history' is set to '24 or more password(s)', you can change 24 to match the custom value.
Upload a new custom profile
- Click Import Tailoring File.
- In the Upload Custom Profile window, enter a Description.
- Select a benchmark from the Benchmark drop-down list.
- Click Select File and locate the tailoring file for the new profile.
A custom profile can also be specified with a tailoring file. For more information about tailoring files, see NIST's Technical Specification for the Security Content Automation Protocol (SCAP) or consult with your TAM.
Cloning custom profiles
- Click Clone next to the custom profile.
- Provide a new Title and Description for the duplicate custom profile.
- Make any necessary changes to the rules included in the custom profile.
- Click Create.
Editing custom profiles
- Click Edit next to the custom profile.
- In the Details section, you can edit the Title and Description.
- In the Rules section, choose additional rules or select a new benchmark from the Benchmark drop-down list to select other rules.
- Click Update.
- If any of the selected rules are invalid, a confirmation window appears that invalid rules will automatically be removed from the custom profile. Click OK.
- If one or more reports currently use this custom profile, a confirmation window appears. If you want to redeploy these reports immediately, click Redeploy and Continue; otherwise, click Continue. Reports with changes that are not redeployed will show a Warning next to them on the Reports page.
If you choose to select a new benchmark, previously selected rules might no longer be valid. If a rule is invalid, No will be displayed as the value in the Valid column of the Selected Rules list. A warning also appears below the list indicating the total number of invalid rules that have been selected.
You can create custom checks in Comply to check a condition on endpoints that might not be included in any benchmark. A custom check can be either PowerShell or VBScript on Windows and bash shell scripts on Linux/macOS. PowerShell scripts should use the file extension .ps1, and VBScript files should use the .vbs extension.
You must have the Comply Custom Check Writer role to write custom checks. For more information about Comply roles, see User role requirements.
- At the top right of the Home page, click Settings .
- On the Compliance tab, click Custom Checks.
- Click Create Check.
- In the New Custom Check window, enter a Title, Description, and Identifier.
- Select the appropriate Severity and Platform.
- Click Select File and locate the file for the custom check.
- Click Save. Your custom check will now show under Custom Checks and be available in the Custom Checks section of the page when you create a new Configuration Compliance report.
The result of a custom check is indicated by the last line of output from the custom check. This value should appear on a line by itself after all other output and should return one of the following results:
|pass||All conditions are satisfied.|
|fail||All conditions are not satisfied.|
|error||Compliance evaluation could not be completed; therefore, the status of the endpoint(s) compliance has not been confirmed.|
|unknown||The result is unknown.|
Use custom ID mappings to create a custom column on results that associates a specific tag with a custom check or rule identifier.
- At the top right of the Home page, click Settings .
- On the Compliance tab, click Custom ID Mappings.
- Click Create Custom ID.
- In the New Custom ID window, enter a Name and Description.
- Click Select File and locate the custom ID mapping file.
- Click Save. Your custom ID will now show under Custom ID Mappings and be available in the Advanced Settings section when you create a new Configuration Compliance report.
Use the following file format for a custom ID mapping: Rule id|custom id
A report can only have a single custom ID mapping associated with it; however, it can have multiple benchmarks and custom checks. When selecting the benchmarks and custom checks, be aware that a report is targeted to a single action group.
- Obtain the hash for the custom ID for a report by clicking on the report name on the Configuration Compliance Reports page and expanding More Details. You can click Copy to copy the hash.
- In Interact, ask the question that matches the engine type such as Get Comply - CIS-CAT Results from all machines and paste the hash in the Comply bundle hash field.
Use the appropriate Comply sensor for the engine type:
- Comply - CIS-CAT Results
- Comply - JovalCM Results
- Comply - SCC Results
In order to view, edit, or reuse a custom check or ID mapping, you can export it.
Select a custom check or custom ID and click export .
Last updated: 9/17/2019 1:58 PM | Feedback