How do we…
How do I brief the executives at the end of discovery?
Add to board memoOpen the memo
The short answer
- Recommendation
- At the end of discovery, brief the executives on what you have checked: the findings in four words, the top risks, the starting position in counts and words, and your asks. Spend most of the time on the asks, written as decisions, and promise no money, date or result before the plan is agreed.
- Reasoning
- Executives act on what you show them, so a statement you have not checked must stay Described only (rule TR-02). The pack says to promise nothing until the plan is agreed, because an early promise rests on what you were told. An ask the executives can decide from alone states the options, a recommendation, the cost and the risk of not deciding. That turns the meeting into decisions.
- Considerations
- In the pack's defaults discovery ends at the close of week 7. Your own standard or the sponsor may change the timing and the slide set.
- A risk acceptance or an exception goes to the approver its band sets. Outside tolerance that is the board, a board risk committee it has delegated to, the management board in a two-tier structure, or executive management where there is no board.
- Something that must stop harm or meet a legal duty goes to its owner and the sponsor at once. Do not hold it for the briefing.
- This briefing does not replace telling the management body what it must approve and oversee. Counsel confirms what liability means.
The decision, step by step
Select any step for the reasoning behind it and where the pack covers it.
- Start
- Step
- Decision
- Outcome
Keyboard: Tab to a step, arrow keys move along the flow, Enter pins its explanation, + and − zoom, 0 fits the diagram, Esc closes. The text version below has the same content.
Where a step quotes a number, it is the default in the CISO Times pack. Your own standard may set a different one.
Read as text
The same flow written out: each step, its reasoning and where the pack covers it. 21 steps.
Start
Discovery is ending and the executives expect a briefing
The pack's first executive briefing comes at the end of discovery, which in its defaults is the close of week 7. It reports what you found. It is neither an audit nor yet a plan. It has four parts: the findings in four words, the top risks, the starting position and the asks.
In the pack
- P27-A02 First 90 Days Security Leader Checklist90 Days (rule TR-13)
- P27-A09 First Executive Briefing Deck for a New Security Leader
Decision
Must something reach the executives before discovery ends?
The pack says to change nothing until discovery ends, except to stop harm, to act on a legal duty or to take a no-regret action. Judgement: only those cases justify telling the executives early. If you cannot tell whether a finding is that serious, answer yes and tell the sponsor.
- Yes, or not known: Tell the sponsor now, act only to stop harm, then brief as planned
- No: Close discovery and count the findings in the four words
In the pack
- P27-A02 First 90 Days Security Leader ChecklistRequirements (rule TR-01)
Outcome
Tell the sponsor now, act only to stop harm, then brief as planned
Take the finding to its owner and to the executive sponsor at once, and do only the action that stops the harm or meets the duty. The discovery workbook says a contradiction that is a live risk goes to its owner now. Make no wider change and no promise. The full briefing still follows at the end of discovery, with everything else you have found.
In the pack
- P27-A02 First 90 Days Security Leader ChecklistNot Early (rule NE-3)
- P27-A02 First 90 Days Security Leader ChecklistRequirements (rule TR-01)
- P27-A03 Inherited Security Programme Discovery WorkbookInstructions
Step
Close discovery and count the findings in the four words
Count items as Evidenced, Described only, Not found or Contradicted, and list every contradiction. Show counts such as 14 of 20 looked at, never a score. An item you have not yet looked at stays as not yet looked at. Do not guess a finding to fill the table.
In the pack
- P27-A03 Inherited Security Programme Discovery WorkbookSummary
- P27-A02 First 90 Days Security Leader Checklist90 Days (rule WK-31)
Decision
Does every finding state what you saw: a record, test or system view?
A statement alone is Described only, however senior the person who made it. Executives will act on what you show them, so separate what you were told from what you saw before you present. If a finding rests on a document you have not checked, or you are unsure, answer no.
- Yes: Has each owner heard their Contradicted and Not found items first?
- No, or not known: Get the proof, or present the item as Described only
In the pack
- P27-A02 First 90 Days Security Leader ChecklistRequirements (rule TR-02)
- P27-A02 First 90 Days Security Leader ChecklistNot Early (rule NE-9)
Step
Get the proof, or present the item as Described only
Go back for the record, the test or the system view. If you cannot get it before the briefing, present the item as Described only and say what proof would settle it. A shorter list that holds up serves you better than a long one that does not.
In the pack
- P27-A03 Inherited Security Programme Discovery WorkbookSummary
- P27-A02 First 90 Days Security Leader ChecklistNot Early (rule NE-9)
Decision
Has each owner heard their Contradicted and Not found items first?
Judgement: tell the owner of a Contradicted or Not found item what you found before it goes into a briefing, so that nobody learns of it in the meeting. The pack asks for this only where the contradiction is a live risk, which goes to its owner now. If you have not spoken to the owner, or you are unsure, answer no.
- Yes: Pull together the risks, past-review items, open duties and baseline
- No, or not known: Tell those owners now, and change a finding only on new evidence
In the pack
- P27-A03 Inherited Security Programme Discovery WorkbookInstructions
Step
Tell those owners now, and change a finding only on new evidence
A short private conversation or note is enough. Record what you find, not who is to blame. Judgement: if the owner shows you a record, update the finding. If they only disagree, keep the finding and say on the slide that the owner disputes it.
In the pack
- P27-A02 First 90 Days Security Leader ChecklistNot Early (rule NE-7)
- P27-A03 Inherited Security Programme Discovery WorkbookInstructions
Step
Pull together the risks, past-review items, open duties and baseline
Take the few risks the findings support from the risk register, each with its owner and band. Add how many inherited exceptions and risk acceptances are past review, the open incidents and promises with dates, and the baseline in counts and levels in words, with each unknown and its reason. Never total the baseline.
In the pack
- P27-A10 Security Posture Baseline ScorecardRules and Words (rule BL-01)
- P27-A10 Security Posture Baseline ScorecardBaseline Summary
- P05-A02 Risk Assessment Methodology & Scoring ModelWriting a risk
- P27-A09 First Executive Briefing Deck for a New Security Leader
Step
Write each ask as a decision with options, a recommendation and cost
Each ask states the decision, why now, at least two options, your recommendation, the cost and the risk of not deciding. The pack's usual asks cover the decision-rights arrangement and sponsor, the few priorities, owners for acceptances past review, the reporting rhythm, who briefs the management body, and a date for the budget conversation.
In the pack
- P03-A02 Board Reporting Narrative ModelWriting an ask as a decision (rule BR-06)
- P27-A09 First Executive Briefing Deck for a New Security Leader
Decision
Does an ask need money, a date or a result you cannot yet keep?
The pack says to promise nothing until the plan is agreed, and its briefing asks for no money. It asks the executives to set a date for the budget conversation instead. If you are unsure whether you can keep a commitment, answer yes.
- Yes, or not known: Turn it into a decision on priorities or a date for the budget talk
- No: Does an ask accept a risk or renew an exception?
In the pack
- P27-A02 First 90 Days Security Leader ChecklistNot Early (rule NE-3)
- P27-A09 First Executive Briefing Deck for a New Security Leader
Step
Turn it into a decision on priorities or a date for the budget talk
Replace the commitment with a decision the executives can take now: agree the priorities, agree what the programme will stop or leave for now, or agree a date for the budget conversation. State the cost of the ask as none where it is none, and show the risk of waiting. The plan and any outside promise follow once the plan is agreed.
In the pack
- P27-A02 First 90 Days Security Leader ChecklistNot Early (rule NE-3)
- P27-A07 100-Day Security PlanSummary
- P27-A09 First Executive Briefing Deck for a New Security Leader
Decision
Does an ask accept a risk or renew an exception?
Such a decision goes to the approver the band sets, and nobody approves what they own or requested. An exception goes to the approver for its band. A risk acceptance goes to the approver for the band of the residual risk, and outside tolerance only the board or its equivalent decides. If you cannot tell the band, answer yes.
- Yes, or not known: Address each such ask to its approver and name the role on the slide
- No: Fit the deck to the audience and plan the time around the asks
In the pack
- P27-A06 Transition Decision Rights MatrixDecision Rights (rules DE-02, DE-03)
- P02-A02 Security Exception & Waiver StandardApproval authority and maximum duration (rule EX-05)
- P05-A02 Risk Assessment Methodology & Scoring ModelWhat the band decides (rule RM-08)
Step
Address each such ask to its approver and name the role on the slide
Approvers depend on how the organisation is governed: the board or a board risk committee it has delegated to, the management board in a two-tier structure, or executive management where there is no board. The decision-rights matrix asks the executive sponsor to take such a decision on to its approver. You do not approve what you own. The pack's default is that you accept no new risk in the first 30 days.
In the pack
- P27-A06 Transition Decision Rights MatrixDecision Rights
- P27-A06 Transition Decision Rights MatrixInstructions
Step
Fit the deck to the audience and plan the time around the asks
The deck suggests a slot split that keeps one third of the time for the decisions. In a small organisation, present to the owners or the management team and keep only the deck's minimum slides, cutting the rest to a line each. Settle each cost with finance and each legal point with counsel before the meeting, as BR-06 asks for who has agreed.
In the pack
- P27-A09 First Executive Briefing Deck for a New Security Leader
- P03-A02 Board Reporting Narrative ModelWriting an ask as a decision (rule BR-06)
Step
Agree with the sponsor who tells the management body, and when
This briefing does not replace telling the management body. The pack's default is that, within 60 days of the start, the sponsor tells it what NIS2 Article 20 asks of it: to approve the measures, oversee their implementation and follow training, and that it can be held liable. Counsel confirms what liability means.
In the pack
- P27-A02 First 90 Days Security Leader ChecklistRequirements (rule TR-11)
- P27-A02 First 90 Days Security Leader ChecklistNot Early (rule NP-10)
Step
Hold the briefing and write down each answer as it is given
Present the findings briefly and spend most of the time on the asks. Record each ask with the answer, the owner and the date. If an executive makes a new request, note it as Noted, not committed, until you have checked that you can keep it.
In the pack
- P27-A09 First Executive Briefing Deck for a New Security Leader
- P27-A04 Stakeholder Interview Guide & RecordThe record format
Decision
What did the executives decide on each ask?
Take each ask separately. Agreed as put, agreed with changes, deferred and declined each leave a different task. A deferral is itself a decision, so record until when and what stays true in the meantime.
- Agreed as put: Record the answers, then draft the plan from them
- Agreed with changes, or deferred: Bring it back with the changes or a date, and keep the risk visible
- Declined: Record the refusal and take the risk to its approver
In the pack
- P03-A02 Board Reporting Narrative ModelThe reporting rules (rule BR-06)
Outcome
Record the answers, then draft the plan from them
Keep the decisions and who gave them. Draft the hundred-day plan from the findings and the agreed priorities, tracing every item to a finding, an interview record or a handover gap. Tell the groups you interviewed what you heard, and promise nothing new.
In the pack
- P27-A07 100-Day Security PlanSummary (rule PL-01)
- P27-A02 First 90 Days Security Leader Checklist90 Days (rule WK-32)
Outcome
Bring it back with the changes or a date, and keep the risk visible
Judgement: where the executives agreed with changes, return the amended ask at the next meeting. Where they deferred, record the date and the risk that stays in place until then. A deferral then shows as a choice rather than a quiet default.
In the pack
- P03-A02 Board Reporting Narrative ModelThe reporting rules (rule BR-06)
Outcome
Record the refusal and take the risk to its approver
Write down what was declined, by whom and what stays true. A risk that stays outside tolerance goes to the approver the band sets, the board or its equivalent where the rules say so. Do not work around the refusal, and do not accept a risk you own.
In the pack
- P27-A06 Transition Decision Rights MatrixDecision Rights (rule DE-03)
- P05-A02 Risk Assessment Methodology & Scoring ModelWhat the band decides (rule RM-08)
Practical checklist
- Close discovery and count the findings as Evidenced, Described only, Not found or Contradicted, listing every contradiction.
- Check each finding states the record, test or system view you saw, or present it as Described only.
- Tell each owner of a Contradicted or Not found item before the meeting, and change a finding only on new evidence.
- Pull together the top risks, the items past review, the open duties and the baseline, with no total.
- Write each ask as a decision with options, a recommendation, the cost, the risk of not deciding and who has agreed it.
- Replace any ask for money or a date with a decision on priorities or a date for the budget conversation.
- Address each risk acceptance or exception ask to the approver its band sets.
- Record each answer with its owner and date, then draft the plan from the agreed priorities.
Evidence to have ready
- The discovery counts in the four words, with what was seen for each Evidenced finding.
- The briefing deck, with each ask in its decision form.
- Each ask with the answer given, who gave it and the date, including deferrals and refusals.
- For each risk acceptance or exception, the approver its band sets and their decision.
Assumptions
- You are the new head of security or CISO, and discovery has reached its end, which the pack's defaults place at the close of week 7.
- An executive sponsor exists and has agreed to open the door to the other executives.
- The timings and the minimum slide set are the pack's defaults. Your own standard or the sponsor may change them.
Not covered here
- Telling the management body its duties under NIS2. The sponsor does that, and counsel confirms what liability means.
- How to find the evidence behind each finding. That is “How do I find out what an inherited security programme really does, as opposed to what it claims?”.
- How to build the plan the asks lead to. That is “How do I build a hundred-day plan that mixes quick wins with the decisions that take longer?”.
- Employment or liability advice. Counsel gives it.
Related questions
- How do I find out what an inherited security programme really does, as opposed to what it claims?
- How do I decide who to interview first, and what to ask?
- How do I build a hundred-day plan that mixes quick wins with the decisions that take longer?
- If my predecessor left without a handover, then how do I rebuild what I need?