The Cyber Crime Lab Podcast

There are pockets of genuine operational value - the clean point of return concept, the throttled 400GB download as a pressure tactic, and the risk of getting hit twice during partial remediation - but the episode is heavily padded with obvious advice (patch systems, use MFA, watch phishing) and conversational throat-clearing that dilutes the signal sharply.

“I've seen customers being hit by ransomware twice, actually not at least once in I think two months difference. So while they had not correctly remediated the previous incident, then they got hit by the second group”

“the actual download of the 400 gigs would have taken about 30 days...to put the pressure on you is my take on this”

The name-and-shame misattribution story and the throttled download observation are mildly novel, but the episode closes with the most recycled possible cybersecurity advice (patch, MFA, watch out for phishing), and most frameworks presented are standard IR 101 with no contrarian or first-principles thinking.

“things can be prevented for a large part, obviously, if you have your latest security patches, your latest updates installed”

“using multi factor authentication on all accounts. It basically provides you at least with a second layer of security”

Koen Backers is a genuine practitioner - managing principal IR consultant at SecureWorks with 20+ years in the field - who has clearly done the work at scale; however, he is not a senior executive or widely recognised authority, and the podcast is transparently a marketing vehicle for the host's insurance firm, which limits depth.

“I've been in the CyberSecurity space since 2003, mainly operating in what I call the ecosystem of security, operations center, instant response, and threat intelligence”

“SecureWorks is operating as a business, but we're also humans behind those hotline numbers”

A handful of concrete details appear - 400GB dataset, 30-day throttled download, 15 - 20K Instagram followers, 2 - 3 week typical engagement length, the Uber MFA fatigue incident - but most case details are anonymised, dollar figures are entirely absent, and the bulk of claims remain illustrative rather than evidenced.

“they were claiming to have 400 gigabytes of one of our customers ready for download on that site”

“the actual download of the 400 gigs would have taken about 30 days”

The host occasionally lands useful follow-ups on logistics (spare laptops, remote workforce, timeline expectations) and pushes on the semi-compromised state risk, but there is significant filler, no genuine challenge to any of the guest's claims, and several tangents that go nowhere productive.

“I have a friend and he's always joking. He's like, I can only deal with one problem at a time”

“pays to know the right people”