I accuse your security of being mostly compliance.
Sit down. Argue it. I’ll close with decisions you can ship, not “best practices” you’ll forget.
Not a talk. A public challenge.
I place a provocative statement in the room. People react. We debate with code, architecture and production constraints. Every round ends with a concrete takeaway: a pattern, a guardrail, or a decision you can implement.
Your “secure design” fails at the first attacker.
Let’s test assumptions in public. Faster than a month of internal meetings.
Pick one. Get triggered. Debate.
These are the “sign on the table” starters. Shuffle for the next round.
Use this on a banner, on stage, or as a hallway debate starter.
If it’s not in your design, it won’t appear in your patch.
Security is decided before the first line of code. Let’s argue what you’re missing.
Turn security theater into engineering decisions.
Works as consulting because it exposes blind spots fast, aligns dev and security, and produces an action plan. You leave with decisions teams can implement.
An attraction that creates a crowd and real technical conversation.
Designed for conference floors and dev meetups. High engagement, low production cost, and great content moments.