EvidenceSheet

RA-9 Criticality analysis

Requires critical system components and functions to be identified through a criticality analysis of organization-defined systems, components or services, performed at organization-defined decision points in the system d

4
artefacts
0
held by a system
2
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

  • Evidence the analysis informs protection and supply chain decisions · Policy repository / GRC workspace
  • Update records when architecture or dependencies changed · Cloud console / configuration management

governing documentDocuments that govern the control

  • Criticality analysis results identifying critical components and functions · Policy repository / GRC workspace
  • Documented decision points in the life cycle at which the analysis is performed · 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

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 sheet

RA-8 Privacy Impact Assessments. Conduct privacy impact assessments for systems, programs, or other activities before: Developing or procuring information technology that processes personally identifiable information; and Initiating a new collection of personally identifiable information that: · RA-10 Threat hunting