HERE'S WHY
Readiness provides an at-a-glance assessment of the status of each framework and is the active tracking and validity check for all in-scope framework requirements and controls.
BEFORE DIVING IN
Readiness applies to Frameworks, Requirements, and Controls, with the readiness of one dependent on the other.
HERE'S HOW
A Framework's readiness is measured on the 'Dratameter' and is calculated in one of two ways:
Controls - by the number of in scope Controls that are 'Ready' out of the total number of in scope Controls
Requirements - by the number of in scope Requirements that are 'Ready' out of the total number of in scope Requirements
At the top of the Frameworks page there is a toggle that allows you to choose whether to measure framework readiness by Controls (default setting) or Requirements.
Setting the toggle here impacts the readiness calculation for ALL frameworks and will be evident on this page, as well as individual framework pages, and the Dashboard. To change the readiness calculation, simply return to the Frameworks page and switch the toggle.
What gets updated on each impacted page?
On the Frameworks page, all Dratameters and associated data points will update based on the setting.
On individual framework pages, the Dratameter and data points on the top of the page will update based on the setting.
On the Dashboard, the data in the Readiness Overview section will update based on the setting.
Each user with access to the Frameworks page can toggle between Controls and Requirements at any time. Their setting is saved at the individual user level.
How is readiness calculated?
A Requirement is considered 'Ready' if all the controls it’s mapped to are ready
Examples:
If a requirement is mapped to two controls, one is ready and one is not, the requirement will not be ready
If a requirement is not mapped to any controls, it is not ready
If a requirement is mapped to multiple controls and all controls are ready, then the requirement is ready
You can filter requirements by their readiness status on a framework page—'Ready' or 'Not Ready'—to gauge what needs your attention. The filter on the left will always apply to Requirement readiness.
A Control is considered 'Ready' if:
All mapped evidence is valid
It is not mapped to any invalid evidence
Valid evidence is any of the following:
Test in PASSING state
All mapped Policies have a published version
Mapped Evidence Library artifact that has not exceeded its renewal date
Mapped Miscellaneous Evidence (file or URL) that has not exceeded its renewal date
Invalid evidence is any of the following:
Test in a FAILING state
Mapped Policy that is not published
Mapped Evidence Library artifact that has exceeded its renewal date
Mapped Miscellaneous Evidence that has exceeded its renewal date
Additionally, if a control is not mapped to any evidence at all, it is not ready.
On the Controls page you can filter controls by their readiness status—'Ready' or 'Not Ready'—to gauge which controls need your attention.