Cyber Risk Reporting for the Board: Metrics, Risk Map, and Decision Requests by Quarter

Business & Strategy

Cyber Risk Reporting for the Board: Metrics, Risk Map, and Decision Requests by Quarter

Advanced | 4 whiteboard pages · Task board: 5 columns (4 parent tasks, 12 subtasks)

Advanced: Assumes you know the technical terms and methods, and the steps are only outlined. Work through it on your own, guided by decision criteria and points to check.

Cyber risk reporting for the board turns a technology briefing into a decision request: what stops the business, what it costs, and which response to choose. A CISO or head of IT can gather the material and reuse the same format each quarter. Pick six metrics you can compare with last quarter, such as multi-factor authentication coverage, days to apply critical patches, and recovery test results, and sort the risks by impact and likelihood. Then add a recommended option and its cost from the four risk responses and narrow the board's decision to one to three items. Before you present, check for blocked-attack counts passed off as results, jargon, promises of zero risk, and briefings that end without asking for a decision. The whiteboard has 4 pages: set the purpose, surface metrics and risks, narrow the decision, and run it every quarter. The task board has 5 columns, 4 parent tasks, and 12 subtasks.

0 Likes 0 Copies Author: WeProcess
cyber risk reporting board reporting security metrics risk management executive briefing
Sign up free and use this template

Once you have a free account, you can copy this template from the marketplace

Whiteboard preview

Read the whiteboard text as plain text

Cyber Risk Board Report

How to use (4 pages): ① Write the audience and purpose and answer the four questions (boards①–⑤) → ② Compare six metrics with last quarter and check the traps (boards⑥–⑨) → ③ Place risks by impact and likelihood and narrow the decision (boards⑩–⑫) → ④ Assign owners and dates and set the report flow (boards⑬–⑮)

1/4 Set the purpose

① Purpose of the Report (start here)

  • Who you report to e.g. The board (8 people including 2 outside directors). 15 minutes on the agenda
  • A first guess at the decision (one item; narrow it in ⑫) e.g. Whether to approve an investment that speeds up recovery of the order system
  • Next report date and last quarter's homework e.g. The last board meeting of next quarter. Last time we were asked to "show how many days recovery takes"

② Current Answers to the Executives' Four Questions

Current answer (1 line) Evidence (what you checked) Confidence (high / medium / low)
Biggest risk e.g. Ransomware stopping the order system e.g. System asset register and public cases of breaches at peers e.g. Medium
Business impact e.g. A 3-day stop delays about $800,000 in sales e.g. Sales team's daily order records e.g. Medium (verify the estimate with finance)
Level of preparedness e.g. 4 of 5 critical systems restored in a recovery test e.g. Recovery test records (figures in ⑥) e.g. High
Effect of investment e.g. The authentication upgrade approved last quarter is complete e.g. Admin console totals for authentication (figures in ⑥) e.g. High

③ Speak in Business Terms

  • Say it in days of downtime, money, and the effect on customers
  • Move technical names and details to an appendix
  • e.g. Not "3 weaknesses" but "1 unfixed weakness in the order system"

④ Show It Against Last Quarter

  • Present the same metrics in the same order every quarter
  • Add one line on the change from last quarter and why
  • e.g. Systems restored in the recovery test went from 2 of 5 to 4 of 5. The last one is next quarter

⑤ Put the Decision Request First

  • Write the decision request at the start of the deck
  • Set out the options, the recommended one, the cost, and the remaining risk
  • e.g. Start with "Please approve a review of the insurance coverage limit"

2/4 Surface metrics and risks

⑥ Six Metrics That Answer ② (Compare Last Quarter with This Quarter)

