OneNym.idDiscuss deployment
English

THE BOARDROOM FIREWALL / Chapter 1

Why Security Is Now a Leadership Job

When the systems stop, the first questions are not technical: how long will we be down, who decides, and what did we know beforehand? Chapter 1 explains why cyber risk has moved from the server room to the boardroom.

This chapter is published in full.

It is 7:14 on a Monday morning, and every screen in the building has gone dark. The warehouse scanners, the order portal, the payroll system, the email that would normally tell three hundred staff what to do next: all replaced by a single message demanding money. Somewhere a phone starts ringing, and it does not stop.

By the time the chief executive reaches the office, the questions have begun, and none are technical. How long will we be down? What do we tell the supermarkets? Is the customers' data gone? Do we pay? Who decides? And beneath them all, the one that will follow this leader into every boardroom and newspaper for years: what did we know, and what did we do about it?

Not long ago this was an "IT problem," handled in a back room. No longer. When a company's systems are broken into today, it is the chief executive, the chair, and the board who must explain it, in business terms, under pressure, often in public.

This book is about being the leader who, when that morning comes, already knows the answers, or at least who to ask. It explains why cyber risk now lands on your desk, what you are accountable for, what a breach truly costs, and how the risks that cause real harm work, from ransomware to artificial intelligence. It ends with a concrete 90-day action plan you can start the week you put it down. You will not need to become a technologist, only a capable owner of the risk.

1.1 From the Server Room to the Boardroom

Twenty years ago, most companies could lose their computers for a day and still trade. Orders came by phone and fax. Invoices were printed. The warehouse ran on clipboards and memory. A virus was an annoyance, like a burst pipe in the staff kitchen: messy, irritating, and fixed by the maintenance team while everyone else got on with the day.

That world is gone. Today the systems are not a support function beside the business; they are the business. Orders arrive through a website and an app. Stock levels, delivery routes, payroll, supplier payments, and customer records all live in software, much of it rented from other companies and running in data centres you will never visit. If those systems stop, the trucks stop. If the customer data leaks, the customers leave. If the payment system is tricked, the money is gone.

When technology carries the business, a threat to the technology is a threat to the business. Yet the people best placed to understand the technology are often not the ones with authority to make business decisions about it. A capable IT manager can tell you an old system needs replacing. Only a leader can decide whether that replacement is worth delaying a product launch, or whether to accept the risk for another year.

Several forces have pushed the subject into the boardroom.

The first is dependence. Almost every company is now a technology company in the sense that matters: it cannot operate without its systems, which makes outages and break-ins operational events, not technical ones.

The second is money. Criminals discovered that attacking companies pays. They lock up systems and demand a ransom, trick finance teams into paying fake invoices, and steal data to sell. Where there is reliable profit, there is a reliable, growing industry.

The third is law and expectation. Regulators in most major economies now require companies to protect personal data and report serious breaches promptly. Investors want to know how cyber risk is managed, and large customers send security questionnaires before they sign. These are questions about the company's conduct, not its software, and they land on the desks of senior leaders.

The fourth is visibility. A break-in used to be a private embarrassment. Now it is often public within days, and the story attaches itself to the company name for years.

Put these together and you can see why security has moved from the server room to the boardroom. It is not that technology became more important to technologists; it is that technology became inseparable from revenue, reputation, and legal duty, the things leaders are paid to look after.

Here is the company we will follow through the book.

Meridian Foods is a fictional mid-sized consumer company. It makes sauces, snacks, and chilled ready meals, sold through supermarkets, independent grocers, and its own online shop. It employs about 450 people across a head office, two production sites, and a distribution centre. It has a website, a customer app with a loyalty scheme used by around 300,000 people, an online ordering portal for its trade customers, and a growing set of cloud systems that run everything from production planning to payroll. It relies on dozens of suppliers, from ingredient growers to a logistics partner to the software companies whose tools its staff use every day. It has an annual turnover of roughly 180 million (pick your currency; the logic is the same), a board of seven directors, and an audit and risk committee.

