When a vendor reports a security incident, your team needs more than a brief notice saying an investigation is underway. This guide provides a reusable vendor breach assessment checklist, severity model, evidence request, and escalation workflow for determining what happened, which systems and data are involved, what action is required, and what should be tracked until remediation is complete.
Overview
A third-party security incident can affect your business even when your own network shows no sign of compromise. A supplier may host customer information, process payments, authenticate users, connect to internal systems, or provide a critical operational service. The first vendor notification is often incomplete because facts are still being established. Your response should therefore create a disciplined record of known facts, open questions, decisions, and follow-up dates.
Start by assigning an incident owner from security, IT, risk, or vendor management. Include legal, privacy, communications, procurement, and the affected business owner when the facts indicate material customer, employee, regulatory, or operational impact. Preserve the vendor’s original notice, contract, security addendum, data-processing terms, and relevant service documentation. These records help establish what the vendor was required to report and what information your organization is entitled to request.
Do not treat the vendor’s severity label as the final answer. Assess the incident against your own exposure. A vendor may describe an event as limited because its internal systems were segmented, while your organization may still face significant risk if sensitive data was accessed or privileged credentials were exposed.
What to track
1. Timeline and attack details
Ask the vendor to provide confirmed dates and clearly label estimates. Track:
- The suspected initial access date and time zone.
- The date the vendor detected suspicious activity.
- The date containment began and whether containment is complete.
- The date your organization was notified and the reason for any delay.
- The period during which unauthorized access, data exposure, or service disruption may have occurred.
- Whether the incident is ongoing, contained, eradicated, or under monitoring.
A timeline should distinguish between an event that is still being investigated and a conclusion supported by evidence. Record every revision rather than overwriting earlier entries.
2. Systems, services, and connections
Identify the affected products, environments, regions, accounts, application programming interfaces, and integration points. Ask whether the incident involved production systems, backups, development environments, support tools, identity systems, or subcontractors. Confirm whether your organization’s tenant, account, credentials, encryption keys, network connection, or administrative access was affected.
Request a clear statement about what was not affected as well as what was affected. Negative findings should include the scope and method of verification where the vendor can provide them.
3. Data types and affected populations
Request a data inventory that separates confirmed access, suspected access, and data that was merely stored in an affected environment. Ask about customer, employee, contractor, financial, authentication, health, confidential business, and regulated information. Confirm whether data was viewed, copied, altered, deleted, encrypted, published, or used for follow-on activity.
Also ask how many records or individuals may be involved, whether the count is preliminary, and when a more reliable estimate is expected. Avoid accepting broad descriptions such as “limited customer data” without asking which fields and populations that phrase covers.
4. Containment, evidence, and remediation
Use this evidence request template in writing:
Please provide the current incident timeline; affected systems and services; affected data categories; indicators of compromise relevant to our environment; containment and eradication actions; forensic findings available for sharing; authentication or credential actions required from us; backup and recovery status; subcontractor involvement; customer or employee impact assessment; notification analysis; and the next scheduled update.
Ask whether logs, forensic images, access records, malware samples, or threat indicators can be shared securely. The vendor may not be able to release raw evidence, but it should explain what validation was performed and provide actionable indicators when appropriate. If your own systems could be involved, coordinate evidence preservation before making changes that might destroy useful records. For broader containment and recovery practices, see the ransomware incident checklist.
Severity comparison
| Severity | Typical indicators | Initial response | Review cadence |
|---|---|---|---|
| Critical | Confirmed access to sensitive data, privileged credentials, production systems, or a service essential to operations; active threat or material disruption. | Activate incident leadership, isolate affected connections, preserve evidence, and involve legal and communications teams. | Daily or more frequently until containment is verified. |
| High | Credible unauthorized access, significant uncertainty about data exposure, or disruption to an important business process. | Open a formal third-party incident, validate exposure independently, and require a dated remediation plan. | Several times per week during investigation. |
| Moderate | Limited scope, no confirmed sensitive-data access, and effective containment, but meaningful control or availability concerns remain. | Document the decision, request supporting evidence, and monitor corrective actions. | Weekly until closure. |
| Low | Attempted activity or isolated issue with no indication of access, impact, or connection to your environment. | Record the event, confirm preventive controls, and request closure criteria. | At agreed checkpoints or during routine reviews. |
This table is a starting point, not a substitute for your risk methodology, contractual definitions, or legal assessment.
Cadence and checkpoints
Use an escalation workflow that moves from fact gathering to decisions:
- Within the initial review: Validate the notice, identify the vendor owner, preserve records, map the service to business processes, and determine whether your organization has an immediate containment action.
- At the first checkpoint: Obtain the timeline, affected systems, data categories, current containment status, and next update date. Require the vendor to separate confirmed facts from assumptions.
- During active investigation: Compare vendor updates with your own identity, endpoint, application, data-loss-prevention, and network telemetry. Rotate or suspend exposed credentials when justified, using a controlled change process.
- Before customer or regulator decisions: Ask legal and privacy leaders to assess applicable contractual and notification duties. Requirements vary by jurisdiction, data type, sector, and the role of each organization; do not rely on a generic deadline.
- At closure: Obtain a written root-cause summary, remediation commitments, control improvements, residual risks, and a date for validating those commitments.
Set a monthly or quarterly third-party monitoring checkpoint for critical suppliers. Review open incidents, overdue evidence, unresolved risk acceptances, security advisories affecting vendor products, and changes in service architecture. A vulnerability affecting a vendor component may change the assessment even when there is no reported breach; use the cybersecurity advisory guide to structure patch and exposure decisions.
How to interpret changes
A change in the vendor’s answer is not automatically evidence of poor response. Early facts often become more precise as logs and forensic work are reviewed. The important questions are whether the change is explained, whether the affected scope is expanding, and whether the vendor’s controls and communication remain adequate.
Escalate when the affected date range expands, sensitive fields are added, privileged access is implicated, the vendor cannot explain missing logs, the incident remains active, a subcontractor becomes involved, or the vendor misses agreed update dates. Escalate internally when your own telemetry shows related activity, when business continuity is threatened, or when customer communications may be necessary.
Track three separate statuses: technical containment, meaning the attacker’s access or harmful activity has been stopped; business impact, meaning services and obligations are stable; and risk closure, meaning evidence supports the conclusion and corrective actions are complete or formally accepted. A vendor can achieve one without achieving the others.
For communications, maintain a decision log identifying who approved each customer, employee, partner, or regulator message. A communications matrix can prevent inconsistent statements while facts continue to change. Review the cyber incident communications matrix for a reusable structure.
When to revisit
Revisit this vendor security incident response process whenever a supplier reports a new event, changes its hosting or subcontractor model, renews a contract, adds a sensitive data flow, or becomes essential to a critical business process. Conduct a formal review at least quarterly for high-risk vendors and during annual vendor-risk assessments for other important suppliers.
At each review, confirm that contact details, escalation paths, notification terms, evidence-sharing provisions, audit rights, recovery commitments, and data-retention requirements still match the service. Update questions after recurring supply-chain incidents reveal new attack paths, such as identity compromise, exposed support tooling, software-update abuse, or credential reuse. Recheck privacy and contractual requirements with qualified legal or privacy professionals when the affected data or jurisdictions change.
Practical next step: copy the questionnaire and severity table into your vendor-risk register today. Assign an owner, add the next checkpoint, and record what evidence would move the incident from investigation to closure. A concise, regularly maintained record is more useful than a one-time assessment when the vendor’s answers evolve.