When something happens · 4.5

Telling a customer something happened

Telling a customer something happened. What it costs, who decides, and what usually goes wrong.

For an independent reference point, see MITRE ATT&CK Enterprise Matrix.

Two different obligations

Reporting to the government is not telling your customer

The clause directs a report to a government portal. Whether and when you tell the prime contractor or the agency you work for is governed by your contract with them, by the relationship, and by judgement.

Suppliers routinely satisfy the first and delay the second, on the reasoning that they will have more to say later. That reasoning is understandable and it is usually wrong.

Early and specific

Why waiting for the full picture costs more

A customer who learns early receives a partial account from you. A customer who learns late receives a complete account and also learns that you knew for three weeks.

The second fact is the one that damages the relationship, and it is independent of how well the incident was handled.

Early does not mean speculative. It means: this happened, this is what we know, this is what we do not yet know, this is what we are doing, and we will update you on a stated day.

What to say

Five things, and no more

  • What happened, factually, with times.
  • What information was or may have been involved.
  • What you have done so far.
  • What you are doing next, with a date.
  • Who they should contact and how.

Written by one person, reviewed by counsel where the stakes warrant it, and sent by somebody senior enough that the recipient understands it is being taken seriously.

What not to say

Four things that make it worse

Speculation about cause. Particularly attribution. It is frequently wrong and it is quoted back.

Blame. Of a vendor, an employee or the customer's own systems. Even where accurate, it reads as deflection at this stage.

Assurance you cannot support. "No data was affected", said before the analysis, is the sentence most likely to be retracted and most damaging when it is.

Silence after the first notification. An update on the promised day, even one saying that the analysis continues, is worth more than a complete report a week late.

The legal tension

Speed against review

Counsel will want to review what goes out and review takes time. The resolution is a template agreed in advance, so that the first notification is a form with facts inserted rather than a document drafted from nothing under pressure.

Agree the template while nothing is happening and the tension mostly disappears.

Other people to tell

Three groups often forgotten

Your own staff, who will hear something and construct the rest. Other customers, if the same systems serve them. And your insurer, whose policy may require notice sooner than anybody else.

Afterwards

Tell them what changed

A short note when the review is complete, saying what was found and what has been altered, closes the matter properly. Suppliers who do this are remembered for handling it well; suppliers who go quiet are remembered for the incident.

Also

Elsewhere in when something happens