SR-11 Component authenticity
Requires anti-counterfeit policy and procedures to be developed and put into practice, including how counterfeit components are detected and kept out of the system, and requires any counterfeit component found to be repo
4
artefacts
0
held by a system
3
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
- Evidence of purchasing through authorised distributors or original manufacturers · Document repository
- Inspection or verification records for received components · Document repository
- Reporting records where counterfeit components were identified · Document repository
governing documentDocuments that govern the control
- Anti-counterfeit policy and procedures including detection methods · Policy repository / GRC workspace
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
- Components sourced from secondary markets during shortages with no additional verification
- Detection relies on visual checks alone with no provenance verification
- No reporting path defined, so counterfeits are returned quietly and never reported
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-10 Inspection of systems or components · SR-12 Component disposal