Explain the chosen objective
Recovery moves modeled P95 from $3,512,449 to $1,908,058. Access has lower modeled mean loss, so a board choosing average annual loss instead would select a different option.
Free board resource
Copy a decision brief for exposure, a funding request, alternatives, and the approval the board needs to make. Keep the decision summary in front and the evidence behind it. No signup is required.
CYBERSECURITY BOARD REPORT — DECISION BRIEF Company / business service: [name and scope] Meeting date / evidence cut-off: [dates] Prepared by / evidence reviewer: [names and roles] 1. DECISION REQUIRED Approve / defer / request validation: [specific action] Amount, currency, cost horizon and budget cap: [values] Budget approver / decision deadline: [name and date] 2. EXPOSURE AND BUSINESS CONTEXT Loss scenario and affected service: [description] Baseline annual gross loss: [mean and selected percentile, or unknown] Sources, model version and assumptions: [links and dates] Insurance treatment and exclusions: [state explicitly] 3. ALTERNATIVES Option | first-year cost | modeled mean | modeled P95 | evidence gaps [baseline] | [cost] | [value] | [value] | [gaps] [proposed] | [cost] | [value] | [value] | [gaps] [alternative / held option] | [cost or unknown] | [values or not modeled] | [gaps] 4. RECOMMENDATION AND WHAT COULD CHANGE IT Chosen objective and why this option fits: [reason] Required work and implementation dependencies: [items] Sensitivity / missing evidence that could reverse the choice: [items] 5. APPROVAL AND FOLLOW-THROUGH Decision / conditions / approver / date: [record] Execution owner and due date: [name and date] Verification evidence and next review: [test, owner and date] Observed control change: [evidence or not yet verified] Modeled financial change: [recomputed estimate or not yet modeled]
Annotated fictional example
Fictional Example Manufacturing Co. asks for $90,000 within a $100,000 first-year cap: $15,000 for a sponsor-required tabletop and $75,000 for recovery capability. The objective is the lowest modeled P95 annual gross loss among the priced, affordable options.
Scroll sideways for all columns.
| Option | First-year spend | Modeled mean annual loss | Modeled P95 annual loss |
|---|---|---|---|
| No optional action (mandatory tabletop only) | $15,000 | $791,066 | $3,512,449 |
| Mandatory tabletop + access hardening | $70,000 | $402,566 | $2,092,283 |
| Mandatory tabletop + recovery capability · Proposed for P95 | $90,000 | $513,439 | $1,908,058 |
| Mandatory tabletop + both optional actions · Over budget | $145,000 | $257,921 | $1,285,222 |
Fictional assumptions, modeled outcomes. Annual gross loss before insurance. P95 is the annual loss threshold exceeded in about 5% of simulated years; it is not expected loss or a worst-case ceiling. The required $15,000 tabletop receives no modeled loss-reduction credit. Figures are rounded from the reproducible sample.
Recovery moves modeled P95 from $3,512,449 to $1,908,058. Access has lower modeled mean loss, so a board choosing average annual loss instead would select a different option.
If recovery only lowers mean per-event severity to $800,000 rather than $650,000, its modeled P95 becomes $2,348,379. Access then has the lower P95. Require evidence for the recovery assumption before treating the recommendation as robust.
Segmentation remains held because cost and tested effectiveness are missing. It is not a zero-cost option, a failed control verdict, or proof that the priced plan covers every risk.
Name the company’s approver, execution owner, due date, and verification test. A modeled reduction is not booked savings. Report actual spend, observed control evidence, and refreshed model outputs as separate facts.
This example uses a 50,000-trial synthetic model. It is not a customer result, earnings adjustment, valuation opinion, or guarantee. The methodology and input checklist explain the numbers.
Actual product interface

See the workflow
A free 30-minute platform demo uses illustrative data. Adil reviews requests personally and replies within two business days. Agree company scope, users, evidence handling, supported workflows, onboarding, and terms before evaluation access.