Call for Speakers

Call for Speakers is closed. Submissions are no longer possible. Sorry.
in 25 hours

null Dallas

planned future dates

22 Oct 2026, 30 Nov 2026, 19 Dec 2026

location

Dallas, Texas, United States


The null Dallas Chapter aims to create a space where communities can learn from one another, collaborate, and build something together.

finished 4 days ago
Call for Speakers
Call opens at 12:00 AM

16 Oct 2026

Call closes at 12:00 PM

16 Oct 2026

Call closes in Central Daylight Time (UTC-05:00) timezone.
Closing time in your timezone () is .

The next security thing starts here!

We are looking for speakers who can share real-world security knowledge, technical research, lessons learned, tools, experiments, failures, and ideas that move the community forward.

Whether you are an experienced security researcher, a practitioner working on interesting problems, a student with a cool project, or someone who has learned something the hard way, we want to hear from you.

🎯 Session Formats

We are open to different formats:

  • Lightning Talk: 10–15 minutes
  • Technical Talk: 30–45 minutes
  • Deep Dive: 45–60 minutes
  • Hands-on Workshop: 1–3 hours
  • Panel / Roundtable: 45–60 minutes
  • Live Demo / Research Showcase


Additionally, below are some useful resources by experts on writing submissions for CFPs:

1. This Blog post by Cheryl Biswas about giving a talk in Infosec (https://cyber-watch.ca/learning/giving-a-talk-in-infosec/)

2. The CFPs 101 Panel from BSidesLV 2016 (https://m.youtube.com/watch?v=k0prs_m7FrE)

3. The DEFCON Speaker’s Corner post by Nikita titled How do I Make my CFP Stand Out? (https://www.defcon.org/html/links/dc-speakerscorner.html#nikita-cfp)


Note: Sessions involving vulnerabilities, exploits, malware, offensive techniques, or real-world incidents must be presented responsibly.

Speakers should:

  • Avoid exposing sensitive, confidential, or personally identifiable information.
  • Clearly distinguish controlled demonstrations from real-world exploitation.
  • Avoid sharing credentials, secrets, access tokens, or other sensitive material.
  • Clearly identify fictional, simulated, or sanitized examples.