SR-12 Component disposal
Requires organization-defined data, documentation, tools or system components to be disposed of using organization-defined techniques and methods, so that disposal does not release information or usable components to una
4
artefacts
0
held by a system
2
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
- Disposal records including certificates from any third party disposal provider · Vendor register / contract repository
- Verification records confirming disposal was completed as specified · Data governance / DLP tooling
governing documentDocuments that govern the control
- Defined disposal techniques per item type and classification · Policy repository / GRC workspace
- Evidence that data and documentation are destroyed as well as hardware · 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
- Hardware disposal managed while documentation and development tooling are not
- Third party disposal used with no certificate or verification obtained
- Disposal method chosen by cost rather than by the classification of what is held
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