SI-7(15) Software, Firmware, and Information Integrity | Code Authentication
Implement cryptographic mechanisms to authenticate FedRAMP-defined software or firmware components prior to installation.
3
artefacts
1
held by a system
1
at each review
moderate
to go live
Source control / CI pipeline
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Pipeline or configuration step performing signature verification before install · Source control / CI pipeline
periodic reviewEvidence produced at each review
- Records of components rejected for failing authentication · Identity provider / directory
governing documentDocuments that govern the control
- List of components subject to cryptographic authentication · Policy repository / GRC workspace
First move
Start with the 1 of 3 artefacts that already live in a system (Source control / CI pipeline); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Verification applied to vendor packages but not to internally built artefacts
- No record kept of verification failures
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 sheetSI-7(7) Integration of Detection and Response · SI-8 Spam Protection