RA-2 Security Categorization
Categorizes systems in a way that carries through to the criticality of the components and suppliers they depend on.
3
artefacts
0
held by a system
2
at each review
hard
to go live
Document repository
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
- Categorization records · Document repository
- Review on change · Document repository
governing documentDocuments that govern the control
- Linkage from system category to component and supplier criticality · Vendor register / contract repository
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
- categorization stops at the system and never reaches its dependencies
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