Board Cyber Oversight

How a Board Can Test Security Leadership Succession Before a Vacancy

Test CISO succession planning before a vacancy. Check interim authority, evidence access and critical relationships with a practical leadership tabletop.

Business Meeting in Bright Office Space

A named deputy is not a succession plan if that person cannot authorize an incident decision, reach the insurer or explain an open risk exception. The board needs evidence that security leadership can continue when the usual leader is unavailable.

Test the operating model before a vacancy. Give an interim leader a realistic decision, remove the incumbent from the exercise and watch where authority, knowledge and access break down. This is a continuity test, not a public audition for someone's job.

A useful CISO succession planning board discussion separates emergency coverage from the longer-term hiring decision. The first protects decisions now. The second determines the leadership the business will need next.

Key takeaways

  • Test decisions and relationships, not just the organization chart.

  • Distinguish an interim appointment from authority to accept business risk.

  • Give deputies controlled access to the evidence their role requires.

  • Include critical suppliers, counsel and customer commitments in the handover.

  • Record gaps with owners, interim safeguards and a retest date.

Step 1: Identify the decisions that cannot wait

List the decisions the security leader normally coordinates: escalating an incident, advising on a risky launch, briefing directors, requesting emergency resources and assessing whether a control exception remains acceptable.

For each decision, distinguish the security recommendation from the executive authority to act. A deputy may coordinate response without having authority to accept a material business risk. The plan must identify the actual decision maker and a fallback when that person is unavailable too.

NIST CSF 2.0 calls for cybersecurity roles, responsibilities and authorities to be established, communicated, understood and enforced. A succession exercise tests whether those words describe a working arrangement.

Step 2: Build the minimum handover

Prepare a current record of material risks, exceptions, active incidents, provider dependencies, upcoming commitments and open board decisions. Link to the controlled source rather than copying sensitive evidence into an unrestricted handover folder.

Include relationship coverage. A phone number is not enough if only the incumbent is recognized as an authorized contact by the response provider. Check emergency engagement and approval routes without triggering a real service request.

NIST's workforce guide connects workforce gaps to enterprise risk decisions. A vacancy may call for temporary support, reassigned work or a changed risk response, rather than expecting one person to absorb every responsibility.

Step 3: Run a bounded absence scenario

This fictional tabletop assumes the security leader is unavailable for two weeks during a supplier incident. It is an exercise design, not a claim about any organization.

Decision moment Evidence the interim leader needs Pass condition
Supplier reports a possible data exposure Service scope, data map and escalation contacts The team identifies accountable owners without relying on the incumbent.
Emergency assistance may be needed Engagement terms and spending authority A permitted approver can make the decision through a supported route.
An executive asks whether to continue service Current facts, uncertainty and business options Security advice reaches the business risk owner with a recorded recommendation.
Directors need an update Incident status, decisions and next checkpoint The briefing distinguishes confirmed facts from open questions.

Do not grant broad production access just to make the exercise pass. Test through authorized accounts and controlled evidence. If emergency access is part of the plan, test its approval and logging arrangements safely.

Step 4: Watch the handoffs rather than rescuing them

The incumbent can help design the scenario, but should not quietly supply every answer during it. Observe where the interim leader needs undocumented knowledge, personal relationships or authority nobody has delegated.

Include an unavailable deputy or a conflicting executive instruction as a second scenario when the first test is stable. A plan that depends on one replacement can reproduce the same concentration risk under a different name.

The related discussion of customer-impact recovery testing asks whether service actually works after restoration. Apply the same standard here: the title may be covered while the decisions are still blocked.

Step 5: Close the gaps and retest

Record each failure as a specific operating gap. Assign an owner, an interim safeguard, a due date and evidence that will demonstrate closure. Report unresolved authority or capacity gaps to the executive who can change them.

The board should ask what changed after the test and which decisions remain dependent on one person. It should not need a dossier of private personnel assessments to understand that exposure. Keep talent evaluation separate from the exercise record where appropriate.

Sources

NIST, Cybersecurity Framework 2.0, GV.RR and GV.OV; NIST, Cybersecurity, Enterprise Risk Management, and Workforce Management Quick-Start Guide, March 2026. The tabletop and pass conditions are practical recommendations, not a prescribed NIST test.

Frequently asked questions

Does the board choose the interim CISO?

That depends on the company's governance and appointment arrangements. The board should verify that the responsible people have a workable plan, rather than assuming it owns every appointment decision.

Is a fractional or external leader enough?

It can be part of the response if scope, availability, access and authority are explicit. A contract alone does not establish that the person can make or support the decisions the business needs.

Should the incumbent participate?

Yes in preparation and learning, but not as an invisible rescue path throughout the test. The purpose is to expose dependencies safely, not to blame the incumbent for having specialized knowledge.

What evidence should directors receive?

A concise summary of decisions tested, gaps found, temporary safeguards, accountable owners and retest results. Sensitive operational and personnel details should stay within appropriate access boundaries.

Closing

Ask for one absence tabletop before the next leadership change. The useful result is not a reassuring name on a chart. It is evidence that a qualified person can reach the right decision maker with the facts needed to act.

Next step

Get Board-Ready on AI and Cyber Risk

A 30-minute call. No charge. You'll leave with a clear read on where your oversight stands and what to do about it.

Stop Guessing. Start Scoring
Tyson Martin

Written by Tyson Martin, NACD.DC

Chief Trust, Security & AI Officer. CISO of record at MIO Partners; former CISO & CTO at Lumber Liquidators and Orvis; advisor to 200+ Fortune 500 boards and C-suites at AWS.

See the track record
Keep reading

More on Board Cyber Oversight

All CISO Insights
Board Cyber Oversight

When a Cyber Risk Exception Should Expire

A cyber risk exception without an expiry date is an unrecorded acceptance of risk. Learn when exceptions should expire, renew, or escalate to the board.

Board Cyber Oversight

What Directors Should Ask After a Near Miss

Use cyber near-miss board questions to identify what worked, what allowed the event and which fixes need evidence. No loss does not mean no lesson.