The Compliance page shows how your active policies align with industry standards. Each framework is broken down into individual controls, and each control links to the policies that satisfy it — and any open findings that violate it.
- •Compliance is read-only — you manage coverage by launching or adjusting policies on the Management page
- •Scores update automatically as policies are launched, findings are resolved, or new resources are detected
- •A control is compliant only when its mapped policy is active and has zero open findings for the resources in scope
Each framework displays a compliance score (0–100 %) calculated as:
A control is counted as compliant when:
- The mapped policy is active (launched), and
- There are no ACTIVE findings for that policy
A control is non-compliant when the policy is active but has open findings. A control is not monitored when the policy hasn't been launched yet.
| Control State | Meaning |
|---|---|
| Compliant | Policy active, zero open findings |
| Non-Compliant | Policy active, one or more open findings |
| Not Monitored | Policy not yet launched |
The Compliance page shows a card for each framework with its score gauge, total controls, and open finding count. Click a framework card to drill into its controls.
Each framework detail page lists all controls with their state, associated policy, service, and finding count. Use the state filter tabs (All / Compliant / Non-Compliant / Not Monitored) to focus on what needs attention.
Clicking a finding count on a control row navigates to the Findings page filtered by that policy — so you can immediately see what's causing the non-compliance.
Coverage is driven by policies
- 1Open the framework detail page and filter by Not Monitored
- 2Note the policies associated with unmonitored controls
- 3Go to Management and launch those policies with appropriate scope
- 4Review open findings for non-compliant controls and remediate the underlying resources