The PrOTect OT Cybersecurity Podcast

There are a handful of usable operational observations - using Windows Firewall as a compensating control to reduce patch pressure, the 2017 NSA exploit release as a ransomware inflection point, and bringing IT teams in as vendor-accountability advisors rather than territory owners - but the episode is padded with lengthy career origin stories, repeated teamwork platitudes, and mutual affirmation that dilutes the useful content-per-minute ratio significantly.

“if you put Windows firewall on those engineering workstations, whatever you want, and you block these certain ports from the machines that don't need to talk to them...I won't bug you about patches again because me as a threat actor, if I can't hit a port, I can't take advantage of a port”

“the biggest fear is this decision by the SEC to hold CISOs accountable for breaches”

The IT/OT convergence and 'we're all on the same team' framing is extremely well-worn territory; the episode rarely escapes it. The observation that threat actors have shifted from parasitic long-term data siphoning to short-term ransomware destruction, and the 2017 NSA exploit release as the inflection point, shows some genuine pattern recognition, but most of the episode recycles standard industry talking points.

“2017 to me is, is when the game changed as far as how no matter what environment you're on, if you got Windows on it, then the threat actors, this is what they're going to go after”

“the threat actors now eventually they want to be, they want to be known so they can get the ransom”

Todd Beebe is a genuine 30-year practitioner with hands-on pen testing history at Ernst & Young, cross-industry CISO experience in oil and gas, finance, and chemical, and real OT exposure - not a career thought leader. His credibility is docked slightly because his current employer is deliberately withheld and he acknowledges limited time as an OT-side employee, keeping him more IT-adjacent than a deep OT operator.

“got a job with Ernst and Young. They brought me down to Houston where I now live for a role to build their attack and pin UM program. And from there did two startups”

“been in oil and gas, I've been in finance, I've been in chemical”

The episode has scattered historical specifics - MS08-067, the 2017 NSA exploit releases, Banyan Vines, Novell, Code Red/Nimda - and the host's concrete example of 42 power plants supported by a team of six is the strongest grounding moment, but there are virtually no current named companies, breach case studies, dollar figures for ROI, or measurable security outcomes to anchor the operational claims.

“42 something power plants that I was responsible for and my team of six had to support all of those”

“Ms. 08067. That was the only one I remember because as a pen tester that was the bread and butter”

The host functions more as a co-narrator than an interviewer, frequently redirecting to his own lengthy anecdotes and consistently agreeing with the guest rather than probing or challenging; there is no productive pushback, no attempts to stress-test claims, and the only substantive question toward the end ('what's coming over the horizon') is a podcast cliché that the guest himself admits he wasn't ready for.

“I spent you know, five years as a senior manager there at ey and, and same thing like I never saw myself as an, as a consultant or an advisor”

“Yeah, 100%”