164.308(a)(7)(ii)(D) Testing and Revision Procedures (Addressable)
Implement procedures for periodic testing and revision of contingency plans. NIST recommends annual tabletop, biennial functional, and post-incident lessons-learned updates.
4
artefacts
0
held by a system
1
at each review
hard
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Test reports · Policy repository / GRC workspace
governing documentDocuments that govern the control
- Test schedule · Policy repository / GRC workspace
- After-action reports · Policy repository / GRC workspace
- Plan revision history · Policy repository / GRC workspace
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- Plans untested for years
- Lessons learned never folded into plan
- Test scope too narrow
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheet164.308(a)(7)(ii)(C) Emergency Mode Operation Plan (Required) · 164.308(a)(7)(ii)(E) Applications and Data Criticality Analysis (Addressable)