SR-4 Provenance. Document, monitor, and maintain valid provenance of the following systems, system components, and associated data: [organization-defined]
Provenance. Document, monitor, and maintain valid provenance of the following systems, system components, and associated data: [organization-defined].
5
artefacts
1
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
- Provenance records showing history of ownership, custody, location and changes for each · Document repository
periodic reviewEvidence produced at each review
- Evidence provenance is monitored, not just documented once at acquisition · Document repository
- Records where a provenance discrepancy was identified and investigated · Document repository
governing documentDocuments that govern the control
- The defined systems, components and associated data whose provenance is maintained · Document repository
- The method for validating provenance claims from suppliers · Vendor register / contract repository
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your Document repository on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.
Common gaps auditors find
- Provenance captured at purchase and abandoned once the component is in service, missing repairs and replacements
- Supplier assertions accepted with no validation method behind them
- Software and firmware provenance omitted while hardware provenance is tracked
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 sheetSR-3 Supply chain controls and processes · SR-5 Acquisition strategies, tools, and methods