PlaybookChecked 16 November 2026
Third-party and supplier incident response playbook
Stages
The template in full
1 When to use this playbook
Use this playbook when a supplier tells you it has been compromised, when a supplier's product or update is malicious, or when a supplier holding your data may have lost control of it.
2 Before you start: prerequisites
Complete these before an incident, as part of planning.
- Each critical supplier is on the list in section 12 with an incident contact and a contractual notice time.
- Contracts say what the supplier must tell you, how fast, and what it may do on your behalf.
- You know what data and access each supplier has.
- You have an exercise scenario that includes a supplier failure.
3 Workflow
Work in this order. Record each step and its time in the incident log.
- Get the facts from the supplier: what happened, when, what of yours is affected, and what it has done.
- Check your own logs for activity linked to the supplier: connections, API calls, accounts and updates.
- Contain: suspend the supplier's access, rotate shared secrets and credentials, and block affected components.
- Assess your exposure: data held by the supplier, access it had to your systems, and customers who depend on it.
- Decide who must be told. A supplier that is a processor must tell you without undue delay under GDPR Article 33(2); a business associate must tell the covered entity under 45 CFR 164.410.
- Agree a shared communications line with the supplier.
- Review the contract and the supplier's assurance after the incident.
4 Decision points
Stop at each of these and record the decision, the decider and the time.
| Decision | Who decides | Information needed |
|---|---|---|
| Suspend the supplier's access? | Technical lead, executive sponsor | Risk to your systems versus the business use |
| Are you the controller or covered entity with a notice duty? | Privacy lead, legal | Contract role, data involved |
| Switch suppliers? | Executive sponsor | Alternatives, time to switch |
5 Notices to check
Open section 10 of the plan and confirm whether any of these start a notice clock.
- If you are the controller or covered entity, your own clock may have started when the supplier told you, or earlier if you would have known with reasonable diligence.
- Check customer contracts: your customers may expect notice because of your supplier's incident.
6 Exit criteria and follow-up
Close the playbook only when all of these are true.
- Supplier access restored on agreed terms or ended.
- Shared secrets rotated.
- Contract and assurance updated.
About this playbook
What is the incident response playbook for a third-party incident?
NIST SP 800-61 Rev. 3 lists CSF outcome GV.SC-08: relevant suppliers and other third parties are included in incident planning, response, and recovery activities. It adds that responsibilities should be defined in the contract.
The NCSC supply chain security guidance, published 28 January 2018 and reviewed 22 October 2025, sets out 12 principles and notes that very few UK businesses set minimum security standards for their suppliers, citing the 2025 Security Breaches Survey.
Download the template
Free, no sign-up. Word (.docx, 3 KB): download. PDF (46 KB): download. Both files carry the same text as this page, edition 16 November 2026.
Related pages
- Incident response playbook: what it is and how to build a library
- Free incident response plan template
- Cloud account compromise incident response playbook
- DDoS attack incident response playbook
- What is an incident response playbook, and what is it for?
- How to write an incident response playbook
- Incident response plan templates: the full set
- Incident response steps: the order and who does what
Sources
- NIST SP 800-61 Rev. 3, full text (April 2025)
- NCSC, Supply chain security guidance
- Regulation (EU) 2016/679 (GDPR), EUR-Lex
- eCFR, 45 CFR 164.410, Notification by a business associate
Last reviewed 16 November 2026. Each source above was read that day.