RA-2 Security categorization
Requires the system and the information it processes, stores and transmits to be categorized, the categorization result and its rationale to be documented in the security plan, and the authorizing official or their repre
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
- Approval evidence from the authorizing official or designated representative · Policy repository / GRC workspace
governing documentDocuments that govern the control
- Security categorization determination with supporting rationale · Policy repository / GRC workspace
- Information type inventory used to derive the categorization · Policy repository / GRC workspace
- Security plan section holding the recorded categorization · 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
- Categorization asserted with no rationale or information type analysis behind it
- Never reviewed after the system began handling more sensitive information
- Approved by the system owner rather than the authorizing official
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 sheetRA-1 Policy and procedures for risk assessment · RA-3 Risk assessment