If a supplier reports a data breach, verify the notice through a contact or website you already trust. Find out what information or access may be affected, then take steps that match your exposure. A supplier incident does not automatically mean your own systems were hacked.
What to Do After a Supplier Data Breach

Jump to a section
Start with the evidence you have
- Verify the message. Contact the supplier through an independently known route. Do not use a sign-in link or telephone number supplied only in an unexpected notice.
- Ask what is affected. Request the relevant services, incident period, information categories and whether the supplier had access to your systems. Ask what is confirmed and what is still being investigated.
- Protect exposed access. If credentials, tokens or a connected service may be affected, coordinate revocation or rotation with the appropriate service owner. Restrict supplier access where necessary without interrupting essential operations blindly.
- Record your decisions. Keep the verified notice, dates, affected services, contacts and actions in a protected location.
A supply-chain attack can affect organizations in different ways. A breach of a vendor's contact list, a stolen credential and unauthorized access through a managed service do not call for the same response.
Identify your actual connection
List what the supplier handles: customer records, employee information, payment details, business credentials, software, remote access or a combination. Ask the person who owns the relationship to verify the supplier's statement and check your own account and audit records where available.
If a password or API key may have been exposed, revoke or rotate it through the issuing service and check the permissions and logs. Replacing a key does not necessarily disable the old one. Our API key exposure guide explains the sequence.
Ask the supplier the questions that change your response
- Was your organization's information or account actually included, or is the scope still being determined?
- Were passwords, API keys, tokens or the supplier's access to your systems affected?
- What protective steps is the supplier recommending, by when, and where will verified updates be published?
- What logs or records can the supplier preserve or provide to help investigate?
If the answers are not yet known, record that uncertainty and agree on the next update. A contact list leak may call for vigilance against impersonation; evidence of a compromised integration may require immediate access changes and investigation.
Expect follow-on impersonation
A criminal who has real names or supplier details may send a convincing invoice, phone call or sign-in request. Verify bank-detail changes using a number already held independently. If money has been sent to a suspected fraudulent account, contact the bank immediately and ask about stopping or recalling the transfer. The fake invoice guide covers what to preserve.
Decide who needs to know
Involve the staff responsible for the supplier, IT and any affected records. If personal or customer information may be involved, consult your privacy or legal adviser about duties that apply to the facts and your jurisdiction. Avoid promising that information was safe or breached until the evidence supports it.
Ask the supplier for updates, available protective steps and a contact for unresolved questions. Keep confirmed facts separate from assumptions. CISA's supplier risk guidance for small businesses describes ways to assess dependencies and supplier controls.
Review the relationship after the urgent checks
Consider whether the supplier still needs the same permissions, whether access can be limited and whether you have a workable alternative if the service is unavailable. Record who owns the relationship and how the supplier will communicate future incidents.
Effective response is proportionate to the actual connection. A verified notice and a clear inventory help the business address real exposure without treating every supplier incident as proof of a wider compromise.