
Start the day with a realistic tabletop simulation designed to see how you handle the pressure under fire. From there, you'll dive into hands-on workshops led by seasoned security leaders who are opening up their playbooks and sharing the lessons they've learned firsthand.
Find your people and talk honestly about what's working and what isn't in security today. Between the hallways and post-session chats, you'll grow your circle and strengthen existing relationships to build a trusted network you can lean on long after the event ends.
Keep your certifications up to date while you learn. Every session, workshop, and simulation you attend throughout the day counts directly toward your CPE credits, letting you invest in your career while you connect with the community.
To be Announced
Identity governance was designed around people. Someone joins, changes roles, eventually leaves, and a manager signs off on their access along the way. Service accounts, API keys and AI agents don’t follow that pattern. They get spun up by whoever needed them, collect permissions over time and often stick around long after the project that created them has ended. In this roundtable, we’ll work through what lifecycle governance looks like when a growing share of your identities aren’t human. Who should own an agent once it’s in production? What does an access review mean for something whose behavior can change week to week? When an agent acts with a user’s permissions, whose risk is that? And how do you offboard an identity nobody remembers creating? You’ll leave with a working model for bringing non-human and agentic identities into the governance program you already run, including how to assign ownership and decide which access to tackle first.
To be Announced
Ask a business unit how many AI agents it’s running and you’ll get a number. Go looking yourself and the real count can be a lot higher. Some of those agents live in platforms like Copilot Studio and Agentforce, built by teams that never looped in security. Others run on developer laptops with MCP connections reaching into production code and internal APIs. This session starts with discovery and moves into runtime. We’ll talk through how to keep an inventory accurate when new agents show up every week, then get into the harder problem of what to do when an agent takes an action it’s technically permitted to take but that doesn’t match what the person behind it intended. You’ll walk away with a practical way to sort your agent footprint by where it runs and how much damage it could do, plus a clearer view of where enforcement should sit in the stack you already have.
To be Announced
Are you a member of The CISO Society?