How to Submit a Talk to BSides

A practical guide to getting your talk accepted at a BSides security conference

Open CFPs Right Now

USA, Iowa, Des Moines — 13 Jun 2026
2026-04-30 (closing soon!)
Submit →
Israel, Tel Aviv — 25 Jun 2026
2026-04-30 (closing soon!)
Submit →
USA, Texas, San Antonio — 13 Jun 2026
2026-05-01 (closing soon!)
Submit →
Poland, Krakow — 26 Sep 2026
2026-05-31
Submit →
UK, England, Basingstoke — 31 Jul 2026
2026-06-01
Submit →
UK, Northern Ireland, Belfast — 10 Sep 2026
2026-06-06
Submit →
Estonia, Tallinn — 24 Sep 2026
2026-07-31
Submit →
Croatia, Zadar — 11 Sep 2026
2026-08-05
Submit →

What is a CFP?

A Call for Papers (CFP) is an open invitation for speakers to submit talk proposals. Most BSides events publish a CFP a few months before the conference, review submissions, and notify accepted speakers 2-6 weeks before the event.

BSides CFPs are typically managed through platforms like Sessionize, Google Forms, or the event's own website. The process is usually straightforward: fill out a form with your talk title, abstract, and bio.

Writing a Strong Abstract

Your abstract is the most important part of your submission. Reviewers read dozens or hundreds of them, so make yours stand out.

1. Lead with the problem

Start by describing the problem or question your talk addresses. Reviewers want to know why the audience should care before they learn what you'll cover.

Good: "Most container security tools miss runtime threats because they only scan images at build time. This talk demonstrates three techniques for detecting container escapes in production."

2. Be specific about what attendees will learn

Vague abstracts get rejected. Instead of "I'll discuss cloud security," say exactly what the audience walks away with: a tool, a technique, a framework, a case study.

3. Keep it concise

Two to three paragraphs is ideal. First paragraph: the problem. Second: your approach or what you'll cover. Third (optional): why you're the right person to give this talk.

4. Show, don't just tell

Talks with demos, tools, or real-world case studies are strongly preferred over purely theoretical presentations. If you built something, released a tool, or investigated an incident, say so.

Common mistake: Submitting a vendor pitch or product demo disguised as a talk. BSides events are community-driven and reviewers will reject marketing content.

First-Time Speaker Tips

BSides is the best place to start

BSides events are specifically designed to be welcoming to new speakers. Many have dedicated first-timer tracks or mentorship programs. Don't let impostor syndrome stop you.

You don't need to be an expert

Some of the best BSides talks come from people sharing something they recently learned. "I spent a weekend reversing this IoT device and here's what I found" is a perfectly valid talk.

Start local, then expand

Submit to your nearest BSides first. Smaller events often have higher acceptance rates and more supportive audiences. Once you have one talk under your belt, submit it to other events.

Talk length

Most BSides talks are 20-30 minutes. Some events offer lightning talks (5-10 minutes), which are a great way to ease into speaking.

Watch talks from past BSides events

The single best preparation is seeing what the BSides crowd has actually presented. Browse the archive of recorded BSides talks — filter by chapter, speaker, or year, and watch a few in the style of talk you want to give. You’ll pick up pacing, structure, slide density, and what reviewers tend to accept, far faster than reading guidance.

Topic Ideas That Work Well

After Submitting

Most BSides events notify speakers 2-6 weeks before the conference. If you don't hear back, it's fine to follow up once. If you're not selected, submit the same talk to another BSides — different review committees have different preferences.

Keep an eye on this page for newly opened CFPs, and check the main event list for upcoming events that haven't opened their CFP yet.