Risky Business Features

Risky Business Media
  • 5.0 (16)
  • Technology
  • Updated Weekly

Join reformed CTO James Wilson as he dives deep on cybersecurity topics through an enterprise lens. From solo content and interviews with CISOs and researchers to vendor and startup deep dives, James does a bit of everything.

  1. 4d ago

    What I learned from cheating clankers

    In this solo Risky Business Features episode, James Wilson looks at the string of recent AI benchmark cheating escapades and how they’ve reshaped his thinking about LLMs and vulnerability research. He explores the current benchmarks and exactly how agents go about gaming the testing system to achieve their tasks. And why understanding that has changed the way he interacts with his agents. Show notes OpenAI incident account and grading distinction METR and Redwood independent assessment FrontierCode original evaluation methodology BrowseComp aggregation experiments Sonnet 4 point 5 coding scaffold and parallel selection Opus 4 point 6 BrowseComp setup BrowseComp evaluation awareness and contamination investigation Sonnet 5 point 5 effort and review subagents FrontierCode 1 point 1 revision and rubric changes Astra launch comparison and effort conditions Original OSWorld task construction and worked examples Sonnet 4 point 6 system card Original OSWorld benchmark OSWorld 2 environment and evaluation design GPT 5 point 4 comparator table GPT 5 point 5 comparator table BrowseComp construction and grading paper GPT 5 point 6 single model and Ultra configurations METR investigation and artifact evidence Released task definition Released scorer for reference only OpenAI paper sections 3 point 1 to 3 point 3 OpenAI accompanying explanation Sycophancy to Subterfuge paper Training a Misaligned Reward Seeker and evaluation appendix GPT 5 point 2 AIME result

  2. Oct 2

    Bug count sounds impressive... but means little

    In this solo Risky Business Features episode, James Wilson explains why “number of bugs” fixed in any given update is a misleading metric. We’ve seen up to 1,000 individual bug fixes in a single update recently, but that doesn’t give defenders the full picture they need to manage risks. Not all bugs are equally exploitable, so the industry needs to catch up to the bugpocalypse with more transparency. And maybe an entirely different approach to patching. Show notes

  3. Sep 15

    How to launder illicit Bitcoin

    In this podcast episode, investigative journalist Geoff White joins James Wilson to talk about what happens to the money after ransomware gangs get a payday. The payment itself might be in the millions, but it’s difficult for gangs to convert their ill-gotten crypto gains into cash they can actually spend. Geoff explains the role of professional launderers and why cash-rich drug gangs are useful connections for crypto-rich cybercriminals. They also dive into who operates these international laundering networks, other types of crime they enable, and whether this affects the argument of whether victims should be allowed to pay. Show notes

  4. Sep 11

    Hunting software supply chain malware

    In this podcast episode, OpenSourceMalware founder Paul McCarty joins James Wilson to explain how researchers find and analyse malicious packages, GitHub repositories and developer tools. Paul walks James through static analysis, deobfuscation and reconstructing multi-stage kill chains to identify what attackers are trying to steal. They also discuss how LLMs make malware development easier while introducing operational security mistakes. The pair examine DPRK tradecraft, blockchain-based payload delivery and what Paul calls Pollen Rider, which can reinfect developers through their own repositories. Show notes

  5. Sep 3

    Who gets to hack the hackers?

    In this podcast episode, Brad Arkin joins James Wilson to chat about the Trump administration’s call to let private entities conduct cyber operations against criminal groups. Brad’s firsthand experience responding to cyber incidents alongside US law enforcement gives him a unique perspective on how government and private sector relationships work, and how this program could improve the ability of both sides to tackle cybercrime. James and Brad also explore who might participate in these campaigns and whether the government will be able to effectively oversee them. Show notes

  6. Aug 28

    How Brian Krebs doxxed TeamPCP

    In this podcast episode, James Wilson chats with Brian Krebs about the investigation that led him from recycled cybercrime handles and old forum records to the true identity of TeamPCP’s alleged leader in Perth. TeamPCP is the hacker group that has gone berserk in the software supply chain over the last year or so, stealing credentials to compromise developers, their software packages, and their repositories. In this interview Brian talks about his Signal conversations with the group’s ringleader, the strange Cybercats community surrounding TeamPCP, and the passive DNS breakthrough that helped him unmask what he thinks are the ringleader’s true identities. Show notes Two Alleged ‘TeamPCP’ Hackers Arrested in Australia – Krebs on Security

  7. Aug 17

    James Kettle on inventing new attack techniques with LLMs

    In this podcast episode, James Wilson chats with PortSwigger’s Director of Research James Kettle about using an LLM to develop genuinely new attack techniques. Kettle has built what he calls the HTTP Terminator, an autonomous research system that generates and tests tens of thousands of potentially new HTTP desync techniques. The Terminator, which makes use of Kettle’s own research methodology, has already come up with new desync methods that James hadn’t thought of before. Kettle and Wilson discuss how to develop and evaluate machine-generated ideas without drowning in false positives, and why the most powerful part of the process is the discovery cascade, where one unexpected result becomes the seed for another. The upshot is AI can conduct genuinely novel security research, but don’t expect to one-shot your way to an army of robot hackers. Show notes Can AI do novel security research? Meet the HTTP Terminator | PortSwigger Research HTTP/1.1 must die: the desync endgame

  8. Aug 7

    How private LLM inference actually works

    In this podcast episode James Wilson chats with Tinfoil co-founder Tanya Verma about how you can run a powerful LLM in the cloud without the inference provider seeing your prompts. Tanya talks James through how private inference works, from trusted execution environments and hardware attestation, to TLS termination and GPU isolation. Customers can verify the exact code and model processing their data, while Tinfoil and its infrastructure providers remain locked out. That’s clever engineering… but who really needs it? Is private inference only useful if you’re doing something bad, or will it become a privacy baseline like TLS? James and Tanya discuss the costs and trade-offs, and how open weights make private inference more transparent and trustworthy. Show notes

See All (41)

5
out of 5
16 Ratings

About

Join reformed CTO James Wilson as he dives deep on cybersecurity topics through an enterprise lens. From solo content and interviews with CISOs and researchers to vendor and startup deep dives, James does a bit of everything.

Information

  • Creator
    Risky Business Media
  • Years Active
    2026
  • Episodes
    41
  • Rating
    Clean
  • Copyright
    © Copyright Risky Business Media 2007-2026
  • Show Website
    Risky Business Features

You Might Also Like