SR-9 Tamper Resistance and Detection
Applies tamper resistance and detection to components across development, transport and operation.
3
artefacts
0
held by a system
0
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
none for this control
governing documentDocuments that govern the control
- Tamper resistance and detection measures in use · Document repository
- Inspection procedures and records · Policy repository / GRC workspace
- Handling of components found tampered with · 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
- tamper evidence applied but never inspected on receipt
- no procedure for a component that fails inspection
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-8 Notification Agreements · SR-10 Inspection of Systems or Components