The people we will meet most often are Daniel Okafor, the chief executive; David Chen, the chief financial officer; Tom Brennan, the head of IT, who has been with the company for eleven years; Aiko Tanaka, a security manager who reports to Tom and is the closest thing Meridian has to a dedicated security lead; and Margaret Hale, the chair of the board. Throughout the book you are cast as a senior leader at Meridian, sometimes in Daniel's chair, sometimes David's, sometimes on the board. Either way, you are one of those who will be asked, "What did we know, and what did we do about it?"

In the Boardroom: The Question Nobody Expected

It is the quarterly board meeting. David has just finished the financial results. Tom is listed for ten minutes near the end, under "IT update," which usually means a slide about laptop replacements.

Before Tom can begin, a non-executive director, a retired retail executive named Graham, raises his hand. "Before the IT slide, a question. Last month a supermarket chain we sell to had its systems locked by criminals. Their stores ran on paper for nine days. If that happened to us tomorrow, how long would we be down, and who would decide what to do?"

The room goes quiet. Tom starts to answer, carefully, about backups and antivirus software. Graham listens politely, then asks again. "I understand the tools. My question is about us. Who decides? How long? What would it cost?"

Nobody in the room can answer. Not because the company has been careless, but because the question has never been asked in this form. It has always been a technical topic, discussed in technical terms, at the end of the agenda.

Margaret, the chair, closes the item gently. "Graham has put his finger on something. Daniel, can we bring this back next quarter as a proper agenda item, not an IT update? I would like to understand what we are exposed to, in plain terms, and who owns it."

That moment is where this book begins. Nothing has gone wrong at Meridian. But the question has changed, and the people in the room have noticed.

1.2 What You Are Now Accountable For

Accountability gets used loosely. Here it means something specific: when things go wrong, you are one of the people who must explain what happened, why, and what the company had done beforehand to prevent it. You may not have chosen the software or configured the systems, but you will still be asked.

It helps to think about the groups who hold a leader to account, because each cares about something different.

Customers care about their data and their service. If Meridian's loyalty app leaks names, addresses, and purchase histories, the 300,000 people in that scheme will want to know whether they are at risk. Trade customers, such as supermarkets, care about continuity: if Meridian cannot ship for a week, shelves have gaps and buyers start looking for a second supplier.

Regulators care about whether the company met its legal duties. Data-protection laws in most countries require organisations to protect personal information with "appropriate" measures and to report serious breaches within short deadlines, sometimes as little as 72 hours. They do not expect perfection, but they do expect evidence that the company took the risk seriously, understood what data it held, and acted reasonably. Chapter 5 looks at the rules in more detail.

Shareholders and lenders care about value and disclosure. A serious incident can hit revenue, raise costs, and, in listed companies, move the share price. In several jurisdictions, listed companies must now disclose material cyber incidents promptly and describe how they govern cyber risk. Even private companies answer to owners, banks, and investors who will ask whether the risk was managed.

Staff care about their own information and their ability to do their jobs. Payroll data, home addresses, and bank details are all personal data. When systems go down, it is staff who sit at idle production lines or field angry calls, and they judge leadership by how calmly and honestly it handles the moment.

Partners and suppliers care about whether a problem at your company becomes a problem at theirs. If Meridian's email is taken over, criminals may use it to send convincing fake invoices to Meridian's own suppliers. Connected businesses share risk whether they like it or not.

This gives you a useful map. For each group you can ask, "What would they lose, and what would they expect us to have done?" What it does not give you is a technical plan, and that is fine. Your job is not to design the controls but to make sure someone competent is designing them, that they are funded sensibly, and that you could comfortably explain the approach to each of these groups.

There is a second layer that is easy to miss: leaders are accountable not only for outcomes but for decisions. If an incident happens despite a reasonable, well-documented approach, most stakeholders, including most regulators, will be understanding. If it happens because a known risk was raised and ignored, or because nobody ever asked the question, the conversation is much harder. You are judged on whether you acted responsibly beforehand, not on whether an intruder ever got in.

In Plain English: Accountability

