Submission Checklist

If you are submitting multiple talks, please submit them separately.

Put yourself in the shoes of the HackBama’s Review Board. You would want to read well thought-out, complete, submissions without having to load special document viewers or visit external web sites. You would want to read the entire submission without having to lookup acronyms or research prior works. You would have hundreds of submissions to evaluate and so the most complete ones would stand out to you.

With that in mind, your submission must contain all the following information.

• Presenter Information
• Presentation Information
• Abstract
• Speaker Bio(s)
• Outline
• Scheduling Information
• Equipment requirements
• Supporting Files

Please be as detailed as possible so that our review board can best evaluate your presentation against other submissions.


• Submissions with incomplete application forms.
• Submissions without an abstract, detailed outline, or bio.
• Submissions that have sent in only attached slides, papers, or point to a URL.
• Submissions that have withheld details, or have knowingly falsified details.

Please cut and paste your submission into the body of an email or within a .txt file. We request that applications are in plain text only to avoid disfiguring formatting errors. Please do not submit your application in .pdf, .docx, .odf, mdf, or any other formats, else it may delay your review. Submit in one text file only, do not submit each section individually. Do not add decorative section breaks or ascii tomfoolery to the application.


Primary Speaker Name or Pseudonym*:

*No real name is necessary for submission; however, if you are selected we will need your real name in order to register you and to complete your speaking honorarium payment. If disclosing your identity is problematic, please let us know. We can plan for alternative means of authentication.

Primary Speaker Title and Company (if applicable):

Additional Speaker Name(s)* and Titles:

Primary Speaker Email Address:

Backup Email, in case of communication failure:

Primary Speaker Phone Number:

Co-Speaker (s) Email Addresses:

Co-Speaker (s) Phone Numbers:

HackBama promotes you as a speaker in several ways. We build a Twitter list of all accepted speakers, we tweet about you, share your posts, etc. We include your social media information on the web site within your bio, so people can contact or “follow” you. Please list all the links that you’d like us to share. (Twitter, Facebook, website, etc):


I would like my submission sent in *anonymously to the review board. The human CFP processor will manually remove the presenter information and bio(s) for the listed presenter(s): Yes or No

*I have removed PII from any attached slides, white papers, or materials.

I acknowledge I’m responsible for the metadata in my content.


Date of Submission:

Presentation Title:

Is there a demonstration? Yes or No

Is there audience participation? Yes or No
If yes, how?

Are you releasing a new tool? Yes or No
If yes, under which license?

Are you releasing a new exploit? Yes or No

Are there any contingencies that might prevent releasing the exploit (e.g. vendor relationships)? Yes or No

If you are releasing vulnerabilities, clearly break them down and abstract as a vulnerability database would. Include the vendor(s), product(s), and version(s) affected.

Length of presentation?(20 minutes, 45 minutes, 105 minutes)

Are you currently submitting this topic to any other conferences held prior to HackBama? If yes, please list where.


Your abstract will be used for the website and printed materials. Summarize what your presentation will cover.

Attendees will read this to get an idea of what they should know before your presentation, and what they will learn afterwards. Use this to describe how technical your talk is, what tools will be used, what materials to read in advance to get the most out of your presentation.

This abstract is the primary way people will be drawn to your session, but should not give them the entire content of the talk. We request you keep your abstract to at least over 140 characters, but at or under the 1337 maximum.

Speaker Bio(s):

This text will be used for the website and printed materials and should be written in the third person. Cover any professional or hacker history that is relevant to you and the presentation, you may include past jobs, tools that you have written, etc. Let people know who you are and why you are qualified to speak on your topic. If you prefer, you may write your bio under a pseudonym.

Detailed Outline:

This is the most important section on the application. You must provide a detailed outline containing the main points and navigation through your talk.  Show how you intend to begin, where you intend to lead the audience and how you plan to get there. Your outline should be in simple text. Please do not submit slides, Docs, or PDFs as an outline.

If you are submitting a panel, it’s encouraged to list the contributions of each panel member on the outline, as well as the estimated time budgeted for the bullet point on the outline.

The review board needs submissions that include references to prior works and research you used in developing your presentation. The more detailed your outline, the better we will be able to review your presentation compared to other submissions, and the higher chance you will have of being accepted.

Scheduling & Equipment Needs

Is there a specific day or time by which you must present?*

* We work to accommodate special speaking time-slots, but cannot guarantee any specific availability. We have dozens of presentations to arrange so we ask that you be available for speaking at any time during the conference. If you have special circumstances limiting when you can speak, please let us know ASAP otherwise we may not be able to accept your submission.

Equipment needs & special requests

Will you require more than 1 LCD projector feed? Yes or No
If yes, please specify how many and why.

Are there any other special equipment needs that you will require?

Supporting File(s):

Additional supporting materials such as code, white papers, proof of concept, etc. should be sent along with this email to talks(at}hackbama[dot)com. Note that additional files that may help in the selection process should be included. We are not asking for a complete presentation for this initial submission – That will only be required if you are selected for presenting.

If you are speaking or submitting anonymously you are responsible for removing metadata and PII from materials that may reveal your identity.


Please read and accept these terms by inserting your name where noted. Failure to do so will render your submission incomplete. Please read these carefully as some of the terms have changed.

Grant of Copyright Use

I warrant that the above work has not been previously published elsewhere, or if it has, that I have obtained permission for its publication by HackBama. and that I will promptly supply HackBama with wording for crediting the original publication and copyright owner. If I am selected for presentation, I hereby give HackBama permission to duplicate, record and redistribute this presentation, which includes, but is not limited to, the conference proceedings, conference CD, video, audio, and hand-outs to the conference attendees for educational, on-line, and all other purposes.


I, (insert primary speaker name) understand that HackBama’s official Press Liaison & Staff may contact me. I consent to be contacted in order to arrange interviews with the media. My contact information will not be given to third parties without my consent. No, I (insert primary speaker name), don’t want to be contacted by HackBama’s press staff for any reason.
If you have not received confirmation of your submission after two business days of submission, contact us again at talks[at]hackbama[dot]com.

TIPS: Please check your spam folder, whitelist, and search for mail from [at]gregtampa[dot]com.

Good luck!


Credit for the above CFP Submission outline goes to defcon(dot)org greatest cybersec conference on the planet!