Skip to content
Template · free to view · download is Pro

CISO Board Deck Template

Ten slides for the quarterly cyber update to the board or one of its committees. Each slide says what it is for, what goes on it, what to say, an example line and the mistake that trips people up. Part of the CISO Resource Bundle.

Educational template. Example wording is illustrative; replace every placeholder with your own facts and agree anything about incidents or regulation with your legal team first.

CISO Board Deck Template

A ten-slide outline for a quarterly cyber update to the board or its risk or audit committee. Each slide has its purpose, what goes on it, speaker notes, example wording and the mistake to avoid. Replace every placeholder with your own facts. Keep the main deck to ten slides and put the detail in the appendix.

01Before you build the deck

  • Ask the chair or committee secretary what the board wants from this session: information, a decision, or both.
  • Check how much time you have. Plan for half of it to be questions.
  • Agree the risk appetite statement and thresholds you will report against. If there is none, that is your first ask.
  • Pre-brief the CEO, CFO and general counsel so nothing on the slides surprises them.
  • Send the deck in the board pack ahead of time, so the meeting is for discussion, not reading.
Meeting
Board / risk committee / audit committee, date
Time on the agenda
Minutes
Decisions you need
List them. If none, say this is for information

02Slide 1: Risk posture headline

One slide that answers the question every director has: are we inside the risk appetite you set, and is it getting better or worse?

  • A one-line verdict on posture against appetite: inside, near the edge, or outside.
  • The direction since last quarter, with the one or two reasons.
  • The decisions you will ask for later in the deck.

Speaker notes: Say the verdict first, then the reason. If the board only remembers one slide, it should be this one.

Example wording: "We are inside appetite on four of our six top risks. Ransomware recovery and third-party access are above tolerance. I will ask you to approve funding for the first and accept the second for one more quarter."
Common mistake: Opening with the threat landscape or a list of attacks blocked. The board wants your organisation's position, not the internet's.

03Slide 2: Top risks in business terms

Show the handful of cyber risks that could hurt the business most, written as business outcomes.

  • Five to seven risks, each phrased as an outcome: "We cannot ship orders for n days", not "EDR gaps".
  • For each: current rating, appetite threshold, trend, owner.
  • Where you can, a loss range with its source and method stated.

Speaker notes: Link each risk to a business process the directors know. Name the executive owner, not just security.

Example wording: "Risk 2: a ransomware attack stops order processing. Current: high. Appetite: medium. Trend: improving, because offline backups now cover the order system."
Common mistake: Listing technical findings or control gaps as risks. A gap is a cause; the risk is what happens to the business.

04Slide 3: Incidents and near misses

Tell the board what happened this quarter that matters, and what you learned.

  • Material or notable incidents, with impact and status.
  • Near misses that show a weakness, even if no harm was done.
  • What changed as a result.

Speaker notes: Be plain about what went wrong. Boards lose trust when they hear about an incident from the press first. Agree with counsel beforehand how incidents under legal privilege are described.

Example wording: "One notable incident: a supplier's stolen password was used to reach our ticketing system. No customer data left. We have since required multi-factor sign-in for every supplier account."
Common mistake: Showing a count of incidents or alerts with no severity or context. A bigger number can mean better detection, not worse security.

05Slide 4: Metrics and trend

A few metrics that each map to a decision, shown as a trend against a target.

  • Six to eight metrics, mixing leading (coverage, patch time) and lagging (incidents, time to respond).
  • Several periods of trend, with red, amber or green against an agreed threshold.
  • One line on what moved and why.

Speaker notes: Lead with any metric that breaches appetite. Use the board metrics template to pick the set.

Example wording: "Critical internet-facing vulnerabilities fixed within 14 days: 71%, 80%, 88% over three quarters. Target 95%. On track for next quarter."
Common mistake: Vanity metrics: blocked emails, total alerts, number of tools. They map to no board decision.

06Slide 5: Programme progress against plan

Show whether the security programme the board funded is delivering.

  • The three to five main initiatives, each with planned versus actual milestone and status.
  • What the initiative reduces: which top risk it moves.
  • Anything late, why, and the recovery plan.

Speaker notes: Tie each initiative back to a risk on slide 2. Say plainly what is late.

Example wording: "Identity programme: phishing-resistant sign-in rolled out to 60% of staff against a plan of 75%. Delay: a legacy finance system. Recovery: vendor upgrade booked for month."
Common mistake: A project status report with dozens of rows. The board needs the few that move risk.

07Slide 6: Investments and asks

Ask for money, people or a decision, with the risk it reduces and the option of doing nothing.

  • Each ask: what, how much, which risk it reduces and by how much (with method).
  • Two or three options, including doing nothing and its consequence.
  • How spending compares with plan this year.

Speaker notes: Put the ask in the CFO's language. Show the do-nothing option honestly: it is a legitimate choice the board can make.