Think of a restaurant owner. They do not cook every meal or wash every plate, and nobody expects them to. But if a customer gets food poisoning, the owner is the one the health inspector wants to speak to. The inspector will ask simple questions. Did you have rules about hygiene? Did you train your staff? Did you check the fridge temperatures? Cyber accountability works the same way. You are not expected to do the work. You are expected to make sure the work is done.

Here is how this plays out. Imagine two companies of similar size suffer similar break-ins, each exposing customer contact details.

The first can show the regulator a risk register that named the threat, a board minute approving a budget, a security policy, training records, and an incident plan that was followed. The investigation is uncomfortable but short; the company is told to make improvements and is not fined.

The second has none of this. The IT manager had raised concerns twice by email, but they never reached leadership. The press coverage focuses on the ignored warnings, and the board spends months on the fallout.

The technical failure was the same. The leadership story was completely different, and that difference is the subject of this book.

1.3 The Real Cost of a Breach

When people talk about the cost of a cyber incident, they usually quote one large number. Those numbers are real but can feel abstract. It is more useful to break the cost into the units a leader already thinks in: money, time, trust, and attention.

Money is the most visible cost, and it comes from several directions at once: the direct cost of response (investigators, lawyers, communications advisers), lost revenue while systems are down, regulatory fines, legal claims, or contractual penalties for missed delivery commitments to large customers, and the cost of rebuilding systems faster and more expensively than planned. Then come the longer-tail costs: higher insurance premiums at renewal, lost contracts, and the extra security spending approved in a hurry after the event, usually at a premium.

Time is the cost leaders most often underestimate. A serious ransomware attack, where criminals lock up a company's systems and demand payment to release them, typically takes operations offline for days and full recovery for weeks or months, while production schedules slip, orders go unfilled, and staff work around broken processes. For a food company like Meridian, time has a sharper edge: chilled products have short shelf lives. A week without a working planning system is not just a week of lost sales; it can be a week of spoiled stock.

Trust is harder to measure and slower to rebuild. Customers who receive a letter saying their data was exposed may forgive one incident handled honestly; they are less forgiving of evasive communication or a second incident. Trade customers may add contract clauses, demand audits, or quietly diversify their suppliers. Staff, too, lose trust in leadership if they feel the company was careless or that they were kept in the dark.

Attention is the hidden cost. A serious incident consumes the leadership team for weeks: the chief executive on calls with lawyers, insurers, and major customers, the finance team reconstructing records, the board meeting more often. Every hour spent managing the incident is an hour not spent on strategy, growth, or the product launch meant to happen this quarter. For many companies the opportunity cost of distraction is larger than the direct financial loss, although it never appears in the incident report.

In the Boardroom: Putting a Number on a Bad Week

After Graham's question, Daniel asks David something unusual: estimate what a week-long shutdown would cost Meridian in money, before anyone talks about technology.

David returns with a single page. Meridian turns over roughly 3.5 million a week. If the planning and ordering systems went down, some production could continue on paper, but he estimates sales would fall by at least half: around 1.7 million in lost revenue in the first week. Chilled stock that could not be shipped might add another 400,000 in waste. Outside investigators, lawyers, and communications support, based on conversations with the company's insurance broker, could easily reach 500,000. He has not included regulatory fines, lost contracts, or the cost of rebuilding, because he does not yet know how to estimate them.

"So the floor," he says, "is somewhere above two and a half million for a bad week. And that assumes we are back up in a week."

The figure lands differently from any technical briefing. Tom's deferred request from last year, 220,000 to improve backups and add stronger login protection, suddenly looks small. Nobody says so out loud, but everyone is doing the same arithmetic.

Margaret asks one more question. "David, how confident are you in the one-week assumption?" David pauses. "Not very. I asked Tom how long a full restore would take. He said he did not know, because we have never tested one."

That answer goes into the minutes. It will matter later.

The point is not precision; David's number is rough, and he says so. It is that once a cyber risk is expressed in the same language as every other business risk, the leadership team can reason about it: compare the cost of prevention with the cost of disruption, and decide what level of risk it is willing to carry. Chapter 3 shows how to think about risk in money more carefully.

