Birth of the AI CISO — Austin

Who signs for the agent? When an autonomous system makes a security decision, someone still has to answer for it. Nobody has written down who. 20 security leaders, one closed door- a discussion worth joining. The evening 6:00 — Welcome and drinks 6:30 — Moderated discussion 7:30 — Dinner and open conversation What we'll put to the room Three questions. One. What does your organisation already do autonomously that you couldn't stop inside an hour? Two. When an agent gets it wrong, how do you find out and how fast? Three. What's the first control you'd drop if it slowed AI adoption down, and what would you put in its place? What we'll leave to the room The moderator holds the three questions. Everything else comes from whoever's sitting there. Whether an AI-driven incident is reportable, and to whom The shadow AI already running inside business units you don't own Whether you could evidence an agent's decision to an auditor tomorrow The first time an agent did something you had to explain upward. The agents your vendors run inside your environment, and whose model is behind them Who's in the room CISOs, deputy CISOs, and heads of security engineering, risk, or governance at organisations where AI has moved past the pilot stage. Financial services, healthcare, and regulated technology are heavily represented in this edition. The table is capped at 25 — above that, the conversation stops working. Requests are reviewed and you'll hear back either way. Convened by CloudSEK — threat intelligence and attack surface management. We spend our days outside your perimeter, watching what adversaries find before you do. OSec- We help security teams understand what can actually be exploited, how far an attacker can go, which findings matter most, and what to fix first to reduce real-world risk.