CA-2 Control Assessments
Assess controls annually (FedRAMP); third-party assessor (3PAO) required; produce SAR.
6
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
- Control assessment report with tester names and dates · Document repository
- Authorization to operate memorandum signed by the authorizing official · Document repository
governing documentDocuments that govern the control
- Control implementation statement for CA-2 citing the system mission and inheritance from common controls · Document repository
- Independent assessor statement of independence · Document repository
- System security plan covering the authorization boundary · Policy repository / GRC workspace
- Plan of action and milestones tracking open findings · 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
- Authorization boundary description does not match the asset inventory
- POAM items past due without justification or risk acceptance
- Continuous monitoring metrics collected but not reported to leadership
- Assessment scope omits inherited cloud provider controls
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