A note of proportion is worth adding. Most incidents are not catastrophes. Many are contained quickly, cost modest sums, and never reach the press, and some large companies have suffered major breaches and recovered fully. The aim is not to frighten anyone into spending, but to understand the shape of the downside clearly enough to make calm decisions about it, the way a sensible board treats fire, fraud, and theft without lying awake about them.

1.4 "We're Too Small to Be a Target"

Of all the sentences heard in boardrooms about cyber risk, this is probably the most common and the most expensive. It has several cousins: "We're not a bank." "We just make sauces." "Nobody would bother with us." It is a natural thing to believe, and for most companies simply wrong.

The reason is that most attacks are not aimed at a particular company. They are aimed at a weakness, wherever it happens to be. Think of a burglar walking down a street at night, trying every car door handle. They are not looking for your car specifically. They are looking for any car that is unlocked. If yours is, they get in. Much online crime works the same way, except that the street has millions of cars and the burglar has automated the walking.

Criminal groups run software that constantly scans the internet for systems with known weaknesses: an unpatched server, a login page without strong protection, a remote-access tool left open. They send millions of deceptive emails, known as phishing, hoping a small fraction of recipients click a link or enter a password. When one succeeds, they look around to see what they have found. A food manufacturer with 450 staff and a 180-million turnover is, from a criminal's point of view, a perfectly good catch: it has money, a payroll, and customer data, and it cannot afford to be offline for long. That last point matters most. The more a company depends on its systems and the less prepared it is to recover, the more likely it is to pay.

There is also a second path to being a target that has nothing to do with your size: who you are connected to. Criminals who want to reach a large retailer may find it easier to go through one of its smaller suppliers. A mid-sized food company with access to a supermarket's ordering systems is a stepping stone. Being small does not make you invisible; sometimes it makes you the side door.

Here are a few general patterns, drawn from the kinds of incidents that appear in the news and in insurance claims every year. None involve famous companies.

A family-owned manufacturer with a few hundred staff has its systems locked on a Monday morning. Production stops across two sites. Recovery takes three weeks, and the company loses a major contract because it cannot meet delivery dates.

A regional distributor's finance team receives an email, apparently from a long-standing supplier, saying the supplier's bank details have changed. The email looks perfect because it was sent from the supplier's real, compromised mailbox. Three invoices are paid to the new account before anyone notices. The money is not recovered.

A small online retailer discovers that its website has been quietly altered to copy customers' card details as they check out. The alteration went unnoticed for four months.

A professional services firm of eighty people has a former employee's account left active after they leave. Months later, that account is used to download client files.

None of these organisations was "interesting." All of them were reachable.

In Plain English: Not Being a Target Is Not a Plan

Think of the houses on a quiet street. Burglars do not choose a house because they have heard of the owners. They choose the house with the open window, the dark porch, or the ladder left in the garden. A modest house with an open window is a better target than a mansion with good locks. In cyber terms, being small and unremarkable does not keep you safe. Closing the obvious windows does.

The good news is significant: if most attacks are opportunistic, most can be discouraged by doing the basics well. Strong login protection, kept-up-to-date systems, tested backups, and staff who know how to spot a suspicious request remove a large share of the opportunities that criminals rely on. You do not need to be impregnable, only a harder target than the next company along, and able to recover if someone gets in anyway.

The phrase "we're too small to be a target" is therefore worth replacing: "We are reachable, like everyone else. What are the obvious open windows, and how quickly could we recover if someone climbed through one?" That question is answerable, and the answer is usually affordable.

For the Experts: Why "Targeting" Is the Wrong Frame for Most Boards

Security professionals distinguish between targeted and opportunistic attacks, and the distinction matters operationally. For board communication, though, it can mislead. Telling a board "we are unlikely to be targeted by a sophisticated actor" is usually true and almost always unhelpful, because the dominant loss drivers for mid-market firms are not sophisticated actors but commodity intrusion paths, credential theft, exposed remote access, unpatched internet-facing services, and payment fraud, executed at scale by groups whose economics resemble volume businesses.

