Just released a new episode, #521: Red Teaming LLMs and GenAI with PyRIT with guests Tori Westerhoff and Roman Lutz + host @mkennedy #python

Are you worried about LLMs, Agents, and security? Give it a listen?

https://talkpython.fm/episodes/show/521/red-teaming-llms-and-genai-with-pyrit

Red Teaming LLMs and GenAI with PyRIT

English is now an API. Our apps read untrusted text; they follow instructions hidden in plain sight, and sometimes they turn that text into action. If you connect a model to tools or let it read documents from the wild, you have created a brand new attack surface. In this episode, we will make that concrete. We will talk about the attacks teams are seeing in 2025, the defenses that actually work, and how to test those defenses the same way we test code. Our guides are Tori Westerhoff and Roman Lutz from Microsoft. They help lead AI red teaming and build PyRIT, a Python framework the Microsoft AI Red Team uses to pressure test real products. By the end of this hour you will know where the biggest risks live, what you can ship this quarter to reduce them, and how PyRIT can turn security from a one time audit into an everyday engineering practice.

@talkpython @mkennedy I'm getting 404s for this episode on the feed. Deja vu. :)
@_chrismay @talkpython Thanks. I’ll have a look. I probably misnamed the ad free version. Can’t look for an hour but should be fixed after.
@mkennedy @_chrismay @talkpython wait... there's an ad-free version I could be paying for? I could support your show and get to skip the ads? That's awesome! How do we sign up?
@edrogers @_chrismay @talkpython Hey Ed! Thanks a bunch. This was part of the talk python training bundle extras. But I've discontinued that for something much better that is coming soon. Been working on it for a month or so. I’ll share more soon, thank you!
@_chrismay @talkpython Look at this Chris. After messing things up a couple of times (the pro edition was missing the ’t’ in pyrit), I decided we're going full guard rails and wrote a whole mp3 file management and naming UI frontend for the website. This *should* mean this never happens again. We'll see!