Frameworks, controls & tests
Review linked framework coverage
Inspect the exact requirements a control supports and the test contributions available for them.
Before you start
Who this is for: Compliance operators, control owners, and scoped reviewers.
- Have access to the control and relevant framework.
- Interpret coverage within the organization's selected scope and your visible access.
Follow these steps
Open the control's Frameworks section
Find the control in Controls, open its full detail, and select Frameworks. Review each requirement's identifier, name, framework, and version. The list documents explicit relationships; it should be the starting point for a coverage discussion.
Read the requirement in context
Follow a framework link to understand the corresponding organizational scope. Where the control shows Statement of Applicability decisions, read the applicability rationale and status, including any pending override. An old snapshot or pending decision should not be reported as a newly approved scope change.
Inspect test contributions
Open Tests on the control and review the mapped test contributions and any supplemental requirements shown. Open individual tests to inspect their rule, source, and result. A test can contribute evidence to a control without proving every part of every linked requirement.
Identify the remaining work
Review Documents, Evidence, linked tasks, and the displayed Next action. Record which requirement lacks support and coordinate the specific implementation or evidence task. Keep the underlying requirement separate from an operational test failure and from a pending document review.
What you should see
You can explain which requirements are linked and which supporting work remains visible in the control.
If something doesn’t look right
A framework or mapping is missing
Confirm the active organization, enabled framework, and your access scope. Ask the program owner to review the intended mapping.
Counts differ across pages
Check filters, scope, and the kind of item being counted. Requirements, controls, tests, and evidence versions are different units.
A percentage looks complete
Review the linked records and current decisions. A displayed progress measure is not an audit opinion or certification guarantee.
Still need a little help?
Ask the assistant about these steps, or tell our team where you got stuck.
Contact support