Detail A · The signatories
The people whose word settles it
Every vendor sounds the same, so nothing gets decided. We brought people with no reason to agree with each other. What changed, what to do about it, and how enterprises are already proving it works.
View 01
View 02
View 03
.png)
View 04
.png)
View 05
View 06
Agenda · Session 1 · Opening keynote
Duration · 20 to 25 mins
Three Decades in Security.
This One Is Different.
Mikko Hyppönen
In this session Mikko Hyppönen sets out what actually changed. Four numbers, one conclusion: you cannot patch, schedule, or predict your way out of this. He has watched every prior shift in this industry, and he speaks as an independent voice, so you get the picture as it is rather than as a vendor would frame it.
Agenda · Session 2 · The Answer
Duration · 25 to 30 mins
Proof at Machine Speed
Volkan Erturk, Co-founder and CTO, Picus Security
This is one of the most important sessions you will attend this year. Volkan Erturk shows how to be ready for Mythos-class attacks: why you cannot patch past the volume, why weekly testing cannot hold against daily change, and what closes both.
Agenda · Session 3 · The Demo
Duration · 15 to 20 mins
See It Run: The Loop, Live
RC Christopher and Autumn Stambaugh, Picus Security
In this session our architects walk a real day, live in the product, nothing pre-recorded.
- 08:00A brand new vulnerability lands. No patch, no working exploit, and your board is already asking whether you are exposed.
- 08:30You validate the chain the CVE would need and get an answer while everyone else is still waiting for one.
- 10:00A working proof of concept appears. You fire it safely at your own controls and see exactly what blocked and what missed.
- 11:00The fix ships and the attack path is re-validated as closed, before the day is out.
Agenda · Session 4 · CISO Fireside
Duration · 30 mins
Hear It From the CISOs:
Preparing for Mythos-Class AI Attacks
Security leaders from Chanel, Atlassian and National Football League (NFL)
Three peers answer the questions your board is asking. What they changed, what they stopped doing, what broke on the way, and how they got comfortable letting the loop run with a named human still signing off. You leave with precedent you can cite internally.