Why a 60‑Minute Triage Matters
When a vendor publishes a breach notice, panic can spread faster than the news itself. For small SaaS teams, the first hour is critical: you need to know whether your data is at risk, which secrets are exposed, and whether you must inform customers. A structured, time‑boxed triage keeps the team focused and prevents over‑reactive or under‑reactive moves.
The process below is deliberately simple. It assumes you have a basic incident‑management channel (Slack, Teams, or a shared doc) and a small team of 2‑5 people. Each step takes a few minutes, and the whole thing fits comfortably into an hour.
Minute 0‑10: Set Up the Incident Record and Roles
Create a single place for everything – a document or channel named
incident-vendor-YYYYMMDD. Write a header with the vendor name, the time they announced the breach (in UTC), and the source URL. Keep the original announcement text in the document; vendors edit it later.-
Assign roles – you only need three:
- Lead – keeps the clock, makes decisions.
- Investigator – reads the notice, checks your systems.
- Communicator – drafts internal messages and any customer notifications.
If you’re a two‑person team, one person can play two roles.
- Log the basics – copy the following template into the document:
INCIDENT LOG Vendor: __________________ Announced (UTC): __________________ Source URL: __________________ We learned of it at: __________________ Lead / Investigator / Communicator: __________________ Status: TRIAGE Minute 10‑30: Answer the Six Core Triage Questions
Write a one‑sentence answer for each. If you’re unsure, note it as Unknown but assign an owner and a plan to find out.
| # | Question | What to look for | Owner | Notes |
|---|---|---|---|---|
| 1 | Do we use this vendor, and for what? | Inventory list, password manager, billing, SSO, .env files | Investigator | Search for the vendor name in all places |
| 2 | What did the vendor say was affected? | Systems accessed, data types, time window, confirmation of customer data | Investigator | Treat vague phrases as unknown |
| 3 | What data could have been sent to them? | Customer data, employee data, source code, internal docs, payment data, metadata | Investigator | List each type |
| 4 | What credentials do they hold? | API keys, OAuth tokens, SSO/SAML configs, webhook secrets, service accounts, keys in docs | Investigator | Check all credential storage |
| 5 | What can their access reach in our systems? | Auth provider, docs tool, billing provider, etc. | Investigator | Map to internal systems |
| 6 | Did the exposure window overlap with our usage? | Vendor’s stated window vs. when you used the integration | Investigator | Mark as Yes/No/Unknown |
Quick Example
Vendor: Hosted documentation platform
Announcement: “An attacker accessed internal storage; some customer content may have been viewed.”| Q1 | Yes – public docs & internal runbooks | Priya |
| Q2 | Storage access, vague “customer content”, window unclear | Unknown – need vendor details |
| Q3 | Page content, editor emails | Priya |
| Q4 | CI publish token, Google SSO | Priya |
| Q5 | Token can publish, no prod access | Priya |
| Q6 | Used for 2 years, assume overlap | Priya |Likely exposure: internal runbooks (check for pasted secrets), editor emails.
Minute 30‑45: Classify the Risk Level
Choose one of three levels. If you’re uncertain, default to the higher level; you can downgrade later.
| Level | Meaning | Immediate Action |
|---|---|---|
| A: Confirmed | Vendor states our data or credentials were exposed, or you find evidence. | Rotate exposed secrets immediately; start log review; prepare customer notice |
| B: Possible | We use the vendor, scope unclear. | Rotate high‑privilege secrets; review logs; request details from vendor; draft notice, don’t send |
| C: Not affected | No use, or the affected product/feature not used. | Record reasoning; re‑check in 24 hrs |
Quick‑Decision Checklist
- Can any exposed credential reach production data? If yes, rotate first.
- Did we ever paste a secret into the vendor’s tool (docs, tickets, chat)? Search for
key,token,password,secret,BEGIN PRIVATE. - Does the vendor hold personal data of our customers? If yes, note it for possible legal notification review.
- Is the vendor an SSO/login path? Check for unusual sessions and consider forcing re‑auth.
Minute 45‑60: Communicate, Contact, and Schedule Next Steps
- Ask the vendor for details – send a concise request from your account’s support channel. Example:
Hi [Vendor] team, We’ve read your breach notice and need more details to assess our exposure. Specifically: * Which customer data types were accessed? * What was the exact time window of the breach? * Did the breach involve any credentials we supplied? * Do you have a list of affected customers? Thanks for your prompt help. - Draft internal communication – keep the tone factual and concise. Share the risk level, what we know, and the next steps. Example:
Subject: Vendor Breach – Immediate Actions Required Hi team, Vendor X announced a breach. Our triage indicates a *Possible* risk (Level B). We have rotated the CI publish token and are reviewing logs. Please review the attached summary and let me know if you see anything else. - Schedule follow‑up – set a 1‑hour check‑in if the vendor is slow to respond, or a 24‑hour review if the risk is low.
What Happens After the Hour?
- If Level A – you have a confirmed breach. Rotate all exposed credentials, review logs for malicious activity, and draft a customer notification. Consult a lawyer for legal obligations.
- If Level B – continue rotating high‑privilege secrets, monitor logs, and keep the customer notice draft ready. Await vendor details before deciding on a public notice.
- If Level C – log the findings, keep monitoring, and re‑evaluate in 24 hrs.
The key is that you have a clear, documented decision after the first hour, and you’re not rotating secrets blindly or ignoring the breach.
Takeaway
A structured, one‑hour triage turns a chaotic vendor breach notice into a manageable, actionable plan. By answering six core questions, classifying risk, and communicating effectively, you protect your systems and keep stakeholders informed without panic.
The full “Vendor Breach Response Runbook for Small SaaS Teams” is available at https://heracles-store.pages.dev/p/vendor-breach-response-runbook-for-small-saas-teams/.
Written with AI assistance and reviewed for accuracy before publishing.

