OneNym.idDiscuss deployment
English

THE BOARDROOM FIREWALL / Appendix F

A Breach Materiality Worksheet

In the middle of an incident, leaders must decide whether it is serious enough to tell a regulator, the market, customers or the board. This appendix offers a worksheet that makes that decision consistent, documented and prepared in advance.

This page summarises the chapter. The full text is in the book.

Why decide the method in advance

The worksheet grows out of a story in Chapter 5, where Meridian's general counsel, chief financial officer and head of security wrote a short materiality guide after an investor's lawyers asked how the company decides whether an incident must be reported. For a leader, materiality is best treated as a plain question: is this serious enough that we have a legal or moral duty to tell someone outside the response team? Each audience has its own triggers and deadlines, and definitions vary by country, sector and type of company, so there is no universal threshold.

That is why the method should not be invented under pressure. A pre-agreed worksheet does not make the decision, but it ensures the same factors are weighed in the same order each time, and that the reasoning is written down. The book is explicit that the worksheet is not legal advice: thresholds should be set in advance with qualified counsel, who have the final word.

Nine factors, rated low, medium or high

Each factor is answered with what is known now and rated low, medium or high: the number and type of people affected, the sensitivity of the data, operational disruption, financial impact, safety implications, legal and regulatory triggers, reputational and customer impact, whether the attacker may still be present, and contractual notification duties. Where a factor has a number or deadline, the company fills in its own threshold beforehand. A factor that cannot yet be assessed is marked unknown rather than low, because an unknown is itself a reason to escalate. A short note beside each rating is worth more than the rating alone.

From ratings to a provisional call

The ratings lead to one of three provisional conclusions. Likely material means escalating and preparing notifications alongside the technical response; a single high on safety, legal triggers, sensitive data or a running statutory clock is enough. Needs legal review is the default for anything mixed or uncertain, and such cases go to counsel immediately rather than waiting. Not material is reserved for events that are minor on every factor, and even then the reasoning is recorded.

The rule leans towards caution because over-escalating costs a little effort, while under-escalating can mean a missed legal deadline. Two reminders belong on the page: the decision should be revisited as new facts arrive, and some disclosure clocks start when the organisation decides an event is material, so deciding and acting should happen close together.

Putting it to work

Fill in thresholds now with counsel, keep a printed copy with the incident response plan, name who makes the call (typically the chief executive with the general counsel and chief financial officer), and inform the board chair of any incident serious enough to reach the worksheet. Keep every completed sheet, dated and timed, with the names of those who decided.

KEY POINTS

Key points

  • Agree materiality thresholds with your lawyers before any incident happens.
  • Mark factors you cannot yet assess as unknown, not low, and treat unknowns as a reason to escalate.
  • Send borderline incidents to counsel immediately instead of waiting.
  • Keep a printed copy of the worksheet with the incident response plan.
  • Tell the board chair about any incident serious enough to reach the worksheet.
  • Keep every completed sheet with the date, time and names of the decision-makers.

QUESTIONS

Common questions

How do we decide if a cyber incident is material?
The Boardroom Firewall recommends a pre-agreed worksheet that rates nine factors as low, medium or high, including people affected, data sensitivity, operational disruption, financial impact, safety, legal triggers, reputation, whether the attacker is still present and contractual duties. The ratings lead to one of three provisional conclusions. Thresholds should be set in advance with qualified lawyers, who make the final call.
What should we do if we are not sure whether a breach must be reported?
Treat it as needing legal review and send it to counsel immediately rather than waiting to see. Borderline cases, mixed pictures and unknown key facts all belong in this category. It is better to review many incidents that turn out not to be material than to miss the one that was.
Who should decide whether a cyber incident is disclosed?
The decision-makers should be named in advance, typically the chief executive together with the general counsel and chief financial officer. The book also recommends a rule that the board chair is told about any incident serious enough to be assessed on the worksheet, whether or not it is finally judged material.
Does the disclosure deadline start when we decide an incident is material?
For some obligations, yes: the clock can begin when the organisation determines that an event is material. That is why reaching the decision and acting on it should happen close together, rather than treating the decision as a quiet internal milestone. The exact rules vary by jurisdiction, so they should be confirmed with counsel in advance.
Why should we record our reasoning on a breach decision?
A dated and timed record of the factors, the conclusion and the names of those who decided shows what was known and when. Regulators, insurers and later reviews will ask to see exactly this, and the record protects both the company and its leaders.