SR-7 Supply Chain Operations Security
Applies operations security to acquisition so that adversaries cannot learn what is being bought, from whom and when.
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
- Operations security measures applied to acquisition · Document repository
- Controls on disclosure of supplier and delivery detail · Vendor register / contract repository
- Awareness for procurement staff · HR system / LMS
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
- delivery schedules and destinations broadly visible
- supplier relationships publicised in detail
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-6 Supplier Assessments and Reviews · SR-8 Notification Agreements