Your Cybersecurity Budget Is a Horse’s Behind
summary
Argues that cybersecurity budgets copy last year’s numbers instead of optimizing value, and demonstrates math-based alternatives using Monte Carlo, graph-flow and machine learning to compute probabilities and ROI. Shows a modeled 45% password‑reuse exploit probability where org value is $100M, and claims org‑wide multifactor authentication costs $2M to prevent $45M loss. Cites the 37% Gordon‑Loeb ceiling as a sanity check, describes prioritizing choke‑point controls and a board app that ties budget cuts to increased exposure.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:51Why CISOs think like losers and cost centers
- 5:26The history of budgets designed around a horse’s behind
- 13:57How cybersecurity budgets are stuck in the past
- 16:31The flawed sanity check of IT security budgets
- 19:19Why cybersecurity lacks business process re-engineering
- 23:06CISOs get budgets they deserve
- 25:16Risk management basics
- 29:11Optimizing risk with ROI
- 32:35Prioritizing countermeasures
- 36:57Quantifying cyber risk with AI
- 41:14Business case for investments
- 43:23Presenting budgets to the board
- 45:31Improving cybersecurity budgeting
related talks
30mCybersecurity Silver Linings
48mSecuring Buy-In for Security Budgets
15mFrom Risk to Return: Measuring Cybersecurity ROI with Data Analytics
31mPerspective and Opportunity Costs of Cyber Attacks
22mCybersecurity: The Challenge of Our Decade
40mGetting Cybersecurity Funding from Your CEO: the 5 Critical Steps
52mA Proven Methodology to Secure the Budget You Need
01h 09mKeynote: What Do We Owe One Another In Cybersecurity?