Tips for Submission

It doesn't matter whether you are an independent consultant, a security professional at a small company, a blogger, an expert security tester at a large software company with a story to tell, or a senior developer at a company that is not exhibiting at RSA Conference 2016 Abu Dhabi – you are all reviewed equally! That doesn’t mean you won’t be in serious competition. The Conference is vendor-independent. Sponsor and exhibitor submissions are reviewed with the same criteria by our Program Committee judges who are selected based on their industry knowledge and experience. Our judges are technical like you and love reading submissions that come directly from you.

Marketing and agency personnel – please work closely with your speakers in order to provide the technical depth required to get our Program Committee judges excited! We welcome your submissions but you have a challenge when it comes to many parts of the submission without the help of your speakers!

Below are some tips that have helped previous speakers get selected to speak at RSA Conference Abu Dhabi.

1.  Select Your Topic Carefully. This can be the most challenging aspect of the entire process. You need to consider:

• The scope of your personal expertise and those of any co-speakers. You should be very well versed in the topic to be addressed and equally skilled at presenting. Provide evidence that the speaker is an expert in the topic proposed. Ask yourself, “Am I (and any other speakers) considered an expert on this topic by my organization and professional peers?” Having personally experienced an implementation or war story in your enterprise automatically positions you as that expert.

• Timeliness of the topic. Is this a topic of current importance to Conference attendees in this region? Is it one their organizations and/or clients are struggling to get their arms around?

• Technical level of the topic. The average RSA Conference attendee has nine or more years’ experience in the security industry. Attendees are looking for highly technical and high level strategic information and demonstrations. Review the session classifications and topic choices carefully, and based on the topic, consider creating a proposal that is technical in nature, including technology demos, architectural discussions, and code-level examples and explanations.

• Educational value of the topic. Conference attendees respond very positively to detailed case studies and real implementation stories that they can use when they return to their jobs. They want to leave the Conference equipped with “lessons learned,” especially as they relate to new technologies or approaches to security management. Be extremely objective in considering whether the Program Committee might believe that your session is about marketing or selling your company’s products or services. A case study (problem statement, approach, lessons learned, outcomes, post mortem) is very different from a customer reference story.

2.  Develop a Unique Approach to the Topic. Recognize that your professional peers may be submitting their proposals on a similar topic. Evaluate how to make your proposed topic stand out from the crowd.

3. Consider Every Aspect of Your Submission. Each item on the online form is important to your potential selection and your proposed presentation. Many of these items are character-restricted and the character count includes spaces. Therefore, save time by ensuring that each item is within the correct character count before going online. Using our offline form is a good way to manage the character counts.

• Topic Selection - the wide range of topics to choose from will be mapped to tracks once the Call for Speakers is closed. Find a topic where you can identify an interested audience and provide a deep dive into the subject matter. Keep the regional interests of our attendees in mind as you develop your proposal.

•  Session Title (limit 75 characters including spaces) - should clearly indicate your topic and attract potential attendees. Remember your competing against other sessions at the same time! Creative titles do attract attention from the Program Committee and the Conference attendees – but not if the session abstract and detail don’t deliver.

• Session Abstract (limit 400 characters including spaces) - this will be included on our website and in our Program Guide helping Conference attendees choose which sessions to attend.

• Quick Abstract  (limit 200 characters including spaces) - this shorter abstract will be used for pocket guides, mobile apps, etc.

• Session Detail (Limit 2,500 characters including spaces) - should describe the architecture of your session. What are the main points you plan to cover (note: bullets are not supported)? Describe the presentation flow. This section is very important for the Program Committee to understand and evaluate your submission. Please note: The information provided in the Session Detail section is very important in the review process so please be detailed. The information provided for the Session Detail section will not be published.

• Session Classification. You have the choice of Advanced, Intermediate and General Interest. Given the experience of our attendees, technical sessions should be an intermediate level at minimum. Unless it is a new technology or concept, attendees are experienced in the basics of most security subjects and are interested in taking it to the next level.

• Security Tags (up to five keywords) - will be used for attendee searches.

• Session Length - select 50-minute session.

The best approach is to download the offline form.

This document was retrieved from on Tue, 16 Jul 2019 08:28:23 -0400.