Call for Papers – 2015:

The Call for Papers is now closed!

Focus areas this year are:
Attack:
From 0-days to strange, unpatched variations of the #ShellShock or #Heartbleed vectors or absolutely anything in between. You wear the black (or grey) hat and we are interested in any and all attack vectors you are willing to chat about. We can arrange a conference call with the EFF (no, not that one) in advanced if you feel it’s necessary but please do come and scare us silly and bring us those sexy attack talks.
Defend:
All your bases are exposed: from IoT to storage of our phone’s photos (yes, even the “private” ones) everything is all online now. If you are wearing a white hat and in the business of saving the bacon of a company (no names required) or simply are one of those that “does it right” feel free to share your paralyzing fears with us, as well as any tips you might have that would either:
  1. make your job easier, or
  2. make the lives of those concerned with these things themselves more sane – especially if you just passed on your fears!
Develop:
The first part of DevOps and the place it all (should / can??) be made right. Cape Town has a very active community of developer types and as this IS where the security mistakes can be avoided we would like to hear from developers themselves on the topics they are working on. Whether it’s how awesome <insert-your-language-here> (Node.js or IO.js perhaps?) is; or on security considerations for microservices (you are all on that bandwagon, right?) please do come and talk to your peers – and get their feedback on these things.
Operate:
The second half of DevOps and where stuff starts to fall apart (or at least where people notice it). If you are maintaining an environment or designing one, this is the area you should most be concerned with. Whether your thoughts are along the lines of the DARPA Cyber Grand Challenge or on securing lightweight virtualised systems running all those microservices the dev-types are building, we want your thoughts on how to maintain the systems we all rely on.
If your talk does not fit one of those four broad themes, don’t worry. We will look at all talks coming in and if the idea appeals to us we’ll find you a spot on the program. If you are not talking at BSides CapeTown this year it had better be because you are bringing someone that is.

Papers can be either formal or informal but the presentations are generally less than formal – speak to your research, talk about it with us, don’t merely read it to us 🙂


Talks can be submitted in one of three formats:

Speed talks of 15mins or so that focus on a very specific aspect of a topic, think: “inch-wide, mile-deep”. In total you will speak for about 15mins but be given at least that amount of time for audience questions. (30min total)
Overview talks of about 30min that take on a topic as a whole, but plan to provide a mile-wide; inch-deep level of detail. These are generally very high-level and will usually (if they strike interest) result in conversations with others outside of the main speaking room. We will give you about 15mins to handle questions so view these talks / papers as a way to kickstart a conversation in the community. (45mins total)
Deep dive talks where you plan to talk about your topic for about an hour and take another 30 mins (or so) of questions. These are the big brother of the speed talks and will tend to focus on the details of your research. While these are the types of talks that most of us come to BSides for they do tend to be quite intense and we will only accept a few in this category, so if your paper catches our eye but doesn’t make the cut we may ask you to consider reformulating your paper as option 1 or 2 above. (90mins total)

Remember that the majority of the BSides Cape Town audience are developer types when you make your submissions, as those talks that most appeal to developers are more likely to make the cut. Code is welcome.