[ broadcast // status ]
CFP is transmitting
We want talks with substance. If you've got a demo, a diff, a war story, or a weird bug worth showing, submit it. First-time speakers get mentored. Rookies and repeat offenders welcome.
[ trajectory // timeline ]
M-6
CFP opens
◉May 2026
M-3
CFP closes
◉August 2026
M-2
Speaker notifications
◉September 2026
M-0
Launch day
◉November 2026
[ signal // what we want ]
Bring the signal
- ▸Technical deep-dives: offensive, defensive, reverse engineering
- ▸Hardware, firmware, and embedded research
- ▸Malware analysis, threat intel with substance
- ▸Cloud security, identity abuse, supply-chain work
- ▸AI/ML security with a demo or a diff
- ▸War stories: what you did, what broke, what you'd do differently
- ▸Practitioner workshops (60 to 90 min) and tutorials
- ▸First-time speakers, we actively mentor
[ static // what we skip ]
Leave the noise
- ✕Vendor pitches dressed up as talks
- ✕Rehashed conference circuit material from the last three years
- ✕"AI will solve X" without a demo, diff, or data
- ✕Theoretical cryptography without a concrete attack
- ✕Compliance-as-a-talk
[ protocol // how to submit ]
Submission
The official CFP form opens in May. Until then, email drafts or talk ideas to cfp@bsidesjax.org and we'll help shape the pitch. First-time speaker? Say so. We pair you with a mentor to polish the talk before it hits the stage.
$ grep -i "first time speaker" /cfp/guidance.txt
→ yes. please submit. we'll work with you.
→ yes. please submit. we'll work with you.