Watch the full episode · Recorded live October 8, 2026
Your risk register lists the problems. A budget request needs a business case. Most security teams bring the first to a conversation that calls for the second, and leave with nothing.
Kayne McGladrey, a former CISO and the author of Cyber Risk is a Myth, argues that treating cyber risk as its own category is part of why it stays unfunded. In this episode of GRC Radio he and Compyl’s Sid Roper get into business impact analysis, putting a defensible number on a vulnerability, and the objections finance raises before you reach the second slide, with Dan Tangney hosting.
Kayne McGladreyCybersecurity Risk AdvisorAUTHOR, CYBER RISK IS A MYTHFormer CISO who spent years as a virtual CISO for SMB and mid-market firms, in the board meetings where security gets filed under cost. CISSP and Senior IEEE Member.
Sid RoperVP of Customer SolutionsCOMPYL24 years in cybersecurity and GRC as a practitioner, a customer and a vendor. Replacing manual chaos with automated trust.Hosted by Daniel Tangney, Compyl
What the conversation covers
- ✓Why a risk register is a list of problems, and a budget request is a business case.
- ✓Business impact analysis: finding what actually generates revenue, and the undocumented dependencies underneath it.
- ✓Putting a defensible number on a vulnerability without inventing false precision.
- ✓The objections finance always raises, and what answers them.
- ✓Metrics an executive will act on, versus the ones filed under someone else’s problem.
- ✓What deferred governance actually costs, where the regulatory fine is the smallest line item.
Kayne has released 43 templates and 24 exercises from the book for free at kaynemcgladrey.com/myth.
If you’ve presented a risk and been told to come back next quarter, this episode is for you.