Example wording: "Option A: cost to add immutable backups for the order system, moving ransomware recovery from high to medium. Option B: do nothing and accept a recovery time of n days."
Common mistake: Asking for budget with fear and no options. A board can only weigh choices it is shown.

08Slide 7: Regulatory and compliance

What the organisation must do, where it stands, and what is changing.

  • Obligations in force (for example disclosure rules, sector regulation, contracts) and status.
  • Audit and assessment findings still open, with dates.
  • New or changing rules on the horizon and their effect.

Speaker notes: Agree wording with legal and compliance before the meeting. Separate "we must" from "we choose to".

Example wording: "Two audit findings remain open from the year external audit; both close by date. A new reporting rule takes effect in month; our incident process already meets its timeline."
Common mistake: Listing every framework you map to. The board cares about obligations, exposure and dates.

09Slide 8: Third-party risk

Show the suppliers whose failure would hurt you most and how they are managed.

  • Critical suppliers by business impact, and whether each was assessed in the last year.
  • Supplier incidents this quarter and how they affected you.
  • Concentration risk: several critical services depending on one provider.

Speaker notes: Many incidents now start at a supplier. Show that you know which ones matter and what you would do if one failed.

Example wording: "Of our n critical suppliers, n were assessed this year. Two hold customer data without a current independent assurance report; we have asked for one by date."
Common mistake: Reporting the number of questionnaires sent. Coverage of critical suppliers is what matters.

10Slide 9: Decisions needed

Repeat the decisions you need, so the minutes can record them.

  • Each decision as a yes or no question.
  • Your recommendation and the alternative.
  • What happens next once the board decides.

Speaker notes: Read each decision out and pause. Ask the chair to record the outcome. If the board defers, ask when it will decide.

Example wording: "Decision 1: approve cost for immutable backups (recommended). Decision 2: accept third-party access risk above tolerance until date, with monthly reporting to the risk committee."
Common mistake: Ending on "questions?" with no decision recorded. Accepted risk should be minuted as accepted.

11Slide 10: Appendix

Detail for directors who want it, without taking meeting time.

  • Full metric definitions and data sources.
  • The complete risk register extract.
  • Method behind any loss estimate.
  • Glossary of terms used in the deck.

Speaker notes: Refer to the appendix when a question goes into detail. Do not present it.

Example wording: "The method for the loss ranges on slide 2 is in appendix A3. Happy to walk anyone through it after the meeting."
Common mistake: Moving everything into the main deck. If a slide does not support a decision or the headline, it belongs here.

12Mistakes across the whole deck

  • Jargon and acronyms. If a director has to ask what it means, rewrite it.
  • Fear without options. Every concern should come with a choice the board can make.
  • Numbers with no source. Say where each figure comes from and how it was worked out.
  • Good news only. Boards notice, and it costs you credibility when something goes wrong.
  • Too many slides. Ten is plenty for the main deck.
  • Surprises. Anything awkward should be pre-briefed to the chair and executives.
After the meeting, write down the questions directors asked. They tell you what the next deck should answer up front.

Practise the room

The deck is half the job; the questions are the other half. Rehearse them in the Audit Committee Q&A Lab, and pick the metrics for slide 4 in the Board Metrics Selection Lab.

TL;DR

What this template is

5 points
  • A ten-slide outline for a quarterly cyber update to the board, risk committee or audit committee.
  • Slides: risk posture headline, top risks in business terms, incidents and near misses, metrics and trend, programme progress, investments and asks, regulatory and compliance, third-party risk, decisions needed, appendix.
  • Every slide has its purpose, what goes on it, speaker notes, example wording and the most common mistake.
  • Free to read here. Copy and Markdown download are Pro; paste the outline into your own slide software.
  • Practise the questions directors ask in the Audit Committee Q&A Lab.

Frequently asked questions

What should a CISO present to the board?

Where the organisation stands against the risk appetite the board set, the top risks in business terms, notable incidents and what was learned, a few metrics as trends, progress on the funded programme, the investments and decisions you need, regulatory status and third-party risk. This template puts those in ten slides, with the detail in an appendix.

How many slides should a board cyber update have?

Keep the main deck short: this template uses ten, including the appendix. Board time is limited and plenty of it should go to questions. Put definitions, the full risk register and methods in the appendix and send the deck ahead of the meeting.

How do I explain cyber risk to a board in business terms?

Phrase each risk as what would happen to the business: orders stop, customer data is exposed, a regulator investigates. Give the current rating against the appetite threshold, the trend and the executive owner. Add a loss range only if you can state its source and method.

Which metrics belong in a board deck?

Six to eight that each map to a board decision and are shown as a trend against a target, mixing leading and lagging measures. Avoid vanity numbers such as blocked emails or total alerts. The Board Cyber Metrics Dashboard template has a curated set.

Can I download this as slides?

You can copy the outline or download it as Markdown with Pro, then paste each section into your own slide software. Reading the whole template here is free.