Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

Configuration Compliance correlation

Log in to subscribe to topics and get notified when content changes.

Configuration Compliance correlation

Configuration Compliance provides prioritization and test result grouping to aid remediation of non-compliance issues.

Asset-Centric Prioritization

Configuration scans can produce large number of findings. Prioritize findings for greatest risk reduction. Priority includes both configuration test criticality and asset criticality. Configuration test result priority is expressed as a 0–100 scale risk score. Calculator groups compute risk score and can be customized.

When the third-party import is complete, Configuration Compliance sends an event to indicate end-of-import actions. For every active result group, the following actions are taken:
  • Resolved groups with failed results return to the Awaiting implementation state.
  • Groups where all results passed are Closed.
  • The state of test results that are in active groups is updated.
  • The flag indicating whether a result is part of an active group is updated.

Test Result Groups order of precedence

When test results belong to more than one group, the State of a test result is derived according to an order of precedence.

The State and Resolution fields in the Configuration Test form and the Result field in the Test Result form, are calculated following this order of precedence.


The group membership precedence only applies to items where the item did not pass the configuration test. Passed items are always in the Closed-Fixed state.

The Result value determines the state. We ignore groups in the Closed-Fixed and Closed-Canceled state. The item state is computed from the states of all other test result groups it belongs to or is set to Open, if no other group exists for the item.

Test result group order of precedence

Test Result Groups creation

Configuration Compliance Test Result Groups are created manually.

There are two ways to create and populate Test Result Groups.

  • From the Test Results Groups module and using filters that automatically populate the Test Results tab.

    This way is good for when you know what filtering you want to use. For example, capturing all failed test results that are moderate and higher criticality, affect the windows-based infrastructure, and apply only to the SAP supply chain application.

  • By selecting test results in the Test Results list and creating a group from the Actions on selected rows... menu.

    This method is good for results that are not easily filtered, or situations where you want to specify test results for remediation. For example, outliers that have nothing in common.

Note: If you create a group from the Test Results list and you later decide to use a filter for that group, your original entries are removed and replaced by the filter results.

Ungrouped Test Results

Ungrouped Test Results contain all non-pass test results that are not members of an active (non-Closed) group. This module is updated after every import and whenever test results are added or removed from a group.