SR-12 Component Disposal (SR-12)
Dispose of data, documentation, tools, or system components using defined techniques and methods.
6
artefacts
1
held by a system
1
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
- Continuous monitoring scorecards for critical suppliers · SIEM / log platform
periodic reviewEvidence produced at each review
- Supplier incident notification clauses and exercise records · Vendor register / contract repository
governing documentDocuments that govern the control
- Control implementation statement for SR-12 citing the system mission and inheritance from common controls · Document repository
- Contractual flow down of security requirements to subcontractors · Document repository
- Supply chain risk management policy and program charter · Policy repository / GRC workspace
- Tiered vendor inventory with criticality scoring · Vendor register / contract repository
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your SIEM / log platform 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
- Supplier incidents discovered through news rather than contractual notification
- Flow down clauses present in master agreements but missing from statements of work
- Sub tier suppliers not identified for critical components
- Vendor risk tier ratings static despite changes in service scope
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