Skip to main content

An independent cyber security consulting practice for businesses and public institutions.

MAXTSOGTCyber Security

Guide

A supplier had a security incident. What customers ask next.

After a security incident at a supplier, customers ask questions. Some questions go to the supplier that had the incident. When a widely used product is affected, questions can go to many suppliers at once.

Published

Asking these questions is standard practice. The NIST Cybersecurity Framework 2.0 asks organizations to monitor each supplier through the whole relationship. It also asks them to include suppliers in incident response.

The questions often come with a short deadline. This guide shows what customers usually ask for, and what to have ready.

If the incident happened at your company

Your customer needs facts from you quickly. It may have to notify a regulator or its own customers. Two public rules show the time pressure.

U.S. health data
A supplier that handles health data for a hospital is usually a "business associate." The U.S. federal rule (45 CFR 164.410) says the supplier must notify its customer without unreasonable delay. The limit is 60 calendar days after it discovers the breach.
EU personal data
A supplier that processes personal data for a customer is a "processor." Article 33 of the General Data Protection Regulation (GDPR) says the supplier must notify its customer without undue delay. The customer then has 72 hours, where feasible, to notify the supervisory authority.

Customers usually ask for five things.

  1. What happened, and when you found it.
  2. Which of their data is involved, and how many people it affects.
  3. What you did to stop it, and what you changed so it does not happen again.
  4. One named contact for further questions.
  5. Later, a check by an independent party that each fix is in place.

Points 1 to 4 match what the two rules require your customer to report. Your customer needs these facts from you.

Point 5 comes from contracts. Under GDPR Article 28, the contract must let the customer, or an auditor it chooses, audit the processor.

U.S. bank regulators say a contract may let a bank hire an independent party to audit a supplier.

The UK National Cyber Security Centre (NCSC) notes a pattern among customers with weak control over their suppliers. The first time their security teams contact a supplier is often for an audit after an incident.

You do not need every fact on the first day. The U.S. rule lets a supplier send more facts as they become available.

If the incident happened somewhere else

A serious vulnerability in a widely used product affects many companies at once. Your customers then want to know one thing: are you affected?

Risk management firms publish ready-to-use security questionnaires for these events. One for the Log4j vulnerability has 11 questions. One for the MOVEit vulnerability has 8. A customer can send such a questionnaire to all of its suppliers.

Customers often ask these questions.

  • Do you use the affected product?
  • Were you affected, and to what extent?
  • Have you applied the patch, or taken the other steps that the product's maker recommends?
  • Does this affect the service you deliver to us?
  • Who answers follow-up questions?

A customer may also check its suppliers more often after an incident. U.S. bank regulators say banks may change how often they monitor suppliers, and what information they use, as risks change.

If you do not use the product, say so. Also say how you checked.

What to have ready

Prepare these seven things before the questions arrive.

  • A short timeline: what happened, when you found it, and what you did.
  • A list of the customer data you hold, and where you hold it.
  • A list of the software and services you depend on, with version numbers.
  • A record of each fix: the change, the date, and who checked it.
  • Your current ISO/IEC 27001 certificate or SOC 2 report, if you have one.
  • One named contact and one email address for security questions.
  • The parts of your contract that cover incident notification and audits. Read them with your lawyer.

What to avoid

  • Do not guess. Say what you do not know yet, and when you expect to know.
  • Do not write "secure" or "fully fixed" without evidence. The supplier rules of one U.S. hospital system say that a misrepresentation may end the contract.
  • If you have cyber insurance, call your insurer or broker before you hire outside help. One large insurer says providers outside its own list must be named on the policy before any incident.

Sources

Last checked

How we help

MAXTSOGT is an independent cyber security consulting practice in San Francisco. We help small suppliers answer their customers.

Security questionnaire
We prepare the answers with you and organize your evidence.
Fix review
We check each fix you name. You receive a dated, signed record for your customers.

We do not run the emergency response. Your insurer and your lawyer lead that work.

We do not contact companies that had an incident. If you want help, send us a question.

Ask a security question

This guide gives technical information. It is not legal advice. For advice on your own contract, ask your lawyer.