Boards across Asia-Pacific now hear about cyber risk every quarter, usually late on the agenda, after the dividend and before lunch. The chief information security officer has a fixed slot and a long deck: a heat map with a few amber cells and perhaps one red, a maturity score nudged upwards against a framework most directors could not name, and a page of acronyms defined in a footnote.
The questions that follow tend to be about the red cell. Why is it red? When will it be amber? Rarely does anyone ask what the board would do if it stayed red, or whether anything planned for the year ought to wait until it changed colour. The briefing is accurate and carefully prepared, and directors leave better informed. It is much harder to say what any of them is now better able to decide.
That is the gap. Most of what boards hear about cyber risk is built to inform them. Very little of it is built to equip them.
Instruments built for someone else
The tools in a typical board pack were designed for the people who run security. A heat map shows where the risk register is most worried. A maturity score tracks a programme’s progress against a framework. Counts of blocked attacks and patching percentages show whether the operational machinery is turning. All of these answer a management question: are we getting better? None of them answers the question that belongs to the board, which is what it is prepared to do, and when.
The distinction matters because regulators have already settled whose question it is. In Australia, APRA’s prudential standard CPS 234, in force since July 2019, makes the board of a regulated entity ultimately responsible for its information security. In Singapore, the Monetary Authority of Singapore’s Technology Risk Management Guidelines, revised in 2021, expect the board and senior management to oversee technology risk. Responsibility has moved up the building. The briefings, for the most part, have stayed where they were.
A heat map tells a board how the security team is doing. It does not tell the board what the board is prepared to do. A director who must decide whether to delay a launch, take a payments system offline or accept that a critical supplier cannot be audited needs something different: a shared sense, agreed in calm conditions, of where the lines are.
A heat map tells a board how the security team is doing. It does not tell the board what the board is prepared to do.
The CIO Table
Three questions
There is a simpler test of whether a board is ready. Each director should be able to answer three questions without opening the pack.
The first is what would make us stop or delay something. A product launch, a systems migration, the completion of an acquisition. If directors cannot describe that condition in advance, they will invent it under pressure, usually with the project’s executive sponsor in the room and the press release already drafted.
The second is how long it would take to restore our most critical service, and who decides during that time. The useful figure here is the honest one, which is rarely the recovery time objective printed on a slide. The useful name is that of the person who can take a system offline, speak to the regulator or authorise emergency spending at three o’clock on a Sunday morning. Too often, the honest answer to the second half is a committee.
The third is which risks we have knowingly accepted, and who signed. Every organisation runs with some unsupported software, some suppliers it cannot inspect and some systems that cannot be patched without stopping the business. That is normal. What matters is whether each was a decision, taken by someone with the authority to take it, or a drift that nobody chose.
The second question is the easiest to test in advance. Take a rehearsal scenario to the point where someone must decide whether to shut down the customer portal. If the chair looks to the chief executive, the chief executive looks to the chief information officer, and the authority turns out to rest with an operational risk committee that meets monthly, the board has learned something about itself that no heat map would have shown. Better to learn that on a quiet weekday than on the night it matters.
A page, a rehearsal and a direct line
None of this requires a new committee. It requires a few changes to what boards ask for and how they spend the time they already have.
Start with a one-page decision log: every risk the board has accepted, the date it did so, the condition that would make it look again, and the name of the person who signed. It should come before the heat map in the pack, and a director should be able to read it in five minutes. If the page is empty, that is itself a finding. It means the organisation has been accepting risks without telling the board.
Next, run tabletop exercises in which directors play themselves. Many boards watch management rehearse an incident and come away reassured. It is more useful, and much less comfortable, for the chair to sit in the chair, with the real phone list, and be asked forty minutes in whether to pay, disclose or switch off.
Third, hear from the chief information security officer directly from time to time, without the briefing passing through two layers of management on the way up. This is no comment on the reporting line. Material edited for a board tends to be edited towards reassurance, and directors should know what the unedited version sounds like.
Finally, change what director education is for. Most of it teaches vocabulary: what ransomware is, what lateral movement means, how a phishing campaign works. Directors do not need fluency. They need to understand the handful of decisions they may face, how long each one takes, what they will know at the moment of deciding, and how little of it will be certain.
The result should be a shorter pack and a longer, less pleasant discussion, with the decision log first and the heat map in an appendix. The test of whether it has worked is simple: when a shareholder or a supervisor asks what the board decided about cyber risk last year, the chair should be able to answer from a single page, with a name against every line.



