Skip to main content

A main control shows as healthy when the related scope assigned controls are unhealthy

What to check if your main control is healthy and you expect it to be unhealthy because the related scope assigned controls are unhealthy.

Taylor Marchman avatar
Written by Taylor Marchman
Updated over 3 months ago

Control health is an important way to monitor your compliance operation status in Hyperproof. Many factors contribute to control health including implementation, testing, and freshness. The health of controls with related scope assigned controls, can be affected by the status of the scope controls based on the configuration of your organization's health rules.

If you experience a situation where the main control health status is Healthy, but the related scope assigned controls are unhealthy, check the configuration of the health rules for scope controls.

  1. From the left menu, select Settings.

  2. From the Settings menu, select Health.

  3. Select the Control with scope assignments tab.

  4. Review and change the rules for how scope controls health affects the health of the main control.

The default configuration is:

  • if any scope assigned control is critical, the main control is critical

  • if any scope assigned control is at risk, the main control is at risk

  • otherwise the main control is healthy

If your health rules are different than this, it might cause unexpected results. In the example below, the rule for how scope assigned controls with a Critical health status affect the main control has been modified. In the example below, the rule indicates that more than 2 scope assignments must be Critical before the main control is set to Critical. If you expect that any critical scope control should make the main control critical, update the rule to match the default settings shown in the screenshot above.


You can configure the health rules to meet your requirements, but you should be aware of the repercussions. We have seen users question the health calculation only to find that the configuration had been changed from the default settings causing unexpected results.

You can read more about control health in this article.



REF 000001355



Did this answer your question?