Last quarter This quarter Meaning for the business
Multi-factor authentication coverage e.g. 72% of all employees e.g. 91% (100% of administrators) e.g. Fewer ways in for account takeover. SMS codes are weaker than authenticator apps or passkeys, so keep migrating
Critical patches applied e.g. 21 days from release to patch e.g. 9 days e.g. Weaknesses stay open less than half as long
Recovery test results e.g. 2 of 5 critical systems restored e.g. 4 of 5 e.g. More coverage against a long outage
Detection to containment e.g. 6 hours on average e.g. 2 hours on average e.g. Better odds of stopping an attack before it spreads
Third-party checks e.g. 40% of key vendors e.g. 75% e.g. Better prepared for harm that reaches us through a partner
Expected loss from downtime e.g. About $800,000 for a 3-day stop e.g. About $800,000 (unchanged) e.g. Sales delayed if the order system is down 3 days. At 1 day the loss would be about $270,000 (estimate with finance)

⑦ Trap: Counts Passed Off as Results

  • What happens: e.g. You report "120,000 emails blocked" and it is read as more is safer. A rise or a fall tells nobody anything
  • How to check: e.g. For each number in the deck, see if you can say in a few words whether a rise is good or bad
  • How to prevent it: e.g. Move counts to the appendix and keep the rates, days, and amounts from ⑥ in the body

⑧ Trap: Strings of Jargon

  • What happens: e.g. Acronyms pile up and the deck asks for approval with no questions asked
  • How to check: e.g. Ask someone outside technology to read the draft and mark the words they do not understand
  • How to prevent it: e.g. Replace terms with their effect on the business and explain the ones you keep in the appendix

⑨ Trap: Promising Zero Risk

  • What happens: e.g. You say "this investment means no more incidents" and lose trust when one happens
  • How to check: e.g. Search the deck for "complete," "zero," and "always prevents"
  • How to prevent it: e.g. Write the risk that remains after the measure and a rough recovery time if it happens

3/4 Narrow the decision

⑩ Four Ways to Respond to Risk (place the risks from ② and ⑥ on ⑪, then start with the high-impact ones)

Accept Keep it
  • When impact is small or a fix costs more than it saves, record the risk and accept it
  • e.g. Accept a short outage of the staff bulletin board. Review next quarter
Reduce Lower it
  • Invest in measures that lower likelihood or impact
  • e.g. Move administrator accounts to phishing-resistant sign-in such as passkeys (about $20,000)
Transfer Shift it
  • Shift part of a loss through insurance or contracts. Accountability does not transfer
  • e.g. Review the cyber insurance coverage limit (check current terms with the insurer)
Avoid Stay clear
  • Stop or change the activity that creates the risk
  • e.g. Shut down an unused internet-facing server

⑪ Risk Register (sort the risks from ② and ⑥ by impact × likelihood)

Vertical axis: Business impact (higher = bigger) / Horizontal axis: Likelihood (further right = higher)

  • High impact, unlikely Consider transfer or reduction and review once a year. e.g. A long outage at a main site, covered by insurance and a backup site
  • High impact, likely Top priority for reduction or avoidance, and raise it for a board decision. e.g. Ransomware stops the order system
  • Low impact, unlikely Accept and record it, and review next quarter. e.g. A short outage of the staff bulletin board
  • Low impact, likely Reduce it within the department budget and report only the trend. e.g. Suspicious sign-in attempts on employee accounts

⑫ What You Need the Board to Decide (narrow ⑩ and ⑪ to one to three items)

  • What you need decided e.g. Whether to approve an investment (about $170,000) that cuts recovery of the order system from 3 days to 1
  • Options and the recommended one e.g. Reduce (recommended), transfer (raise insurance coverage), accept (leave as is). Also write the expected loss that remains if accepted
  • Trap: reporting without asking for a decision What happens: e.g. It ends with "noted," and no budget or owner is set How to check: e.g. Does the first page of the deck have "what we need decided"? How to prevent it: e.g. Add the deadline for deciding and the risk that remains if nobody decides

4/4 Run it every quarter

⑬ Turn the Decisions from ⑫ into Owners and Deadlines