A more useful frame is exposure plus attractiveness to monetisation. Exposure is how many reachable weaknesses you present. Attractiveness is how easily an intruder can convert access into cash: through extortion pressure (downtime intolerance, data sensitivity), direct fraud (payment processes, supplier-change workflows), or resale (access brokers selling footholds to ransomware operators). A food manufacturer with perishable inventory, thin margins, and just-in-time delivery commitments scores high on downtime intolerance, which makes it more monetisable than its sector profile suggests.

Two further nuances are worth carrying into board conversations. First, the access-broker market means initial compromise and final impact are often performed by different parties, sometimes weeks apart: "we were breached by an unsophisticated phishing email" and "we suffered a sophisticated ransomware event" can describe the same incident. Second, industry-level incident statistics are heavily skewed by reporting bias: sectors with mandatory disclosure regimes look worse in breach databases than others, and small firms are under-represented because many incidents never reach a regulator or a journalist. If a board member says "food companies don't get hit much," the honest answer is that the data does not support that confidence either way. Insurance claims data, accessible through your broker, is usually a better guide to mid-market loss patterns than public breach trackers, because it captures incidents never publicly disclosed.

1.5 What This Book Will and Won't Make You

This book will not make you a security expert. It will not teach you how attacks work at a technical level, how to configure a firewall, or which products to buy. That would be a poor use of your time, and it is not what the business needs from you.

What this book will do is help you become a capable owner of cyber risk. By the end, you should be able to do several things with confidence.

You should be able to hold a sensible conversation with your security leader in plain language, knowing which answers should reassure you or worry you; to make decisions about money, telling an investment that reduces risk from one that merely produces reports; to understand the machinery of governance, who owns what, what regulators expect, and how frameworks help you steer; to understand the handful of risks that most often cause real harm, from ransomware and payment fraud to supplier failures and artificial intelligence; and to lead calmly when something goes wrong, because the key decisions were made before the crisis rather than improvised during it.

The book follows that path, from why this lands on your desk, through the machinery of governance and the risks that keep leaders up at night, to what happens when things go wrong and, finally, a practical plan for your first ninety days.

Each chapter uses the four recurring boxes described in the preface: In Plain English, In the Boardroom, For the Experts, and Questions to Ask.

A word on tone. As the preface promised, this is not a book of fear. Cyber risk is serious, but it is a risk like others you already manage: fire, fraud, product recalls, supply disruption. You handle those with a mix of prevention, preparation, insurance, and practice, and cyber risk responds to the same approach. Calm, informed leadership is far more effective than anxious spending.

A week after the board meeting, Daniel calls Tom and Aiko into his office, David's one-page estimate on the table.

"I want to say something first," Daniel begins. "I am not asking this because I think you have done anything wrong. You raised the backup question last year, and we deferred it. That was a leadership decision, and it was mine as much as anyone's."

Tom relaxes. Aiko, at Meridian two years and rarely in the chief executive's office, takes notes.

"What I need," Daniel continues, "is for the board to understand where we stand, in language they can use. Not a list of products. I want three things. What are the main ways we could be seriously hurt? What would each one cost us, roughly? And what would it take to reduce each one to a level we are comfortable with?"

Aiko asks a careful question. "When you say comfortable, who decides what comfortable means?"

Daniel smiles. "A very good question, and I don't think we have an answer yet. I suspect that is the board's job, with our help."

He is right, and Chapter 3 will show why. For now, what matters is the shift in posture: the chief executive has stopped treating security as Tom's problem and started treating it as a business question the leadership team owns together. Nothing has been bought and no policy written, but the most important change has already happened.

Questions to Ask

  • If our main systems stopped working tomorrow morning, how long would it take us to resume taking and shipping orders, and when did we last test that?
  • Who in this company is responsible for cyber risk, and do they have the authority and budget to act on what they find?
  • What are the three most likely ways we could be seriously harmed, described in business terms rather than technical ones?
  • Have any security concerns been raised in the past two years that were deferred or declined, and why?
  • If a regulator asked tomorrow what we had done to protect customer data, what evidence could we show them?
  • Which of our customers, suppliers, or partners could be harmed if our systems were compromised, and have we ever discussed that with them?

