ReportingREBUILT

“We’re $1.7M over appetite on payments platform risk. Here’s the program that buys it down.”

That’s the sentence every founder and ops lead has wanted to say in the room — and couldn’t, because the night-before pack was a heat map, a dashboard export, or an AI memo that sounds smart and funds nothing. Reporting binds your appetite, live pressure, and plan to one number you can defend under CFO heat.

the vCISO Lite Difference

AI gets you a narrative. Heatmaps give you cyber theater. We enable leaders to confidently prioritize & manage their cyber risk — so you stop funding colors.

vs AI memo

Sounds board-ready. Funds nothing.

A model can summarize last quarter’s tickets. It can’t continuously bind your appetite, rehearsals, owners, and live pressure into a dollar figure you’ll defend when the CFO asks what moved the curve.

Live appetite · rehearsals · dollars you defend
vs heat-map dashboard

Green walls don’t price the miss.

RAG tiles and “all systems nominal” don’t say you’re $1.7M over what the board agreed to accept — or which funded program pulls a 1-in-5 year back to 1-in-10.

Appetite miss priced · program that pulls the curve
vs spreadsheet night-before

Rebuild the story every quarter — or don’t.

Export, paste, hope the numbers still match. Reporting keeps expected loss, pressure since the last meeting, and the plan on the same spine — so the pack is drafted from the system, not from memory.

Expected loss · pressure · plan on one spine
01 · Risk Portfolio

Know how your risks impact your business objectives — in dollars.

Expected annual loss on the loss curve, next to appetite and materiality. One sentence the room can hold: which risk is over, by how much, and what needs a decision. Not a heat map. Not a spreadsheet export the night before.

Understand which risks exceed your tolerance — before someone asks in the room and you stall for “I’ll get back to you.”A short Needs attention list that points to the decision (Plan, Decide, Resilience), not another status page.Today vs plan on the same curve: what a funded program does to a bad year, in the language finance already uses.
Read the changelog →
02 · Early Warning

Risk indicators leadership can read — while you can still act.

Most risk only gets looked at when the board pack is due, so the things that build between meetings show up as surprises: three revenue lines quietly moving onto one sign-in provider, a live attack on tools like yours, a recovery test that ran 37 hours over. Early Warning watches for them as they build. When one crosses a limit you set, you see what it puts at stake in dollars, who owns it, and the next step. Open it to see which business functions it touches, the revenue at risk each day, and the fix that takes it off the list.

Read the changelog →
Only signals that crossed or approached a board-set limit make the cut — so the room sees pressure building, not a wall of green that says everything is fine.Every indicator the board tracks carries dollars at stake, the limit you set, a named owner, and the next step with a date — so “who’s on it?” already has an answer.Improvements show up beside what got worse, with a four-quarter trend and peer median — so the story is progress and pressure, not only bad news.
Portfolio · Early Warning14 indicators

Risk pressure is rising. Three things are already past the limits you set, and one of them is an attack happening now.

Since the last board meeting · Aug 12Snapshot Oct 27
  • A token-theft campaign aimed at code platforms began Oct 21. We're exposed but not breached.
  • September's recovery test measured 61 hours to restore payments, against a 24-hour limit.
  • Containment time improved from 9 to 6 days, and vulnerability fixes on time reached 96%.
At a glance
3past their limit
2getting close
3on track

Showing the 8 indicators the board tracks. 6 more, all fine, are in Analysis. Peer figures are the median for similar-sized software companies.

Click Okta for Analysis (radar + what fixes it), or open the Analysis tab.

03 · Resilience

Know why recovery takes as long as it does — from your own rehearsals.

What would stop the business, and how fast it comes back, scored from tests you already run.

Rank suppliers and systems by revenue at risk per day — and whether a backup is tested.Name single points of failure and the business functions that depend on each.Track rehearsals from plan through fixes until they close.
Read the changelog →
Why payments took 61 hoursFrom the Sep 30 rehearsal

Finding a clean backup took 22 of the 61 hours. The recent backups were encrypted along with everything else.

0h24h48h72h
Decide and mobilize
2h
Contain and isolate
6h
Restore staff sign-in
6h
Find a clean backup
22h
Rebuild the payments database
18h
Reconnect Stripe and test
8h
Reconcile and reopen
5h
Payments back online
61h

37h over the limit

Restore staff sign-in runs alongside the critical path. P-04 (backups attackers can’t reach, $186K) and P-11 (a restore runbook and a second trained admin, $22K) are the two programs that shorten it.

04 · Dependency Map

Keep the map current without owning a spreadsheet.

Every company has a dependency map. It’s a spreadsheet someone built for the last audit, and it went stale the week after. That’s how customer data ended up behind the same Okta sign-in as payments and orders, and nobody noticed.

Here, the map builds itself from what you’ve already told us. You only confirm what changed, and every number downstream moves with it.

Business functions with revenue share and downtime tolerance — from Business context.Systems, suppliers, and people wired from connections you already have.Proposed changes to confirm so the map doesn’t go stale between reviews.
Read the changelog →
What stops if it goes down3 to confirm

Two of your revenue functions sign in through Okta. A third may have joined them. Confirm it below.

