Skip to main content
Promotional banner for a CUI buildout guide
Shared Vendor Incident Playbook for Website ComponentsSoftware Supply Chain Security
4 min readFor Compliance and Regulatory Affairs Teams

Shared Vendor Incident Playbook for Website Components

By Oversight InstitutePublished

What this template is for

At least 178 organizations, including several major brands, exposed website visitors to malware through a single third-party platform. That kind of incident turns one vendor into a shared exposure point. Your team shouldn't wait for a full technical write-up to decide who owns the response.

This template is a one-page incident escalation and evidence-gathering record for vendor-originated threats that reach your website visitors. It's written for compliance and regulatory affairs teams, who often inherit the hardest questions: Were visitors affected? Does anything trigger a notification obligation? Who decides?

Use it when a vendor supplying a script, plugin, or hosted component on your public properties is publicly named in a malware or compromise report.

Prerequisites

Have these in place before you need the template:

  • An inventory of externally supplied website components. Include tag managers, experimentation platforms, analytics scripts, chat widgets, and CDN-hosted libraries. Without this, you can't answer "Are we exposed?" quickly.
  • A named owner for each component in web engineering, plus a named compliance contact.
  • A Criticality Classification for each component, so you can see which vendors appear across multiple brands or business units.
  • Access to web logs, tag configuration history, and Content Security Policy (CSP) reports.
  • Your current Vendor Breach Management contacts and contract Notification Timeline terms.

The template

Copy the block below into your ticketing or GRC tool. Complete sections in order.

VENDOR-ORIGINATED WEBSITE EXPOSURE RECORD

1. TRIGGER
   Report source / link: ____________________
   Date and time received: __________________
   Vendor named: ____________________________
   Reported by (internal): ___________________

2. EXPOSURE SCREEN (answer within first working session)
   a. Do we load any component from this vendor on any public
      property?                          [ ] Yes  [ ] No  [ ] Unknown
   b. Which brands/domains/business units?
      ______________________________________
   c. Component type (script, plugin, hosted content, other):
      ______________________________________
   d. Loaded on authenticated or payment pages?
                                         [ ] Yes  [ ] No  [ ] Unknown
   e. Component owner notified (name/time): ____________

3. EVIDENCE TO PRESERVE (do before any remediation)
   [ ] Snapshot of current page source and tag configuration
   [ ] Tag/script change history for the reported window
   [ ] Web server and CDN logs
   [ ] CSP / browser violation reports, if collected
   [ ] Vendor communications (emails, status pages, advisories)
   [ ] Contract and data processing terms on file

4. IMPACT QUESTIONS
   a. Is there evidence malicious code executed on our pages?
                                         [ ] Yes  [ ] No  [ ] Unknown
   b. Exposure window (start/end, with source): ________
   c. Visitor populations potentially affected: ________
   d. Data types visitors could have entered on affected pages:
      ______________________________________
   e. Third-party forensic findings requested from vendor?
                                         [ ] Yes  [ ] No

5. DECISIONS (record owner, time, rationale)
   Containment (disable/remove component): ____________
   Internal escalation level: _________________________
   Legal/privacy review opened: ______________________
   Notification assessment (regulator, customer, partner):
      Decision: ______  Owner: ______  Date: ______
   Public statement needed: ___________________________

6. CLOSURE
   Vendor attestation received: [ ] Yes  [ ] No
   Lessons logged / inventory updated: ________________

How to customize it

Section 2 is your speed control. If your inventory is solid, you'll answer 2a through 2d in minutes. If you answer "Unknown" often, that's a finding in itself. Log it against your Continuous Monitoring of Active Arrangements program.

Section 3 order matters. Preserve first, remediate second. Removing a component before capturing configuration history can destroy the evidence you need for later impact and notification decisions.

Section 4 is where your regulatory profile applies. Add the instruments that govern you: privacy statutes, sector rules such as SR 23-4 for U.S. banking organizations, or EBA Outsourcing Guidelines for EU institutions. Add a line for each clock that could start, referencing your contractual Notification Timeline and any statutory windows your counsel confirms. Don't hard-code windows into the template unless legal has verified them.

Section 5 needs a decision rule you write in advance. Define who can approve containment without a meeting and what level of uncertainty triggers legal review. A common design: "Unknown" on 4a automatically opens legal review rather than waiting for certainty.

Add a concentration field. If one vendor appears across several brands, add a row to Section 2 that lists every affected business unit. This is your Concentration Risk Assessment in miniature, and it prevents each brand from running its own uncoordinated response.

Map to contract terms. If your agreements include a Right to Audit or incident notification clause, add a task to request vendor findings under those terms. Where a vendor uses sub-processors, note them from your Sub-Processor Disclosure.

Validation steps

Don't wait for a real incident to learn the template doesn't work.

  1. Run a tabletop with a named component. Pick a tag manager or experimentation script you actually load. Time how long Section 2 takes.
  2. Test the evidence step. Confirm engineering can produce tag change history and logs for a past window on request. If retention is too short, fix that now.
  3. Check ownership coverage. Every inventoried component should have both a technical and compliance owner. Blanks mean the form stalls at step one.
  4. Verify contacts and clocks. Confirm vendor incident contacts are current and that contractual Notification Timeline terms match what's in Section 4.
  5. Review after each use. Update the inventory, Criticality Classification, and any gaps in monitoring. A vendor that reached multiple brands should be reclassified upward.

An onboarding assessment tells you whether a vendor was acceptable on the day you signed. This record tells you who acts, on what evidence, and when the vendor stops being acceptable on a day you didn't choose.

This week, pick one externally supplied component and run the tabletop. If your team can't identify its owner or exposure quickly, fix the inventory before the next vendor incident.

Promotional banner graphic asking if you are ready for PCI DSS 4.0 with a call-to-action to get the guide

You Might Also Like