PS.3.1 Archive and Protect Released Software
Archive each release along with its source, build metadata, and dependencies. Retain the archive long enough to support incident response, customer support, and regulatory obligations.
4
artefacts
0
held by a system
0
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
none for this control
governing documentDocuments that govern the control
- Release archive policy · Policy repository / GRC workspace
- Storage layout for archived artifacts · Document repository
- Retention schedule by product · Policy repository / GRC workspace
- Demonstration of restoring a historical build · Document repository
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
- only the binary archived without the corresponding source state
- retention shorter than support obligations
- no test of restoration
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 sheetPS.2.1 Provide a Mechanism for Verifying Software Release Integrity · PS.3.2 Software Bill of Materials