Skip to content
Brendan Fitzpatrick · CISSP, CRISC

Cyber risk, in numbers that survive the meeting room.

I spent years putting probabilistic numbers on cyber risk and assessing the systems those numbers describe. Then I helped build the product that lets other practitioners do it without me in the room — with more help from machines than I would put in a board deck. One person, no hand-offs, no account manager — this site, at least. Twenty-seven years in security and technology, most of the last eleven quantifying cyber risk and assessing the systems behind it across insurance, legal and regulated environments — now productised: I do product management for the quantification capability at Axio and head the modelling team behind it.

sorklin — zsh — 96×24
sorklin --what-do-you-actually-do
cyber-risk-quant .... loading scenario engine .... OK
exposure @ 1-in-20 .... $4.1M ← the number, not a color
cyber-security ...... csf2 · c2m2 · cis-18 · iso-27k ..... OK
ai-projects ......... ledger · rthunder · chat ... SHIPPING
sorklin --capacity
1 proprietor · 0 middlemen · 100% of the blame is mine
and that, somehow, is the selling point

Three practices, one human

They overlap more than a job description admits.

Assessment tells you what's exposed. Quantification tells you what that's worth. The engineering makes both of them less manual every quarter. Doing all three from the same desk means the tooling fits the work instead of the other way round.

01 / Quantify

Cyber Risk Quantification

Convert “we're nervous about ransomware” into “expect $X this year, here's the exceedance curve, and here are the three controls that move it most.” Scenario models, calibrated ranges, Monte Carlo, an answer your CFO can defend.

Done in Axio360. Allergic to 5×5 matrices; the allergy is documented.

Go to Risk Quant →
02 / Assess & harden

Cyber Security

Assessments, gap analysis and roadmaps that survive contact with reality — aligned to the frameworks you actually have to answer to, written for the people who have to implement them, not for the person who signs the report.

Speaks NIST CSF 2.0 · C2M2 · CIS 18 · ISO/IEC 27001 fluently.

Go to Security →
03 / Build

AI Development

Agents, retrieval, evals and the unglamorous plumbing that decides whether a demo survives Monday. Self-hosted first: if a capability can be switched off by someone else's pricing page, it isn't a capability.

Runs on my own hardware. The projects menu is the receipts.

Go to Projects →
3
Disciplines
1
Proprietor
0
Middlemen
100%
Built by hand*Built by hand
or AI. I can’t remember which.

Yes, “0 middlemen” is the pitch. It's also the risk. Both are on the invoice.

How the number gets built

Five steps, no color picker.

Scope the real assets

What actually hurts if it goes sideways, and how much it costs when it does.

Name the scenarios

“Ransomware of the backup appliance”, not “advanced persistent threat”.

Calibrate the ranges

min / expected / max from the people who know the system — plus the sceptic in the room.

Simulate

Tens of thousands of trials. A distribution, not a single optimistic cell.

Deliver the number

Annualised loss, exceedance curve, and the three things worth funding first.

[!]
No heat maps were harmed during this engagement. There were, in fact, no heat maps at all.

Elsewhere

The risk you can't put a number on is usually the one worth quantifying. Start with the exposure you find hardest to estimate.

The day job is at Axio, where I own the quantification product. This domain is the rest of it: the method, the opinions, and the things I build outside working hours.