The Security Table is a cybersecurity panel show built around argument, correction, and practical skepticism. It rarely enters through the front door. A loose opening about Vegas, medical dramas, black shirts, old slogans, or whatever is happening on someone’s video feed can turn into a precise question about risk, access, automation, or trust. That looseness is part of the method. Chris Romeo, Matt Coles, and Izar Tarandosh sound less like presenters delivering segments than practitioners trying to force vague security claims into testable shape. Recent episodes spend real time on AI agents, but the show keeps dragging the subject back to ordinary security ground. Tokens matter. Service accounts matter. API keys matter. Prompt injection matters less when the larger issue is over-agency and real access to real systems. The same grounded pressure shows up in conversations about agentic ransomware, where the panel questions what the label proves, what the code comments reveal, and whether the evidence really supports the hype. AppSec tools get similar treatment. DAST, SAST, false positives, linters, and AI-assisted triage are judged by how they behave in workflows, not by how impressive they sound in a claim. The invisible-code discussion is especially typical: the panel moves from character scanning and package repositories to the harder question of where malicious behavior becomes executable and stoppable. Privacy and security are treated as recurring tradeoffs rather than slogans. Risk is not outsourced to a dashboard. In the episode with Brooke Schoenfeld, the conversation stretches into storytelling, responsibility, and the discipline of explaining risk without surrendering judgment to whoever argues most cleverly. The show can be funny, but the humor is usually doing work. It resets the room, then gives the next technical objection a sharper edge. Listeners should expect shorthand, side paths, and occasional old-internet references. They should also expect the central question to keep returning: does this mitigation, tool, or AI feature actually reduce risk where people build and ship software?