0x03 Call for papers

Submissions on cfp.directory

Call for papers

Talks and workshops from people who build, break and defend things. First-time speakers are welcome.

Opening soon

Opens 25 October 2026. Start your draft now.

Opens
25 October 2026
Closes
6 December 2026
Decisions by
15 January 2027
On stage
3–4 April 2027

01 Formats

Pick a format

A length is a budget, not a target. Fifteen good minutes beat forty-five padded ones.

  • 45min talk

    Technical talk with questions. The main track on day two.

  • 150min workshop

    Hands on, everyone with a laptop. Workshops run on day one.

  • 15min lightning talk

    One sharp idea. A good first time on stage.

02 What we look for

No fixed tracks

Submit the talk you want to give. These are what we tend to say yes to, not filters.

  • Work you did

    Something you built, broke, reversed or cleaned up. First-hand beats a summary.

  • Findings and failures

    A bug and how you found it. An incident and what it cost.

  • Defence too

    Detection, response, hardening, threat modelling, appsec that shipped.

  • A local edge

    Systems, rules, fraud and infrastructure specific to India and the region.

  • Tools, shown live

    Welcome with a live demo and public code. Otherwise it is a product pitch.

  • Depth a beginner can follow

    Students and principal engineers share the room. Start simple, go deep.

See all 28 topic tags
  • Offensive security
  • Red team
  • Penetration testing
  • Blue team
  • Application security
  • DevSecOps
  • Cloud security
  • IoT security
  • API security
  • GraphQL security
  • Mobile security
  • Network security
  • Hardware hacking
  • Reverse engineering
  • Malware analysis
  • Threat intelligence
  • Incident response
  • Digital forensics
  • Cryptography
  • Bug bounty
  • Vulnerability research
  • AI security
  • OSINT
  • Insider threat detection
  • Web application security
  • Blockchain security
  • Supply chain attacks
  • Deepfakes

03 Your proposal

What to send

It does not need polish. Five volunteer reviewers read every one.

Include

  • A clear title. The subject should be obvious from it.
  • An abstract. Two or three paragraphs: problem, what you did, result.
  • What is new. One line is enough.
  • What people take away. A technique, a tool, a warning.
  • Where you gave it before, if anywhere. That is allowed.
  • If it is your first talk. Say so. It helps you.

Leave out

  • A bio longer than three lines
  • A photo
  • Your company name
  • A slide deck
  • Certifications

04 First-time speakers

Never spoken before? Good.

  • Say it is your first

    No penalty. We read for the idea, not the packaging.

  • Ask before you submit

    Send a paragraph to [email protected]. We help shape it.

  • Practise with us

    If accepted, someone on the team does a practice run with you.

05 What you get

Nobody is paid. Here is the rest.

The same for every accepted speaker. Need something else? Ask before you submit.

Pass
Free pass to both days
Hospitality
Lunch, coffee and a speaker room to prepare in
Dinner
A seat at the speaker dinner
Discount
A ticket discount code in your name
Feedback
An answer either way by 15 January 2027A no comes with what the reviewers thought.
Fee
NoneNo one speaking at or organising a BSides is paid.
Travel and stay
Not promised yetIf cost decides whether you can come, say so in your submission.
Recording
Your choiceSaying no does not affect selection. Speaker terms

06 If you are accepted

From yes to stage

22 January 2027
Confirm your place
25 January 2027
Speakers announcedOnly after every submitter has heard back.
1 February 2027
Programme mostly final
14 February 2027
Outline checkStructure only, not finished slides.
7 March 2027
Draft materials
15–21 March 2027
AV checks and rehearsals
28 March 2027
Final materials

07 Questions

Speaker questions

Ask the CFP team: [email protected]

Can I submit more than one idea?

Yes. Send each as its own submission so each is read on its own.

Can I present remotely?

0x03 is planned in person and remote talks are not decided. If travel is not possible, say so in your submission.

Can I talk about my company's product?

Not as the subject. Technical work behind a product is welcome. A product walkthrough is a sponsor conversation.

I am not sure it is good enough.

Submit it. The worst case is a no from volunteers who read it carefully and tell you why.

What if I miss the deadline?

We cannot promise to read a late submission, but write to [email protected] anyway.

Everyone who speaks agrees to the code of conduct.