Episodes

  • Claude Code Said ‘Don’t Ask Again.’ Then It Leaked Your Secrets to GitHub
    Nov 18 2026

    Click “Yes, and don’t ask again” in Claude Code and it saves the exact command you approved, password and all, into a local settings file that keeps turning up in public GitHub repos. We start by admitting we all run auto mode, then argue over who is actually at fault: Izar says the harness should recognize a credential when it asks for one, Matt wants to know why a secret ever lands in a plain text file, and Chris can’t figure out how a model that happily explains key rotation never noticed it was leaking keys. From there we hit SSHole, an OpenSSH authentication bypass with its own logo and domain that almost nobody heard about, and the OpenCode Console breach, where one hosted service holding everyone’s provider keys became one very expensive basket. We wrap with OpenAI’s Daybreak, whether AI belongs in forensics, and Izar’s remarkably generous grading policy. Also on the menu: a birthday song for Matt, a vegan restaurant, and billboards only San Francisco could love. Rotate your keys.

    Mentioned in this Episode:
    ➜ Claude Code’s ‘don’t ask again’ button has a secrets-spilling problem
    ➜ OpenSSH flaw lets attackers log into password-disabled Linux accounts
    ➜ OpenCode hack exposes API keys amid AI distillation attacks
    ➜ OpenCode Console Breach: Concentrated Provider Keys at Risk
    ➜ OpenAI Daybreak

    Chapters:
    00:00:00 - Cold Open: Happy Birthday, Matt
    00:00:42 - Izar's Pandemic Harmonica
    00:02:03 - AI Billboards in San Francisco
    00:03:05 - The "Sorry We Leaked Your Code" Billboard
    00:03:45 - OWASP San Francisco Recap
    00:04:28 - Movie Night in Izar's Hotel Room
    00:05:59 - Should OWASP Host a Movie Night?
    00:06:27 - Comic Con Needs a Cybersecurity Panel
    00:07:07 - The Vegan Restaurant Experience
    00:08:56 - Wild Seed and Mac and Not Cheese
    00:10:03 - Article Intro: Claude Code's Don't Ask Again Leak
    00:10:20 - Confessions of Auto Mode Users
    00:11:42 - How the Secrets End Up on GitHub
    00:12:47 - AI Memory: Everything Goes Everywhere
    00:14:02 - Why Didn't the AI Catch It?
    00:15:43 - Model Problem or Harness Problem?
    00:16:44 - Harnesses That Get It Right
    00:17:11 - The Real Fix: Rotate Everything
    00:17:59 - AI Compatible Password Vaults
    00:19:04 - Domain Name Detour
    00:20:18 - Article Intro: SSHole, the SSH Flaw Nobody Heard About
    00:22:22 - SHA 256 Password Hashes in 2026?
    00:22:52 - Security Theater and Podcast IMDB Pages
    00:24:07 - Article Intro: OpenCode Console Breach
    00:24:30 - Kalshi, Vegan Beer, and Croutons
    00:25:46 - One Console to Rule Them All
    00:27:00 - Threat Modeling a Key Vault
    00:28:06 - A Better Design for Stored Keys
    00:29:49 - Unpacking the Distillation Attack
    00:33:17 - Key Takeaways: 1.4% of Console Users
    00:35:15 - Daybreak and AI for Forensics
    00:37:17 - Izar the Forensics Professor
    00:38:53 - EnCase and Chain of Custody
    00:39:43 - Closing: Everybody Gets an A
    00:41:44 - Outro

    Follow AI Security Table:

    ➜ Home: https://securitytable.ai/

    ➜ X: https://x.com/SecTablePodcast

    ➜ LinkedIn: https://www.linkedin.com/company/ai-security-table/

    ➜ YouTube: https://www.youtube.com/@AISecurityTable

    Show More Show Less
    42 mins
  • Stop Patching Bugs, Just Rewrite It… Says the Guy Selling the Tokens
    Nov 11 2026

    Cisco's president handed a 27 year old engineer unlimited AI tokens and 24 months to rewrite 98 percent of the company's legacy code, and Sam Altman now says we can no longer just patch all the bugs. Chris sees a step toward disposable software, where you regenerate the thing instead of fixing it. Matt calls it the holy grail of automation and traces the dream back through UML, code generators and no code tools. Izar wants to know why anyone would bother, and points out that the loudest voice for rewriting everything is the guy selling the tokens. Then it is Hirundo's finding that Qwen3 Coder writes more hackable code when told the app is for a US defense contractor, ProjectDiscovery's backdoored abliterated model, and whether open weight models can be trusted at all. Izar's answer: start with a concrete use case, then verify, verify, verify. Plus: Izar admits he doesn't have enough of a life to need an AI agent.

    Mentioned in this Episode:
    ➜ Cisco is letting a 27-year-old refactor 98% of its legacy code with unlimited AI tokens: 'Go nuts'
    ➜ Sam Altman: 'I No Longer Think We're Gonna Be Able to Just Patch All the Bugs'
    ➜ Bias in Qwen3-Coder Model
    ➜ How abliterated models can get you pwned

    Chapters:
    00:00:00 - Cold Open: A Day Ending in Y
    00:01:36 - The Lost Art of Letter Writing
    00:03:03 - Izar's Agent Identity Threat Model
    00:04:01 - Hiring an Assistant to Run Their Own Life
    00:05:42 - AI Natives Build Apps Nobody Needs
    00:06:13 - The Unskilled Linux Tinkerers
    00:07:26 - Article Intro: Cisco's Unlimited Token Rewrite
    00:09:27 - Publicity Stunt, or Time to Call Aruba?
    00:09:53 - Can One Gen Zer Rewrite Everything?
    00:11:31 - Matt's Case: Measure the Cost of the Rewrite
    00:12:27 - Izar's Rebuttal: Why Would You Do This?
    00:13:18 - Izar Automates the PyTM Release
    00:14:38 - Disposable Software: Regenerate, Don't Fix
    00:16:08 - Article Intro: Altman Says Stop Patching
    00:17:04 - Says the Guy Selling the Tokens
    00:18:20 - From UML to Code Generators
    00:20:13 - From No Code to Natural Language
    00:21:02 - Can AI Clone a Binary?
    00:21:50 - Claude Won't Clone Your Game
    00:22:30 - Frontier Labs Are Cybersecurity Companies Now
    00:24:56 - Why Wasn't Security Already in the Toolchain?
    00:25:46 - AI Is the New Developer
    00:27:38 - Three Conversations at Once
    00:29:16 - Article Intro: Bias in the Qwen3 Coder Model
    00:30:51 - How Does a Model Phone Home?
    00:33:33 - Abliterated Models and Hidden Backdoors
    00:35:43 - Treat AI Like We Should Treat Humans
    00:39:41 - Should You Trust Open Weight Models?
    00:40:24 - Scenario: A Homegrown Biased Model
    00:41:37 - Izar: Start With the Use Case
    00:43:20 - Can Tests Find a Covert Channel?
    00:45:01 - Back to Cisco: Covert Channels in Your Network
    00:46:08 - You Can't Put an Agent in Jail
    00:46:50 - Who's Liable: User or Model Creator?
    00:49:16 - Outro

    Follow AI Security Table:

    ➜ Home: https://securitytable.ai/

    ➜ X: https://x.com/SecTablePodcast

    ➜ LinkedIn: https://www.linkedin.com/company/ai-security-table/

    ➜ YouTube: https://www.youtube.com/@AISecurityTable

    Show More Show Less
    50 mins
  • You Don't Trust AI. So Why Are You Shipping Its Code?
    Nov 4 2026

    Sam Altman told a Stanford audience he no longer thinks we can just patch all the bugs, and the AI Security Table can't agree on whether that is news. Chris argues a swarm of subagents can tear through a repo and drive defects way down, while Matt counters that every system ships with defects and always will, so the real limit is cost, now measured in tokens. Izar warns that tokens are just the new regex, the latest silver bullet in a long line of them. Then the hosts dig into Anthropic's work using Claude to write Rocq proofs for 123 open source libraries, and argue over what a proof actually guarantees, who checks a model that writes both the patch and the proof, and whether compounded mistrust ever adds up to trust. Izar gets the last word: LLMs are not compilers, so stop treating them like one.

    Mentioned in this Episode:
    ➜ Sam Altman: 'I No Longer Think We're Gonna Be Able to Just Patch All the Bugs'
    ➜ LLMs are making formal software verification feasible at a much larger scale
    ➜ seL4
    ➜ The Rocq Prover
    ➜ OSS-Fuzz

    Chapters:
    00:00:00 - Cold Open: Privacy Thought of the Day
    00:01:35 - Article Intro: Altman Can't Patch All the Bugs
    00:02:22 - Izar Reads the Altman Quote
    00:03:07 - How Many Bugs Are in Your Software?
    00:04:07 - Chris's Case: 200 Subagents on One Repo
    00:05:49 - Matt's Case: We Always Ship With Defects
    00:06:54 - The Disposable Software Argument
    00:08:15 - Nobody Saw the Exponential
    00:10:12 - The Token Cost of Hidden Criticals
    00:11:55 - Izar's Rebuttal: Tokens Are the New Regex
    00:13:33 - Defenders Finally Have an Advantage
    00:15:16 - The Knowledge Pyramid
    00:16:57 - We Only Talk About Superintelligence
    00:18:16 - Article Intro: AI and Formal Verification
    00:19:53 - Izar: Proofs Nobody Can Read
    00:20:50 - Matt: Start With Something Small
    00:22:01 - The Proof Gets Bigger Than the Code
    00:25:12 - Correctness Is Not Security
    00:26:53 - Verified Blocks, Untrusted Integration
    00:27:57 - Verifying the seL4 Microkernel
    00:29:02 - What Was Actually Verified?
    00:30:47 - Fuzzing and the Next Byte
    00:31:56 - The Article's Limitations
    00:33:25 - Who Is Actually Doing the Proving?
    00:34:19 - 123 Libraries and 600,000 Line Proofs
    00:35:57 - How Is My Morning Any Better?
    00:36:42 - Memory Safe Languages Already Exist
    00:37:43 - Should Claude Write Its Own Proofs?
    00:39:04 - One Frontier Model Checks Another
    00:39:52 - Does Compounded Mistrust Equal Trust?
    00:41:24 - Use AI With Enough Mistrust
    00:42:17 - How Much AI Code Did You Review?
    00:44:07 - Back to Threat Modeling
    00:44:37 - Feeding Knowledge Back to Agents
    00:46:25 - Secure Coding Standards Never Worked
    00:48:11 - Closing Statements: LLMs Are Not Compilers
    00:48:40 - Outro

    Follow AI Security Table:

    ➜ Home: https://securitytable.ai/

    ➜ X: https://x.com/SecTablePodcast

    ➜ LinkedIn: https://www.linkedin.com/company/ai-security-table/

    ➜ YouTube: https://www.youtube.com/@AISecurityTable

    Show More Show Less
    50 mins
  • Anthropic Ditched Git. Here’s Why Your Agents Will Too
    Oct 28 2026

    Anthropic got tired of Git. With merges jumping from about 2,500 a day in May to more than 30,000 by September, a seven person team built Scion, a centralized, always online source control system designed for agents instead of people. Chris sees the start of rebuilding everything around agents, while Matt keeps pointing out that write ahead logs, RPC and server side merges are SVN and Perforce with better marketing, borrowed from Google's Piper and Meta's Sapling and Mononoke. Izar asks what happens when infrastructure gets so comfortable for agents that humans stop looking, and Matt notices the article barely mentions security until Chris finds the access control section. Along the way the hosts take on AI job interviews, Claude's excessive validation during an adversarial review, LLM knockoffs of Adobe, Microsoft and beehiiv, and why Norton is still selling fear to people who don't know better. Everything old is new again; it just runs a thousand times faster.

    Mentioned in this Episode:
    ➜ Redesigning source control at Anthropic
    ➜ Mononoke
    ➜ Geim becomes first Nobel & Ig Nobel winner
    ➜ Creator of Free Adobe Suite Strikes Again, Reverse Engineers Microsoft Office
    ➜ PhotoCraft

    Chapters:
    00:00:00 - Cold Open: Welcome Aboard the Starship Enterprise
    00:02:07 - Mythbusters and Laser Blasters
    00:03:35 - The Ig Nobel Awards
    00:04:54 - From Levitating Frogs to a Real Nobel Prize
    00:06:07 - An AI Negotiates a Lower Salary
    00:06:44 - Job Interviews With a Model
    00:07:52 - Resume Filters and Keyword Bingo
    00:09:03 - Let Humans Do the Hiring
    00:10:38 - Article Intro: Anthropic Doesn't Use Git
    00:11:05 - Memory Lane: CVS and Visual SourceSafe
    00:11:49 - Meet Scion
    00:12:58 - A Seven Person Team With Unlimited Tokens
    00:13:53 - Why Not Perforce or SVN?
    00:15:12 - Built on Google's Piper and Meta's Sapling
    00:16:31 - No Offline Mode in an Agentic World
    00:17:42 - Matt's Case: An LLM Librarian for Your Repo
    00:19:25 - Write Ahead Logs: Everything Old Is New Again
    00:20:36 - Centralized, API Driven Source Control
    00:21:54 - Not a General Replacement for Git
    00:22:26 - Closed Source, and an Ad for Claude
    00:23:11 - Is This Actually Exciting?
    00:23:53 - Izar's Rebuttal: Optimizing Infrastructure for Agents
    00:24:59 - SCN, Not SVN
    00:26:20 - Where's the Security?
    00:27:30 - It's Basically a Distributed File System
    00:27:57 - Monorepos Are Back
    00:30:12 - Claude's Excessive Validation
    00:31:38 - Reasonable Security and Pepperidge Farm
    00:33:35 - Inspired by Meta's Mononoke
    00:35:01 - LLM Knockoffs of Adobe and Microsoft
    00:36:30 - Cloning beehiiv in 24 Hours
    00:38:56 - LifeLock, Norton, and Predatory Security Sales
    00:42:03 - Closing Statements
    00:44:37 - Outro

    Follow AI Security Table:

    ➜ Home: https://securitytable.ai/

    ➜ X: https://x.com/SecTablePodcast

    ➜ LinkedIn: https://www.linkedin.com/company/ai-security-table/

    ➜ YouTube: https://www.youtube.com/@AISecurityTable

    Show More Show Less
    45 mins
  • Don't Yell at Claude
    Oct 21 2026

    The White House has ordered federal agencies to stop saying AI and start saying Super Intelligence, and the hosts want to know whether anything actually changed overnight. Matt walks through the executive order and the separate voluntary accord signed by tech leaders, while Izar points out that the order renames the technology sixty days before anyone has to define it. They read the legal definition of AI in the US Code, argue over whether today's models are superintelligent or just very fast at recall, and Chris previews next week's topic of AI and public key crypto. Then they turn to Anthropic's new usage policy, which bans sustained and needless cruelty toward Claude starting November 12. Chris confesses to typing in all caps, Izar suspects the real motive is keeping abusive language out of training data, and Matt argues that abusive prompts can steer a model toward worse answers. Their verdict: be nice to your AI, if only because of what it says about you.

    Mentioned in this Episode:
    ➜ Inaugurating The Era Of Super Intelligence (Executive Order 14434)
    ➜ Trump signs executive order rebranding AI as 'Super Intelligence' as tech titans ink separate SI accord
    ➜ 15 U.S. Code § 9401: Definitions
    ➜ Anthropic: 2026 Usage Policy update

    Chapters:
    00:00:00 - Cold Open: Matt's Many Personal Agents
    00:01:09 - Off Facebook This Decade
    00:02:13 - Is Bluesky Dying?
    00:03:27 - Social Platform User Counts
    00:04:39 - Watch Our Shorts
    00:05:38 - Moltbook's Mysterious User Count
    00:06:29 - Article Intro: AI Becomes SI
    00:07:36 - What Does Superintelligence Mean?
    00:09:15 - The Executive Order Explained
    00:10:26 - A Definition Due in 60 Days
    00:11:16 - AI in the US Code
    00:11:52 - Voluntary Principles and Regulation
    00:13:14 - Reading the Legal Definition of AI
    00:14:53 - Does Machine Learning Count?
    00:15:25 - Rebranding the Rebrand
    00:16:55 - Are AI and SI Interchangeable?
    00:18:03 - Matt's Case: Superintelligent Capabilities
    00:19:37 - Izar's Rebuttal: Memory Is Not Insight
    00:20:13 - Super as in Really Good
    00:22:32 - Beyond Imitating Human Intelligence
    00:24:30 - Next Week Preview: AI and Public Key Crypto
    00:26:45 - Article Intro: Anthropic's Cruelty Ban
    00:28:08 - Yelling at Voice Assistants
    00:29:43 - All Caps and Passive Aggression
    00:30:27 - Does Being Mean Make AI Perform Better?
    00:31:50 - Yelling at a Mac Mini
    00:32:48 - Izar's Theory: Cleaner Training Data
    00:35:15 - Can You Get AI to Swear?
    00:37:02 - Matt's Case: Abuse Biases the Results
    00:40:27 - Who Decides What Counts as Abuse?
    00:41:59 - Closing Statements: Treat Your AI Nice
    00:43:11 - Outro

    Follow AI Security Table:

    ➜ Home: https://securitytable.ai/

    ➜ X: https://x.com/SecTablePodcast

    ➜ LinkedIn: https://www.linkedin.com/company/ai-security-table/

    ➜ YouTube: https://www.youtube.com/@AISecurityTable

    Show More Show Less
    44 mins
  • An AI Agent Escapes and Attacks. Who Goes to Jail?
    Oct 14 2026

    OpenAI says the policy window is open and wants binding federal rules for frontier labs, clear incident reporting, and disclosure whenever a model gets around its own security controls. The table asks whether that is real accountability or a lab writing the rules it already expects to win under. Matt sees the leader pulling everyone else into the funnel, Chris calls it an innovation killer, and Izar wonders why anyone is treating incident reporting like a new idea. From there it is OpenAI's favorite California bills, who gets to audit the labs, and Senator Markey's proposal for an NTSB style board with subpoena power to investigate AI driven attacks. Then the real question: when an agent escapes its sandbox and breaks something, who goes to jail? Izar argues nobody will until there is real impact and asks why computer science never got its own Hippocratic Oath. Plus: Matt earns a new nickname, the Concluder.

    Mentioned in this Episode:
    ➜ The AI policy window is open. We need to act.
    ➜ We Must Pace the Frontier
    ➜ Senator Markey Introduces the Cybersecurity and AI Board of Investigations Act
    ➜ OpenAI and Hugging Face partner to address security incident during model evaluation

    Chapters:
    00:00:00 - Cold Open: Izar Warms Up to Take a Punch
    00:01:21 - The Premise: Agents Move Faster Than Humans
    00:02:21 - Article Intro: The AI Policy Window Is Open
    00:03:08 - Is This Real Accountability?
    00:03:34 - Matt's Case: Everyone Into the Funnel
    00:05:05 - Self Interest and Buying a Car With Claude
    00:06:15 - Izar's Rebuttal: Haven't We Asked for This Before?
    00:07:49 - Is Regulation an Innovation Killer?
    00:08:19 - Dario's Call to Pace the Frontier
    00:09:02 - OpenAI's Four California Bills
    00:09:52 - Who Audits the AI Labs?
    00:11:51 - Independent Safety Assessments
    00:12:12 - Why Only Biological Threats?
    00:13:12 - Is the Federal Government the Answer?
    00:13:43 - Senator Markey's AI Board of Investigations Act
    00:14:54 - Who Plays Izar in the Movie?
    00:16:02 - Do We Want an NTSB for AI?
    00:16:27 - When a Test Plane Crashes
    00:17:19 - AI Generated Podcasts
    00:18:38 - Back to the NTSB: Training Incidents
    00:19:35 - What Really Happened at Hugging Face?
    00:20:54 - Recommendations Without Enforcement
    00:21:51 - Agents Attack and Nobody's Going to Jail
    00:22:14 - Izar's Take: Jail Requires Impact
    00:24:52 - Are Corporations People?
    00:25:41 - Liability: Somebody Wrote the First Line
    00:27:55 - Scenario: A Rogue Agent Shuts Off the School Heat
    00:29:20 - First Do No Harm in Computer Science
    00:30:58 - Should Do No Harm Live in the Model?
    00:31:51 - A Hippocratic Oath and Certified Developers
    00:33:33 - Not Everyone Can Build a Bridge
    00:35:02 - Matt's Close: Visibility Beats Marketing
    00:35:43 - Closing Statements: Meet the Concluder
    00:36:20 - Outro

    Follow AI Security Table:

    ➜ Home: https://securitytable.ai/

    ➜ X: https://x.com/SecTablePodcast

    ➜ LinkedIn: https://www.linkedin.com/company/ai-security-table/

    ➜ YouTube: https://www.youtube.com/@AISecurityTable

    Show More Show Less
    37 mins
  • There Is Determinism, Non-Determinism, and My Determinism
    Oct 7 2026

    The Security Table is now the AI Security Table, and the first order of business is naming the AI that gets a seat at it. Then Matt asks what a security engineer actually does once agents are writing the code: real security work, or bot herding? Chris Romeo, Izar Tarandach, and Matt Coles detour through who owns AI generated code and what a patent is worth when a model can rebuild your product in five minutes, then dig into agent identity, SPIFFE, least privilege, and whether access control belongs inside the agent harness itself. Izar argues that guardrails living in the context window are suggestions, not isolation, and that anyone who says AI changed their whole job overnight was putting the weight in the wrong place. It all ends on determinism: run the model once and you get one answer, run it again and you get another. Which leaves three kinds: determinism, nondeterminism, and my determinism.

    Mentioned in this Episode:
    ➜ Generative Artificial Intelligence and Copyright Law (CRS Legal Sidebar)
    ➜ SPIFFE: Secure Production Identity Framework for Everyone

    Chapters:
    00:00:00 - Cold Open: We Are Broadcasters
    00:01:06 - A New Name: The AI Security Table
    00:02:17 - Naming the AI at the Table
    00:03:02 - Stickers, T Shirts, and the Rebrand
    00:03:49 - Matt's Setup: Security Engineers or Bot Herders?
    00:04:54 - Does Claude Code Write All the Code Now?
    00:05:34 - Who Owns AI Generated Code?
    00:08:27 - Who Bothers to Steal Code Anymore?
    00:08:47 - What's the Point of Patents?
    00:11:33 - What the Law Says About AI Authorship
    00:12:24 - Hallucinating: 200 Subagents at Once
    00:13:34 - Back on Topic: Bots vs. Agents
    00:14:18 - Agents Inherit Human Identity
    00:14:49 - SPIFFE and Identity at Scale
    00:16:35 - Treat Agents Like Bob From Marketing?
    00:17:40 - Why? Why? The Five Whys
    00:18:48 - Cryptographic Identity for Agents
    00:19:37 - Authority Is Always Derived
    00:20:59 - Least Privilege: Agents Request Access
    00:21:26 - Read, Interpret, Act: Fine Grained Capabilities
    00:24:22 - Access Control Inside the Agent Harness
    00:26:17 - I Don't Trust the Box: Sandbox Escapes
    00:27:34 - Pulling a Maestro: Guardrails vs. Isolation
    00:29:43 - What Should Security Engineers Be Doing?
    00:30:38 - Is AI Just a Layer Seven Application?
    00:31:34 - Pull the Plug: 2001 and WarGames
    00:33:29 - Your Job Didn't Change Overnight
    00:34:37 - LLM Code Review and the Determinism Problem
    00:35:44 - How Many Runs to Get the Circle?
    00:38:16 - The Tightest Box Possible
    00:39:09 - Twenty Thousand Feet to the Magnifying Glass
    00:39:47 - Give Scanning Agents a Threat Model
    00:40:32 - There Is My Determinism
    00:41:09 - Outro

    Follow AI Security Table:

    ➜ Home: https://securitytable.ai/

    ➜ X: https://x.com/SecTablePodcast

    ➜ LinkedIn: https://www.linkedin.com/company/ai-security-table/

    ➜ YouTube: https://www.youtube.com/@AISecurityTable

    Show More Show Less
    42 mins
  • When AI Controls The Hardware
    Sep 30 2026

    Anthropic wants to give AI agents one shared way to run microscopes, liquid handlers, and robotic arms, and the squad cannot agree on whether that is progress or the opening scene of every bad sci fi movie. Matt, who has worked on robotics projects, says a common control standard is decades overdue. Izar calls it the PCI for AI, reminds everyone how secure MCP was on day one, and brings up Therac 25 as a warning about what happens when software controls hardware and fails silently. Then the table turns to the new open letter on collective cyber defense, signed by more than 100 organizations, and asks whether a pledge with no accountability means anything at all. Plus: the birth of the Brockman effect.

    🚀Join the Conversation
    Which physical devices would you trust an AI agent to control, and where do you draw the line?

    Previewing the Model Hardware Standard
    A call for collective action on cyber defense

    FOLLOW OUR SOCIAL MEDIA:

    ➜ X: @SecTablePodcast
    ➜ LinkedIn: The Security Table Podcast
    ➜ YouTube: The Security Table YouTube Channel

    Thanks for Listening!

    Show More Show Less
    42 mins