EvidenceSheet
FedRAMP High (NIST SP 800-53 Rev 5 baseline) · CA - Assessment, Authorization, and Monitoring

CA-1 Policy and Procedures

Develop, document, disseminate and review the policy for assessment, authorization and monitoring, and its procedures, on the FedRAMP-defined cadence: policy at least annually under High and at least every three years under Moderate, procedures at least annually and after significant changes under both.

Source: FedRAMP High (NIST SP 800-53 Rev 5 baseline), CA-1. 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.

6
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. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

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

none for this control

periodic reviewEvidence produced at each review

  • SSP CA-1 statement naming the assessment, authorisation and monitoring policy owner and its review cadence (policy yearly for High, at least every three years for Moderate; procedures yearly for both) · SIEM / log platform
  • Control assessment report with tester names and dates · Document repository

governing documentDocuments that govern the control

  • Assessment and authorisation policy with dated approval and links to the continuous monitoring procedure · Policy repository / GRC workspace
  • Continuous monitoring strategy with metric definitions · Policy repository / GRC workspace
  • Independent assessor statement of independence · Document repository
  • System security plan covering the authorization boundary · Policy repository / GRC workspace

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

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

AU-12(3) Changes by Authorized Individuals · CA-2 Control Assessments