Cyber Security for Boards: The Director's Guide to Cyber Resilience, Risk and Control

Share

Who this guide is for

This guide is written for chairs, non-executive directors, managing directors and board committee members who are accountable for how an organisation handles cyber risk, without necessarily holding a technical background. It sets out what the board owns, what it should delegate, and what good evidence looks like.

What the board is actually responsible for

A board is not responsible for running security. It is responsible for whether cyber risk is being managed in a way that is proportionate to the business, and for being able to demonstrate that judgement was applied. In UK listed and large private companies, this sits inside the wider duty to maintain a sound system of internal control and risk management, as set out in the UK Corporate Governance Code.

• Setting risk appetite for disruption, data loss and third-party exposure.
• Confirming that cyber risk is treated as a business risk with named executive ownership.
• Assuring that continuity and recovery plans exist, are funded and have been tested.
• Understanding the material scenarios: extended outage, data theft, supplier failure.
• Ensuring the organisation can meet its notification duties to regulators, customers and insurers.

The decisions you own, and what you can delegate

Directors get into trouble when they delegate the judgement as well as the work.

• Own risk appetite, investment trade-offs, crisis decision-making authority, and whether the residual risk being carried is acceptable.
• Own the decision on whether the organisation would pay a ransom, taken calmly and in advance.
• Delegate control selection, architecture, tooling and day-to-day operations to the executive.
• Delegate technical assurance, but require the results to reach the board in plain language.

The risks a director should understand

• Operational disruption. The cost is usually the outage, not the data. Model the loss per day.
• Recovery dependency. Backups that depend on the same identity platform as the live estate can be reached by the same attacker.
• Third-party exposure. Suppliers and maintenance access are a common route in, and their incidents become your incident.
• Data exposure. Personal data losses attract regulatory attention under UK GDPR, and the reputational cost often exceeds the fine.
• Concentration. A single cloud tenancy or a single administrator group can be a single point of failure for the whole business.

The questions to ask management

1. Which processes must survive, and how long can each be down before the damage is material?
2. If our identity platform were compromised tonight, what would we still be able to restore, and from where?
3. When did we last restore a critical system from scratch, and how long did it take?
4. Which suppliers hold live access into our systems, and who reviews that access?
5. What would we do in the first four hours, and who is authorised to disconnect systems?
6. What are we deliberately choosing not to protect, and does the board accept that?

The evidence to expect

Ask for artefacts, not assurances.

• A tested recovery plan with dates, durations and named owners.
• Results of the most recent restore test, including what failed.
• A short register of critical suppliers and their access rights.
• An incident response plan that works when email and the intranet are unavailable.
• Independent assurance, whether internal audit, an accreditation such as ISO/IEC 27001, or an external review.

What good looks like from the board seat

• Cyber risk appears in the same register, and the same language, as every other principal risk.
• Recovery times are stated as business outcomes, not technical metrics.
• The organisation has rehearsed a crisis at board level within the last twelve months.
• Reporting shows trend and exception, not volume of blocked attacks.

What happens when preventative controls fail

Prevention buys time. It does not remove the need to answer a simple question: if an attacker holds your identity platform and your management console tonight, what still works tomorrow morning? Most organisations discover that their backup catalogue, their recovery credentials and their runbooks all depend on the systems that have just been taken. That is the dependency worth removing first.

No control removes the possibility of a serious incident. The realistic goal is a smaller blast radius, a recovery path that does not depend on the compromised estate, and evidence that both were tested.

Deciding what you actually need

The board question is not which product to buy. It is whether the organisation can still operate and recover when its normal controls have been defeated, and whether the cost of closing that gap is proportionate. Firevault is the company. It provides three distinct things, and the honest answer is often that you need one of them rather than all of them.

• Offline Secure Storage® holds a defined set of critical records and clean recovery data physically disconnected from the live estate. It is a protected set, not a replacement for your backup infrastructure.
• Control Modules are a suite of nine purpose-built tools and techniques that give you physical control over the paths into and across your estate. Introduce only the modules that map to the risk you are treating.
• Control Blueprints are proven combinations of those modules assembled for a named outcome, such as containing a live breach or governing third-party access.

If your existing controls already deliver a tested recovery path that survives the compromise of your identity and management planes, and you can evidence it, you may not need any of this. Test that assumption before you buy anything. If you are unsure which of the three applies, the Firevault Concierge walks through the question set without a sales conversation.

The Control Blueprints most relevant to this role

A board does not need to specify controls, but it helps to know what the executive is choosing between. Control by Firevault is a set of nine Control Modules, grouped into the FIRE layer (Firebreak, Isolate, Relay, Execute) and the VAULT layer (Validate, Archive, Unlink, Lock, Transfer). Seven Control Blueprints combine those modules for a specific outcome. You do not need all nine modules, and most organisations start with one blueprint.

• CP-01 Stop Kill-Chain Ransomware uses Firebreak, Isolate, Execute. Read the stop kill-chain ransomware guide.
• CP-02 Contain Active Breaches uses Firebreak, Isolate, Execute. Read the contain active breaches guide.
• CP-03 Control Third-Party Access uses Validate, Relay, Lock. Read the control third-party access guide.
• CP-05 Protect Critical Infrastructure uses Firebreak, Isolate, Relay, Execute. Read the protect critical infrastructure guide.
• CP-06 Prove Compliance Through Control uses Validate, Lock, Archive. Read the prove compliance through control guide.

The full set is on the Control overview and the Control Blueprints index.

Where to go next

Finance leaders should read the CFO guide to cyber risk and financial resilience. For the assurance and evidence view, see the cyber risk and compliance guide. The leaders playbook covers the crisis rehearsal in more depth.

Sources and further reading

• NCSC Cyber Security Board Toolkit
• FRC UK Corporate Governance Code
• ICO guidance for organisations
• NIST Cybersecurity Framework 2.0
• NIS2 and the UK equivalent regime explained

About this guide

Author Mark Fermor, Firevault. Reviewed by Firevault advisory board. Last reviewed 28 August 2026.

This guide draws on primary regulatory and technical sources together with Firevault's own field work on physical isolation and offline recovery. It is guidance, not legal advice. Where a legal or regulatory duty is in question, take advice on your own circumstances.

Other guides in this series are listed on the role guide hub.

How Firevault would handle this

A recovery copy an attacker cannot reach

Offline Secure Storage® keeps a clean copy of your data on hardware that is physically disconnected, so backup and recovery do not depend on systems an intruder can touch.