SR-9 Tamper Resistance and Detection. Implement a tamper protection program for the system, system component, or system service
Tamper Resistance and Detection. Implement a tamper protection program for the system, system component, or system service.
5
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
- The anti-tamper measures applied, such as seals, enclosures, cryptographic attestation or packaging controls · Vendor register / contract repository
- Records of tamper indications found and the response taken · Document repository
governing documentDocuments that govern the control
- The tamper protection programme documentation covering the system, component or service · Document repository
- Inspection procedures and records showing tamper indicators are actually checked on receipt and in service · Policy repository / GRC workspace
- Coverage across the life cycle including transit, storage, maintenance and return · 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 evident seals applied but never inspected, so evidence of tampering is collected and ignored
- Programme covers delivery while maintenance returns and warranty exchanges bypass it
- No defined response to a tamper indication, so a found seal breach is rationalised away
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