What was decided Owner Due date Figure to show in the next report
Decision 1 e.g. Approve the investment to cut recovery to 1 day e.g. Head of IT e.g. End of next quarter e.g. Time to restore in a recovery test
Decision 2 e.g. Review the insurance coverage limit e.g. Head of Administration e.g. Within 2 months e.g. Coverage scope and the deductible that remains
Decision 3 e.g. Shut down unused internet-facing servers e.g. IT section manager e.g. Within 1 month e.g. Servers shut down and servers remaining
Carried over e.g. How to check third parties e.g. Procurement e.g. Re-propose at the next report e.g. Share of vendors whose checks are done

⑭ Quarterly Reporting Flow (run it in the same order every quarter)

  1. Gather Week 1 of the quarter's last month e.g. Collect the six metrics in ⑥ from the register, admin consoles, and recovery test records
  2. Draft Week 2 e.g. Condense it to one page in the format of ⑮ and update the answers to the four questions in ②
  3. Pre-brief Week 3 e.g. Show it to the sponsoring executive and the finance lead in 15 minutes and fix how the decision request is worded
  4. Report and record Day of the board meeting e.g. Write the decisions in ⑬ and check the minutes record them

⑮ The One-Page Report Format (write it in this order every quarter)

  • Top: conclusion and decision request (condense ⑫ to one or two sentences) e.g. The biggest risk is an order system outage. We ask you to approve an investment that cuts recovery to 1 day
  • Middle: metric changes and meaning (pick up to three from ⑥) e.g. Multi-factor authentication rose from 72% to 91% and recovery tests from 2 to 4 of 5. We are better prepared for takeover and long outages
  • Bottom: remaining risks and next steps e.g. Vendor checks are at 75%. We will check the rest next quarter and report

Task board contents

Gathering material 16 items

Set the purpose

On page 1, write who you report to and what you need decided, then line up your current answers to the four questions executives ask. This sets the bar for choosing metrics and risks on page 2. Press Ctrl+F (⌘F on Mac) and enter "3/4" to jump to page 3.

Open the last deck

Open last quarter's board deck and minutes, and write on board ① the audience, a first guess at the decision, and the next report date with last quarter's homework. Done when the three notes are filled in, in about 15 minutes.

Answer 4 questions

In the table on board ②, write the current answer, evidence, and confidence for each of the four questions executives ask. Keep any answer with no evidence, marked low confidence.

Align the framing

Rewrite the examples on boards ③ to ⑤ in your company's words. Done when the person reporting and their manager agree on the framing.

Metrics and risks

On page 2, compare six metrics against last quarter and check for the traps that make a report fail to land. Once you can say what each number means, page 3 can narrow to decisions.

Collect six metrics

In the table on board ⑥, enter last quarter's and this quarter's figures from the asset register, admin consoles, and recovery test records. Write "not measured" for any you cannot collect and make it next quarter's task.

Write what it means

In the "Meaning for the business" column of board ⑥, write in one line whether each change is good or bad for the business. Done when all six rows are filled.

Check the traps

On boards ⑦ to ⑨, check your draft for emphasized counts, strings of jargon, and zero-risk promises, and rewrite as the "how to prevent it" lines say.

Narrow the decision

On page 3, sort the risks and narrow what the board must decide to one to three items. This is the heart of the report, and if it stays vague the meeting ends as a briefing.

Map the risks

On board ⑪, place the risks from ② and ⑥ by impact and likelihood. Risks in "high impact, likely" become candidates for a decision.

Compare 4 responses

On board ⑩, write the accept, reduce, transfer, and avoid options and their costs for each candidate risk, and pick one recommended option.

Write the request

On board ⑫, write what you need decided with the options and the recommended one, and use the last note to check the report does not end as a briefing only.

Run it quarterly

On page 4, give each decision an owner and a due date so you can report in the same format next quarter. Track decisions in the "Tracking decisions" column of the task board.

Set owners and dates

On board ⑬, write what was decided, the owner, the due date, and the figure to show in the next report. Done when every owner has been told.

Plan the report flow

