On the Frameworks or Controls page, you can designate a Framework Requirement or Control as N/A.
Mark a Framework Requirement (FR) as N/A:
Option 1: From the Frameworks page,
locate the FR and click the 3 dots icon on its row.
Select Mark as not applicable.
Option 2: From within the requirement
On the Frameworks page, click into a specific framework requirement.
Click the Mark requirement as NA button.
Note: Marking a framework requirement as N/A stops exclusively mapped controls and tests from counting toward that framework. Those controls do not move to Inactive as Not Applicable unless you also mark the control itself as N/A.
Mark a Control as N/A
On the Frameworks page, click into a specific framework requirement.
Click the Mark requirement as NA button to mark a control as N/A:
On the Frameworks or Controls page, click the 3 dots on the line of the control.
Select Mark as not applicable.
Or:
On the Frameworks or Controls page, click on a specific control.
Click the Mark control as NA button.
Frequently Asked Questions
Why is my test marked Not Applicable or N/A by Secureframe?
One scenario would be that the Test in question has no mapped Controls, which we call an Unmapped Control State. A new " Unmapped" state more clearly show what controls are actively being used in your implemented control set. Controls that are not mapped to at least one active framework requirement will now show as "Unmapped" in the Inactive tab of this page.
I marked a framework requirement as N/A. Why are related controls still under Implemented?
Marking the requirement N/A makes exclusively mapped controls and tests stop counting toward that framework. They can show as unmapped or no tests mapped.
They only move to Inactive as Not Applicable when you explicitly mark the control N/A. Those are two different actions.