Key Takeaways

  • Technology now carries the business, so a threat to the technology is a threat to revenue, reputation, and legal standing. That makes cyber risk a leadership responsibility, not only an IT one.
  • Leaders are accountable to customers, regulators, shareholders, staff, and partners. Each group asks a slightly different question, but all of them want evidence that the risk was taken seriously.
  • You are judged less on whether a break-in happened and more on whether you behaved like a careful owner beforehand: did you ask, fund, decide, and document?
  • The cost of a breach is best understood in four units: money, time, trust, and attention. Time and attention are the ones leaders most often underestimate.
  • "We're too small to be a target" is a misunderstanding. Most attacks are opportunistic and look for weaknesses, not famous names. Closing the obvious open windows removes much of the risk.
  • You do not need to become a technologist. You need to ask good questions, make sensible decisions about money and risk, and prepare to lead calmly if something goes wrong.

What this chapter sets up

We have established why cyber risk now lands on a leader's desk and what is at stake. Meridian has taken its first step: the board has asked a business question, the finance team has put a rough number on a bad week, and the chief executive has asked for a plain-language picture of where the company stands.

But a picture of risk needs a picture of the threat. Before Daniel and the board can decide what is "comfortable," they must understand who might come through the door and what they are after. Is it a lone teenager, an organised criminal gang, a disgruntled employee, a foreign government, or simply a well-meaning member of staff clicking the wrong link on a busy afternoon?

Chapter 2 answers that question in business terms. It introduces the main kinds of attacker, explains why most are motivated by money, and shows that the criminals who target companies increasingly run themselves like companies, with specialists, suppliers, and customer service. It translates each kind of threat into the units a leader cares about: revenue, downtime, fines, and headlines. You will not need any technical knowledge to follow it. You will simply need to want to know how burglars, con artists, and careless visitors actually behave.

KEY POINTS

Key points

  • Ask how long it would take to resume taking and shipping orders if your main systems failed tomorrow, and when that was last tested.
  • Name who is responsible for cyber risk and confirm they have the authority and budget to act.
  • Estimate in money what a one-week shutdown would cost before discussing technology.
  • Review security concerns deferred or declined in the past two years, and record why.
  • Make sure you could show a regulator evidence of what you did to protect customer data.
  • Replace the assumption that you are too small to be targeted with a list of obvious weaknesses and a realistic recovery time.

QUESTIONS

Common questions

Why is cybersecurity a board-level responsibility?
Because technology now carries the business: orders, production, payroll and customer records all depend on systems, so a threat to those systems is a threat to revenue, reputation and legal standing. Regulators, investors and large customers increasingly ask how cyber risk is governed, and those questions land with senior leaders. The Boardroom Firewall argues that leaders are judged on whether they asked, funded, decided and documented before an incident.
How should executives estimate the cost of a cyber incident?
Break the cost into four units: money, time, trust and attention. Money covers response fees, lost revenue, fines and penalties; time covers days of downtime and weeks or months of recovery; trust affects customers, trade partners and staff; and attention is leadership time diverted from strategy. Even a rough estimate of what a bad week would cost lets leaders compare the cost of prevention with the cost of disruption.
Are small and mid-sized companies really targets for cyber attacks?
Yes. Most attacks are opportunistic and search for weaknesses rather than famous names, using automated scanning and mass phishing emails. A mid-sized firm with money, a payroll, customer data and little tolerance for downtime is an attractive target, and smaller suppliers can be used as a route into larger customers. Doing the basics well removes much of that opportunity.
What do regulators look for after a data breach?
They generally do not expect perfection. They look for evidence that the company took the risk seriously, understood what data it held and acted reasonably. Records such as a risk register, board minutes, policies, training records and an incident plan that was actually followed make a strong difference, while a breach that follows ignored warnings is judged far more harshly.
What basic controls stop most opportunistic cyber attacks?
According to The Boardroom Firewall, strong login protection, keeping systems up to date, backups that have been tested by actually restoring them, and staff who can spot suspicious requests remove a large share of the opportunities criminals rely on. The goal is not to be impregnable but to be a harder target than the next company and able to recover quickly if someone gets in.