Business functions
Payments$1.2M a day · down 4h max
Orders$890K a day · down 8h max
Customer data$340K a day · down 24h max
Operations$300K a day · down 48h max
What they depend on
Okta sign-in2 functions · $2.1M a day · no backup
Payments database1 function · $1.2M a day
AWS us-east-13 functions · partly covered
Stripe1 function · tested fallback
On-call database adminNot on the map yet
3 to confirmProposed from what you’ve already connected
Customer data → Okta sign-inFrom your Okta connection, Sep 18 · adds $340K a day behind Okta
Payments database → one on-call adminFrom your on-call rota · one person, no backup
Operations → AWS us-east-1From your AWS connection · partly covered
05 · Operating Plan

Fund the move that buys the curve down — before anyone votes.

Rank programs by expected loss reduced per dollar, against the budget you actually have. The same dollars Portfolio and Early Warning just named — so the ask is a line in the budget, not a story you invent under heat.

Operating Plan for FY27: a $1.15M security budget against a $1.62M full ask. Residual exposure falls to $7.7M from $9.8M today, $2.1M of risk reduced a year, 4 of 7 programs funded at $2.0 risk reduced per $1. Operational stays $1.7M over appetite; the next $186K (P-04) would buy $1.8M more.Operating Plan for FY27: a $1.15M security budget against a $1.62M full ask. Residual exposure falls to $7.7M from $9.8M today, $2.1M of risk reduced a year, 4 of 7 programs funded at $2.0 risk reduced per $1. Operational stays $1.7M over appetite; the next $186K (P-04) would buy $1.8M more.
Every program names the business goal it protects, like winning EU enterprise deals or keeping the 99.9% uptime promise, and the executive who owns that risk. The CFO and COO are funding their own objectives, not a security wish list.
See each program’s effect on expected loss and a bad year — on the same curve as Portfolio, so the board hears one language.
Set your budget and see exactly which programs make the cut and which don’t, before the meeting, not after.
Read the changelog →
Board · Nov 18 · Item 3Pack v3 · drafted from Portfolio and Plan
Decision needed

Payments stopping for days puts Operations $1.7M over the appetite you set. Nothing funded fixes it.

Expected loss$4.2M → $2.4M
Appetite$2.5M
Risk ownerCFO · D. Whitfield
The board decided · tap the other option to compare
Recorded · what moved
PlanP-04 moves above the funding line. Budget $1.15M → $1.34M; the plan of record updates.
PortfolioPayments expected loss $4.2M → $2.4M, back under the $2.5M appetite.
ResilienceRestore estimate 61h → 39h once delivered.
InvestorsSeries B data room and the Q4 update show the same numbers.
06 · Board

Give the board and your investors the live dollars that move a vote.

Exposure against appetite, pressure since last time, and the program that buys it down — ready when directors and investors need to act. Investor portals carry the raise and every quarter after, without a second set of numbers.

Surface the miss, the pressure, and the funded move in time for a decision — not another status tour.Open investor portals for the raise and every update after — one set of dollars, no parallel process.Record the decision with the dollars that drove it — accept over tolerance or fund a program, and it updates the plan.
Read the changelog →
07 · Briefing Room

Directors learn cyber risk from your numbers — not a generic course.

Short classes built on your expected losses, recovery tests, and plan. Five minutes at a time: watch, listen, or read.

Prep assigned from the next meeting’s agenda so directors show up ready.Twenty-six classes — seven core, nineteen electives — tied to your company’s numbers.Completions land as training evidence, not a forgotten LMS checkbox.
See Briefing Room →
Briefing Room home for the board chair: a 15-minute prep session built from the Nov 18 agenda, the 61-hour recovery test against a 24-hour target, and the board year leading to Nov 18.Briefing Room home for the board chair: a 15-minute prep session built from the Nov 18 agenda, the 61-hour recovery test against a 24-hour target, and the board year leading to Nov 18.

COMMON QUESTIONS

Questions buyers typically ask us

  • How is this different from the risk dashboard in my compliance platform?

    Most compliance platforms roll control health into a score and put a dollar sign on it. Reporting runs FAIR, how often a loss happens times how much it costs, through a Monte Carlo simulation for each risk, and draws the result as a loss curve against the appetite your board set. It tells you which risk is over, by how much, and which program brings it back under.

  • Where do the dollar figures come from?

    From what you’ve already told vCISO Lite: revenue, how long each business function can be down, your insurance, and your recovery tests. How often a loss happens comes from your team’s forecast or, where there isn’t one yet, from how often it happened at firms like yours, cited to the published report and year. Every figure links to its source.

  • Do I need a risk analyst to run it?

    No. If Business context is filled in, Portfolio has your first numbers the same day. You answer questions about the business and decide on proposed risks. The simulation, the curves and the board summary are drafted for you.

  • Who sets the risk appetite?

    vCISO Lite proposes a starting tolerance for each risk category from your business context. It isn’t the board’s appetite until the board adopts it. The board can adopt it as proposed or override it, and the reason is recorded either way.

  • What happens when the board funds a program?

    The plan becomes the plan of record, and every risk that program treats is recalculated. Portfolio, Early Warning, the appetite table and the next meeting pack all read the new numbers.

  • What happens to my existing reports and history?

    Risks, forecasts, plans, rehearsal results and report history carry over as they are. Bookmarks to Executive Dashboard, Risk Analysis, Forecasting and Get Smart open their new home in Reporting.

  • Which plans include what?

    Portfolio, the Operating Plan, Board and the Dependency Map questions come with Business and up. Briefing Room and investor rooms are on Ultra and Enterprise. Early Warning, Resilience and the full Dependency Map are on Enterprise, with a preview on Business and Ultra.

Walk into your next board meeting with the number and the plan.