Control health
By default, Hyperproof calculates control health based on the following rules:
Tip
For more information, see the Control health video at the bottom of the page.
Hyperproof assigns the status of critical if testing proves ineffective and if the implementation status is set to unknown, not started, or in progress.
If testing is set to not tested or in progress, the control is considered at risk. The control is also considered at risk if the freshness is unknown or expired, and if the control contains no proof.
For a control to be deemed healthy, using the default health calculation, testing on a control must be effective, implementation must be completed, it must be fresh, and there must be at least one piece of proof attached to it.
Control health with scope assignments
Hyperproof calculates the health of controls with scopes linked to them as follows:
Exampled scenario
Three scopes are linked to a control in your program: Subsidiary, Region, and Software. For that control to be considered healthy, all three must be healthy. That means that each scope must prove that testing is effective, implementation is completed, the control is fresh, and at least one piece of proof is attached.
Control health
Watch this short video to learn more about control health.