SR-4 Provenance
Establishes and maintains provenance for systems, components and associated data so origin and change history are known.
4
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
- Provenance records for critical components · Document repository
- Evidence of origin and chain of custody · Document repository
governing documentDocuments that govern the control
- Update of provenance as components change · Document repository
- Bill of materials where available · 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
- provenance known only as far as the reseller
- provenance captured at purchase and never maintained
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