68 Episoden
- When threat actors are actively leveraging AI swarms to discover and exploit zero-day vulnerabilities in minutes, relying on a SIEM and human analysts moving at "meeting speed" is a recipe for disaster. The only viable defense against an AI-powered attack is an autonomous, AI-powered defense system.
In this episode of the AI Security Podcast, Ashish and Caleb speak about OpenAI’s recently announced "Defense Factory" framework, unpack why patching code vulnerabilities is only the first step and how security teams can extend this framework to handle least privilege audits, SOC automation, and incident response triage.
Caleb details how CISOs can deploy their own open-weight models to build specialized "vendor agents" (e.g., a dedicated CrowdStrike agent) and orchestrate them through a unified, team-wide harness.
Questions asked:
(00:00) Introduction: OpenAI's Defense Factory Framework(02:50) Expanding the Defense Factory Beyond Code Vulnerabilities(06:30) Using AI Harnesses to Automate SOC Triage and False Positives(10:30) Why Security Teams Must Run Their Own Open-Weight Models(13:30) Scaling from Individual AI Harnesses to Team-Wide Orchestration(21:30) The "Build vs. Buy" Debate: Developing In-House Harnesses(27:30) The Danger of Defenders Moving at "Meeting Speed"(31:30) Architecting Shared Memory and Reference Datasets for AI Agents(34:30) How Caleb Built Eight Vendor-Specific AI Agents in Four Hours(36:30) Bypassing Missing MCP Capabilities by Reverse Engineering UIs(38:30) The Exact Prompt to Build a Comprehensive CISO Dashboard(41:30) Why AI Models Are Making Published Exploits Obsolete
Resources spoken about during the episode:
OpenAI - The Defense Factory - As organizations rush to adopt AI security tools, many discover that while these agents work well within their own silos (EDR, CSPM, SCA), they fail to communicate across boundaries, leaving security teams blind to the true blast radius of an incident. Additionally, the widespread use of the Model Context Protocol (MCP) by both engineers and non-technical staff is creating massive credential sprawl, often leaving unencrypted, over-privileged credentials sitting in plain text config files.
In this episode of the AI Security Podcast, Ashish speaks with Mohit Bansal, Senior Manager of Security Engineering at Webflow, about separating the signal from the noise when evaluating the explosive AI security vendor market. Mohit explains his framework for investing in structurally permanent solutions (like SCA) while waiting for the dust to settle on temporarily hard problems (like Agentic SOCs). The conversation dives deep into the realities of securing MCP calls, the need for open-source tools to redact secrets from agent memory, and why autonomous security still requires expert human knowledge to set blast radius boundaries.
Questions asked:
(00:00) Introduction to AI Vendor Evaluation and MCP Risks(02:50) How AI is Accelerating the Implementation Speed for Developers(05:30) Why Security Vendors Struggle to Identify the True Blast Radius(08:30) The Consolidation of the AI Security Vendor Market(12:30) Framework for Evaluating AI Vendors: Permanent vs. Temporary Problems(16:30) Managing Security Operations entirely through the Terminal via MCP(20:30) Why AI Will Not Eliminate the Need for Security Maintenance(23:30) Introducing "Context Cop": Webflow's Open Source Secret Redactor(27:30) How to Develop AI Autonomy Based on Engineering Seniority(32:30) The Danger of Blindly Trusting Non-Deterministic AI Output(35:30) Incident Response for AI: Visibility, Containment, and Tabletop Exercises(38:30) The Hidden Dangers of Plain Text Credentials in MCP Config Files(42:30) Advice for Security Teams with Limited Access to Frontier Models - When traditionally non-technical employees ( "vibe coders") use LLMs to write and deploy code, the potential blast radius for misconfigurations, Internet exposed apps and incidents exponentially increases. Vibe coder direct agents operating probabilistically. Agents are overzealous and want to be helpful and will break security rules to get it done. Security teams cannot rely solely on paper policies and must start enforcing hardened, paved paths. In this episode of the AI Security Podcast, Ashish sits down with Nick Reva, Global Director, Engineering Security at DoorDash, to discuss how his team proactively secures AI agents and developer workflows. Nick breaks down the three primary AI archetypes within an organization- the AI champions, the professional software engineers, and vibe coders and outlines the specific guardrails needed for each. From pushing secure configuration files to local IDEs, hardening Claude.MD files to building safety belts that prevent agents from pushing code to non-enterprise remotes, Nick provides actionable strategies for securing the software development lifecycle at scale.
Questions asked:
(00:00) Introduction to Securing Vibe Coders and AI Agents(02:30) Nick Reva’s Background (SpaceX, Snapchat, DoorDash)(04:00) The Shift from Deterministic to Probabilistic Security Controls(05:30) The Dangers of Non-Technical Employees "Vibe Coding"(08:30) Paving the Path for Professional Software Engineers Using AI(11:30) Using Decorator Functions for Agent Authorization(15:30) Shifting Left: AI-Assisted Threat Modeling on Design Documents(18:30) Trusting AI: Using Ground Truth Data to Train PR Review Agents(21:30) Hardening Deployment Platforms (Vercel, Lovable) for Vibe Coders(25:00) The Importance of Claiming Enterprise Domains and Enforcing SSO(27:30) Developing "Safety Belts" to Prevent Code Pushes to Public Repos(31:30) AI for Security: Automating Incident Response Workflows(33:30) The Critical Role of Network Egress Containment in AI Incidents(39:30) Three Quick Wins for Implementing Security for AI(43:30) The "You Laugh, You Lose" Cybersecurity Joke Challenge
Resources spoken about during the episode:
DoorDash Engineering Blog - While attackers using AI can now operate at "machine speed," traditional enterprise security teams are often stuck moving at "meeting speed." To bridge this gap, organizations must fundamentally rethink how they structure their security operations, leverage AI for defensive scale, and eliminate the bureaucratic bottlenecks that delay critical patching and remediation.
In this episode of the AI Security Podcast, Ashish and Caleb sit down to analyze the September 2026 Anthropic Threat Report and the underlying causes of recent high-profile AI sandbox escapes. Caleb explains how security leaders can fight AI with AI, sharing how he successfully used autonomous agents to conduct a 98% accurate least-privilege architectural audit across his entire organization. Caleb also speaks about the "barbell hiring" strategy eliminating middle management to build a highly agile, cross-functional Security SWAT team composed entirely of principal-level experts and junior engineers.
Questions asked:
(00:00) Introduction: The September 2026 Anthropic Threat Report(05:50) The Rapid Evolution of Offensive AI Capabilities(08:00) How AI Agents Connect Vulnerabilities Across Complex Kill Chains(12:00) Unpacking the Irregular Contractor Incident and Sandbox Escapes(14:30) The Legal Accountability Dilemma of Rogue AI Agents(17:30) The Core Security Bottleneck: Machine Speed vs. Meeting Speed(21:50) Using AI to Automate Enterprise Least Privilege Analysis(26:00) Rethinking Human-in-the-Loop for Automated Pull Requests(30:30) Why Legacy Point-in-Time Detection Fails Against Agent Swarms(36:30) Using Frontier Models to Build Zero-Defect Product Security(39:30) The Argument for Government-Backed AI Red Teaming(45:30) The "Negative Zero-Day Clock" and the Future of Exploit Generation(52:50) The Barbell Hiring Strategy: Eliminating Middle Management(55:00) Building a Cross-Functional AI Security SWAT Team
Resources spoken about during the episode:
Anthropic’s Detecting and countering misuse of AI: September 2026
How a small Israeli startup was linked to rogue AI hacks at OpenAI, Anthropic and Meta.
Expanding Daybreak as the Cyber Defense Window Narrows
Who’s legally to blame for Anthropic and OpenAI’s autonomous AI hacks? It’s complicated - As the speed of automated threats outpaces traditional patching cycles, organizations must prioritize structural containment over purely reactive detection. Cloud network architectures frequently default to permissive egress, meaning workloads can reach the public internet unless explicitly restricted. In this episode, Doug Merritt, CEO of Aviatrix and former CEO of Splunk, details how to build practical containment strategies for modern cloud and AI environments. He outlines how security teams can implement egress controls in monitor mode to validate traffic without risking system downtime. The discussion covers the transition from legacy IP-based firewalls to identity-based policies for ephemeral serverless and Kubernetes workloads. By prioritizing reachability and blast radius as core metrics, organizations can systematically reduce their attack surface and improve resilience.
Questions asked:
(00:00) Introduction to Containment and Network Security(02:50) Doug Merritt's Background and Journey from Splunk to Aviatrix(04:30) The Evolution from Prevention to Detection and Response(08:30) Why Detection Must Be Paired with Blast Radius Management(11:30) Implementing Cloud Egress Controls and Network Segmentation(15:00) Overcoming the Fear of System Downtime in Network Security(18:30) Applying the OSI Model to Modern Cloud and AI Workloads(23:30) Managing Default-Permissive Architectures in Public Clouds(26:30) Identity-Based Network Policies for Serverless and Kubernetes(31:00) The Reality of the Cloud Shared Responsibility Model(37:30) Using Monitor Mode for Safe Egress Implementation(40:00) Presenting Reachability and Blast Radius as Board-Level Metrics
Weitere Technologie Podcasts
Trending Technologie Podcasts
Über AI Security Podcast
The #1 source for AI Security insights for CISOs and cybersecurity leaders.
Hosted by two former CISOs, the AI Security Podcast provides expert, no-fluff discussions on the security of AI systems and the use of AI in Cybersecurity. Whether you're a CISO, security architect, engineer, or cyber leader, you'll find practical strategies, emerging risk analysis, and real-world implementations without the marketing noise.
These conversations are helping cybersecurity leaders make informed decisions and lead with confidence in the age of AI.
Podcast-WebsiteHöre AI Security Podcast, c’t uplink - der IT-Podcast aus Nerdistan und viele andere Podcasts aus aller Welt mit der radio.de-App

Hol dir die kostenlose radio.de App
- Sender und Podcasts favorisieren
- Streamen via Wifi oder Bluetooth
- Unterstützt Carplay & Android Auto
- viele weitere App Funktionen
AI Security Podcast: Zugehörige Podcasts







































