RA-2 Security Categorization
Categorize system per FIPS 199; document; review and update annually.
Source: FedRAMP High (NIST SP 800-53 Rev 5 baseline), RA-2. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open FedRAMP High (NIST SP 800-53 Rev 5 baseline) in the compliance library.
A FedRAMP baseline is a subset of NIST SP 800-53 Rev 5, enhancements included.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
system holds itEvidence a system already holds
- Vulnerability scan reports for internal, external, and authenticated scopes · Vulnerability scanner / patch tooling
periodic reviewEvidence produced at each review
- Penetration test report with retest evidence · Vulnerability scanner / patch tooling
governing documentDocuments that govern the control
- SSP RA-2 statement documenting the FIPS 199 High categorisation, information types and annual review · Policy repository / GRC workspace
- FIPS 199 worksheet with information types and impact levels, signed by the authorising official · Policy repository / GRC workspace
- Threat intelligence feed subscriptions and triage workflow · Policy repository / GRC workspace
- Risk acceptance memos signed by accountable executives · Policy repository / GRC workspace
First move
Common gaps auditors find
- High severity vulnerabilities exceed remediation SLA without risk acceptance
- Risk register entries lack named owner or due date
- Penetration tests scope narrow and exclude key applications
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