A governance book, not a technical manual
The book is aimed at the people who carry the consequences of cyber risk: chief executives, directors, founders and senior leaders in finance, operations, legal and risk. Its premise is that cyber risk sits in the same family as financial, legal and physical risks such as a warehouse fire. It can halt operations, cost real money and erode customer trust built over years, and when it materialises people will ask what the leaders knew, what they decided and what they did.
Many capable executives disengage when security comes up, faced with unfamiliar vocabulary, vendor acronyms and alarming headlines. The author's answer is one recurring image: running a connected company is like owning a large building. Nobody expects the owner to be a locksmith or an electrician. The owner's job is to see that guards, rules about keys, maintenance, insurance and fire drills are in place, and that the right questions are being asked.
The book deliberately leaves out how to configure systems or investigate attacks. Attacks are described at the depth of a good newspaper, then the discussion turns to what a leader should do about them. It also avoids fear as a motivator: most of what protects a company is ordinary, affordable and well understood, and the hard part is making sure it is done and keeps being done. It is not legal advice; it aims to prepare readers for better conversations with their lawyers, auditors and insurance brokers.
Who the book is written for
The intended reader is a decision-maker used to working with incomplete information, who did not choose a career in technology but keeps finding security on the desk: a customer's long questionnaire, an insurer asking about multi-factor authentication, new disclosure rules, or a peer company shut down for two weeks. That reader wants to know whether security money goes to the right places, who is responsible for what, and whether they would lead well rather than improvise on a bad day.
Smaller companies with no security department are explicitly included. The author argues that the principles scale down, so a company of fifty people can govern cyber risk well with a handful of habits and a few clear decisions. Some of the costliest incidents he has seen hit companies that believed they were too small to be of interest.
A second audience is CISOs, risk officers, internal auditors and technical leaders who have to explain all this upward. For them the book offers language and metaphors that land with non-technical colleagues, plus For the Experts boxes on finer points such as framework limits, risk quantification and regulatory detail. Writing as a founder and engineer who has sat on both sides of the table, the author traces most trouble to the language gap between technical staff and the leaders who control the budget.
How the book is organised
Sixteen chapters are grouped into five parts: why cyber risk reaches a leader's desk; the machinery of governance (roles, regulation, frameworks and budget); the risks that keep leaders awake (suppliers, cloud, artificial intelligence and people); the bad day itself (ransomware, incident response, insurance and board reporting); and a practical plan. Chapter 16 and Appendix G set out the 90-Day Board Cyber Action Plan, a week-by-week programme. Readers can go straight through or dip into the chapter they need, such as insurance before a renewal.
A fictional company, Meridian Foods, runs through every chapter. It has about 450 staff making sauces, snacks and chilled ready meals, a loyalty app, two production sites, a distribution centre, several cloud systems, an outside IT provider and a board that meets quarterly. The reader is cast as one of its senior leaders. Using a fictional firm allows uncomfortable decisions to be examined honestly without turning lessons into blame of real companies.
Four kinds of box recur: In Plain English restates ideas with everyday analogies; In the Boardroom shows short scenes at Meridian; For the Experts goes deeper for specialists; and Questions to Ask closes each chapter with four to six questions for the next meeting. Seven appendices are meant to be used: a board question bank, a one-page dashboard template, a ransomware tabletop exercise, a glossary of around fifty terms, a guide to standards, a breach materiality worksheet and the 90-day plan.
Read it with your own company in mind
The author suggests reading with a pen and testing each idea against your own organisation: is this true where I work, who would know, and what would I want to find out? The value of the book lies less in what it says than in the conversations it prompts afterwards.
KEY POINTS
Key points
- Put cyber risk on the leadership agenda as a business risk, alongside financial and legal risk.
- Aim to become a confident owner of the risk, not a technologist.
- Apply the building-owner test: are the right people, rules and questions in place?
- Avoid fear-driven spending; most effective protection is ordinary and affordable, and the challenge is doing it consistently.
- Take each chapter's Questions to Ask into your next meeting with your security team, IT provider, insurer or board.
QUESTIONS
Common questions
- Who is The Boardroom Firewall written for?
- It is written for chief executives, board members, founders and senior leaders in finance, operations, legal and risk who are accountable for cyber risk but are not technologists. It also serves CISOs, risk officers and auditors who need to explain cyber risk to boards in plain language. Smaller companies without a security department are explicitly included.
- Do executives need technical knowledge to manage cyber risk?
- No. The Boardroom Firewall argues that leaders need judgement and confidence rather than technical skill. Like the owner of a large building who is not expected to be a locksmith, an executive's role is to make sure the right people, rules and questions are in place.
- Is The Boardroom Firewall a substitute for legal advice on cyber regulation?
- No. Where the book touches law, regulation or insurance, it describes the landscape in general terms so that leaders know which questions to bring to their own lawyers, auditors and insurance brokers. Those advisers know the details for a particular country, sector and set of contracts.
- What is Meridian Foods in The Boardroom Firewall?
- Meridian Foods is a fictional mid-sized food company with about 450 staff that serves as the running case throughout the book. It makes sauces, snacks and chilled ready meals and has a loyalty app, two production sites, a distribution centre and a quarterly board. The author uses a fictional company so that difficult decisions can be examined honestly without blaming real organisations.
- Does the book include a practical cyber action plan for boards?
- Yes. Chapter 16 and Appendix G set out the 90-Day Board Cyber Action Plan, a week-by-week programme a leadership team can start as soon as it finishes the book. The appendices also include a board question bank, a one-page dashboard template, a ransomware tabletop exercise and a breach materiality worksheet.