IR-4 Incident Handling
Handles incidents that cross the supply chain boundary, where containment depends on a party the organization does not control.
3
artefacts
0
held by a system
1
at each review
hard
to go live
Vendor register / contract 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
- Incident records involving suppliers · Vendor register / contract repository
governing documentDocuments that govern the control
- Containment actions requiring supplier cooperation · Vendor register / contract repository
- Escalation route into supplier management · Vendor register / contract 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
- handling stalls waiting for supplier response with no escalation
- supplier told nothing until the incident closes
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