In the four steps of board ⑭, write the weeks that fit your own meeting calendar and assign owners for gathering, drafting, pre-briefing, and reporting and recording.

Write a one-pager

Using the format on board ⑮, build a one-page report with the top, middle, and bottom sections filled in. Done when the executive sponsor has reviewed it in advance.

Drafting 0 items

Pre-briefed 0 items

Reported 0 items

Tracking decisions 0 items

← Back to templates

Preview mode Cyber Risk Reporting for the Board: Metrics, Risk Map, and Decision Requests by Quarter

Whiteboard preview

① Purpose of the Report (start here) ② Current Answers to the Executives' ... ③ Speak in Business Terms ④ Show It Against Last Quarter ⑤ Put the Decision Request First ⑥ Six Metrics That Answer ② (Compare ... ⑦ Trap: Counts Passed Off as Results ⑧ Trap: Strings of Jargon ⑨ Trap: Promising Zero Risk ⑪ Risk Register (sort the risks from ... High impact, unlikely High impact, likely Low impact, unlikely Low impact, likely ⑫ What You Need the Board to Decide (... ⑬ Turn the Decisions from ⑫ into Owne... ⑭ Quarterly Reporting Flow (run it in... ⑮ The One-Page Report Format (write i... Cyber Risk Board ... How to use (4 pag... Purpose and decis... Rules and metrics Traps and remaini... Meaning and next ... 1/4 Set the purpose Ctrl+F / ⌘F : 2/4... → 2/4 2/4 Surface metrics a... ↙ 3/4 Who you report toe.g. The board (8 people including 2 outside directors). 15 minutes on the agenda A first guess at the decision (one item; narrow it in ⑫)e.g. Whether to approve an investment that speeds up recovery of the order system Next report date and last quarter's homeworke.g. The last board meeting of next quarter. Last time we were asked to "show how many days recovery takes" Current answer (1... Evidence (what yo... Confidence (high ... Biggest risk e.g. Ransomware stopping the order system e.g. System asset register and public cases of breaches at peers e.g. Medium Business impact e.g. A 3-day stop delays about $800,000 in sales e.g. Sales team's daily order records e.g. Medium (verify the estimate with finance) Level of prepared... e.g. 4 of 5 critical systems restored in a recovery test e.g. Recovery test records (figures in ⑥) e.g. High Effect of investment e.g. The authentication upgrade approved last quarter is complete e.g. Admin console totals for authentication (figures in ⑥) e.g. High Say it in days of downtime, money, and the effect on customers Move technical names and details to an appendix e.g. Not "3 weaknesses" but "1 unfixed weakness in the order system" Present the same metrics in the same order every quarter Add one line on the change from last quarter and why e.g. Systems restored in the recovery test went from 2 of 5 to 4 of 5. The last one is next quarter Write the decision request at the start of the deck Set out the options, the recommended one, the cost, and the remaining risk e.g. Start with "Please approve a review of the insurance coverage limit" Last quarter This quarter Meaning for the b... Multi-factor auth... e.g. 72% of all employees e.g. 91% (100% of administrators) e.g. Fewer ways in for account takeover. SMS codes are weaker than authenticator apps or passkeys, so keep migrating Critical patches ... e.g. 21 days from release to patch e.g. 9 days e.g. Weaknesses stay open less than half as long Recovery test res... e.g. 2 of 5 critical systems restored e.g. 4 of 5 e.g. More coverage against a long outage Detection to cont... e.g. 6 hours on average e.g. 2 hours on average e.g. Better odds of stopping an attack before it spreads Third-party checks e.g. 40% of key vendors e.g. 75% e.g. Better prepared for harm that reaches us through a partner Expected loss fro... e.g. About $800,000 for a 3-day stop e.g. About $800,000 (unchanged) e.g. Sales delayed if the order system is down 3 days. At 1 day the loss would be about $270,000 (estimate with finance) What happens: e.g. You report "120,000 emails blocked" and it is read as more is safer. A rise or a fall tells nobody anything How to check: e.g. For each number in the deck, see if you can say in a few words whether a rise is good or bad How to prevent it: e.g. Move counts to the appendix and keep the rates, days, and amounts from ⑥ in the body What happens: e.g. Acronyms pile up and the deck asks for approval with no questions asked How to check: e.g. Ask someone outside technology to read the draft and mark the words they do not understand How to prevent it: e.g. Replace terms with their effect on the business and explain the ones you keep in the appendix What happens: e.g. You say "this investment means no more incidents" and lose trust when one happens How to check: e.g. Search the deck for "complete," "zero," and "always prevents" How to prevent it: e.g. Write the risk that remains after the measure and a rough recovery time if it happens 3/4 Narrow the decision → 4/4 4/4 Run it every quarter ⑩ Four Ways to Re... AcceptKeep it When impact is small or a fix costs more than it saves, record the risk and accept it e.g. Accept a short outage of the staff bulletin board. Review next quarter ReduceLower it Invest in measures that lower likelihood or impact e.g. Move administrator accounts to phishing-resistant sign-in such as passkeys (about $20,000) TransferShift it Shift part of a loss through insurance or contracts. Accountability does not transfer e.g. Review the cyber insurance coverage limit (check current terms with the insurer) AvoidStay clear Stop or change the activity that creates the risk e.g. Shut down an unused internet-facing server Vertical axis: Bu... Consider transfer or reduction and review once a year. e.g. A long outage at a main site, covered by insurance and a backup site Top priority for reduction or avoidance, and raise it for a board decision. e.g. Ransomware stops the order system Accept and record it, and review next quarter. e.g. A short outage of the staff bulletin board Reduce it within the department budget and report only the trend. e.g. Suspicious sign-in attempts on employee accounts What you need decidede.g. Whether to approve an investment (about $170,000) that cuts recovery of the order system from 3 days to 1 Options and the recommended onee.g. Reduce (recommended), transfer (raise insurance coverage), accept (leave as is). Also write the expected loss that remains if accepted Trap: reporting without asking for a decisionWhat happens: e.g. It ends with "noted," and no budget or owner is setHow to check: e.g. Does the first page of the deck have "what we need decided"?How to prevent it: e.g. Add the deadline for deciding and the r… What was decided Owner Due date Figure to show in... Decision 1 e.g. Approve the investment to cut recovery to 1 day e.g. Head of IT e.g. End of next quarter e.g. Time to restore in a recovery test Decision 2 e.g. Review the insurance coverage limit e.g. Head of Administration e.g. Within 2 months e.g. Coverage scope and the deductible that remains Decision 3 e.g. Shut down unused internet-facing servers e.g. IT section manager e.g. Within 1 month e.g. Servers shut down and servers remaining Carried over e.g. How to check third parties e.g. Procurement e.g. Re-propose at the next report e.g. Share of vendors whose checks are done GatherWeek 1 of the quarter's last monthe.g. Collect the six metrics in ⑥ from the register, admin consoles, and recovery test records DraftWeek 2e.g. Condense it to one page in the format of ⑮ and update the answers to the four questions in ② Pre-briefWeek 3e.g. Show it to the sponsoring executive and the finance lead in 15 minutes and fix how the decision request is worded Report and recordDay of the board meetinge.g. Write the decisions in ⑬ and check the minutes record them Top: conclusion and decision request (condense ⑫ to one or two sentences)e.g. The biggest risk is an order system outage. We ask you to approve an investment that cuts recovery to 1 day Middle: metric changes and meaning (pick up to three from ⑥)e.g. Multi-factor authentication rose from 72% to 91% and recovery tests from 2 to 4 of 5. We are better prepared for takeover and long outages Bottom: remaining risks and next stepse.g. Vendor checks are at 75%. We will check the rest next quarter and report → 2/4 Surface metrics a... ↙ 3/4 Narrow the decision → 4/4 Run it every quarter
100%

Drag to move, scroll to zoom