RSA® CHARGE 2015
Call for Speakers Offline Submission Form
This form is to be used ONLY as a rough draft of submission; ALL final
submissions must be done using ONLINE form which can be found at
charge.rsa.com
SUBMITTER INFORMATION:
The information you provide in this section pertains to you as the Submitter. If
you’re also the Speaker, your account information can be carried forward in the
Speaker Information section.
Please fill out the following information
*= required input

Salutation * Dr./Mr./Mrs./Miss/Ms.

First name *

Middle Initial

Last Name *

Suffix

Company *

Job Title *

Address 1*

Address 2

City*

Country*
o If Country is USA or Canada
 State/Province*
 Zip/Postal Code*
o If Country is United Kingdom
 UK Country*
 UK County*
 Foreign Postal Code*
o If Country is NOT USA, Canada or United Kingdom
 Foreign State
 Foreign Postal Code

Primary email address *

Secondary email address

Primary Telephone *

Mobile Telephone
PAGE 1 of 6
SESSION INFORMATION
All sessions are 45 minutes long, including Q&A. Presentations should target providing
information/insight that attendees can apply to their jobs (e.g. best practices/lessons
learned). Vendor product/solution sales oriented presentations will not be accepted. Please
note that RSA Partner presentations (excluding Sponsor presentations) need to include an
RSA Customer who will co-present and share their experience and lessons learned.
* = required input
Are you the proposed speaker or panel moderator?* Yes /No
If you are not the proposed speaker:
We require each proposed participant to approve their participation in the submission.
Notifications will go out to all speakers, moderators and panelists and submissions will
be disqualified if any participants have not approved their participation in the session.

Session Title * (Limit 75 characters including spaces)
Your session title should clearly indicate the topic of your presentation, and do so in a
way that attracts potential attendees for your presentation. Your title should attract the
interest of the Program Committee – and subsequently your audience.
Enter Session Title Here

Short Session Abstract * (Limit 400 characters including spaces)
In a few sentences, explain what your session will cover (please do not use bullets in
your submission). This abstract will be included in our marketing materials, website
and program guide. NOTE: How long is 400 characters? This paragraph is 274
characters including spaces.
If you are an RSA Customer and would like to lead or participate on a panel
discussion, please include an overview of your use case, your area of focus, expertise
and RSA products used to the Program Committee can determine common theme(s)
with other submitters when building Panel Discussion sessions. You will have an
opportunity, in the Add a Speaker section, to identify your participation desires.
Enter Short Abstract Here

Quick Abstract * (Limit 140 characters including spaces)
Sell it in a Tweet!
Enter Quick Abstract Here
PAGE 2 of 6
Session Format * (select one)
Individual Speaker - One speaker only
Co-Speakers - This format has two speakers, one is designated as Primary
Speaker and the other as Secondary Speaker. The Primary Speaker is the main
contact for the RSA Charge Speaker Manager.
Panel Discussion - This is a session with a Moderator (Panel Leader) and up to
three Panelists. The Moderator is responsible for facilitating the panel discussion and
is the main contact for the RSA Charge Speaker Manager. Panel Discussions are not
presentations.
Session Profiling Information – The following information will help ensure your session is
targeted to the right audience. Sessions will be targeted on specific topics and levels of
experience.
Target Audience *
Foundation – Getting started with solutions, learning the basics, gaining confidence
Advanced – Creative use of solutions; unique, advanced challenges and innovative
solutions
Session Topics for RSA Charge * Please choose one of the following:
Threat Readiness & Incident Response – Secrets of the SOC (General)
Sessions should focus on experiences and best practices for building, operating and
improving Security Operations Centers and their associated people, processes, and
technology. Examples include how to create and evolve, developing a risk or breach
management program, justifying and measuring Security Operations performance and
lessons learned from building and maturing your SOC or CIRC as well as war stories
related to incident response engagements. The sessions should include an explanation of
the business problem, desired outcomes, solution results, key takeaways, and future
plans and lessons for the audience.
Threat Readiness & Incident Response – Attack Detection and
Investigation (Technical)
Sessions should focus on approaches for leveraging RSA Security Analytics, RSA ECAT
and/or RSA Security Operations Management/RSA Archer to detect, investigate and
respond to threats. Examples include incident detection war stories, examples of
“hunting” through data, investigating alerts, incident management, developing and using
threat intelligence, product tips and tricks, deployment and integrations case studies,
etc. The sessions should include an explanation of the business problem, but will focus
on the technical challenge, desired outcomes, solution result and key takeaway lessons
for the audience.
PAGE 3 of 6
Anti-Fraud (General)
Sessions should focus on how to leverage the anti-fraud portfolio to solve specific
business problems such as gaining visibility into cybercrime underground tactics, best
practices for collecting, sharing and leveraging intelligence, transaction protection and
fraud mitigation techniques for login and post login activities. Content should include
best practices, case studies or war stories. The sessions should include an explanation of
the business problem, desired outcomes, required functionality, solution outcomes,
metrics used to measure success and key takeaway lessons for the audience.
Anti-Fraud (Technical)
Sessions should focus on technical implementations and uses of Adaptive Authentication
(e.g. website and mobile SDK integration, optimizing risk engine, policy and case
management), Web Threat Detection (e.g. leveraging click stream analysis to detect
advanced info security incidents, fraud, threat and profile analysis, and WTD reporting)
or technical deep dive into cybercrime underground tactics, techniques and procedure
(e.g. examples of actual underground forums, intelligence gathering and sharing
standards, Trojan reverse engineering examples) The content must include
demonstrations of a business problem that is addressed using RSA Web Threat
Detection, Adaptive Authentication, Adaptive Authentication for eCommerce or
FraudAction. Screen shots, recorded or interactive demonstrations are required. This is a
“How To” presentation to instruct the audience on optimal platform usage.
Secure Access (General)
Sessions should focus on how you have used RSA Authentication solutions to solve a
critical business problem, enable a business process or reduce risk. Content should
include best practices, case studies or war stories. Examples include how to successfully
rollout authentication requirements to end users, leverage authentication across multiple
applications, enable new business activities by providing secure access etc. The
presentation should include an explanation of the business problem, desired outcomes,
required functionality, solution outcomes and metrics used to measure success.
Secure Access (Technical)
Sessions should cover technical uses of authentication including application integration,
mobile & cloud authentication, product deployment, authenticator provisioning, product
migration, reporting, administration etc. The content must include demonstrations of a
business problem that is addressed using the RSA Authentication Manager or Adaptive
Authentication solutions. Screen shots, recorded/interactive demonstrations or
workshops are required.
Identity and Access Management (General)
Sessions should focus on how you have used RSA’s solution — Identity Management and
Governance (Aveksa) — to improve compliance, reduce risk, improve the efficiency and
cost of identity lifecycle management, or accelerate business access. Content should
focus on case studies, best practices or overcoming a significant obstacle. Examples
include how to successfully engage the line of business, roll out access request and
approval, tackle role management, or automate provisioning. The presentation should
include an explanation of the business problem, desired outcomes, required
functionality, solution outcomes and metrics used to measure success.
PAGE 4 of 6
Identity and Access Management (Technical)
Sessions should cover technical uses of RSA’s solution — Identity Management and
Governance (Aveksa) — including access certification, policy management, role
management, access request, or provisioning. The content should include use cases or
demonstrations of a business or technical problem that was addressed using the RSA
platform. Screen shots, recorded/interactive demonstrations or workshops are
required. Interesting or technically challenging use cases are definitely a plus!
Submitters Comments (limit 400 characters including spaces)
Is there anything you want to tell the Program Committee?
Enter your comments here
PROPOSED SPEAKERS
Add a Speaker
1. The number of participants that can be added to this session is based on the Session
Format selected in the prior Session Information section. An Individual Speaker
session may have only one speaker, a Co-Speakers session has two speakers and a
Panel Discussion session requires a Moderator (Panel Leader) and up to four Panelists.
Speaker roles for Panel Discussion sessions:
 Moderator (Panel Leader) - The Moderator (Panel Leader) will lead in the
development and planning of a panel, is responsible for facilitating the panel
discussion and is the main contact for the RSA Charge Speaker Manager.
 Panelist – The panelists should have differing areas of focus and expertise around
a common theme to ensure interactive debate.
All proposed Speakers, Moderators (Panel Leaders) and Panelists will be notified that
they were included in a proposed submission. If a Speaker, Moderator (Panel
Leader) or Panelists has not approved their participation in a proposed
submission, the proposed submission will be disqualified.
Complete the following information for each participant you wish to add. You will be given
the option to populate the form with your information, if you are a participant in addition to
being the submitter.
NOTE: Each speaker must have a unique email address
* = required input:

Salutation * Dr./Mr./Mrs./Miss/Ms.

First name *

Middle Initial

Last Name *

Suffix

Preferred Name

Company *
PAGE 5 of 6

Job Title *

Address 1*

Address 2

Country*
o If Country is USA or Canada
 State/Province*
 Zip/Postal Code*
o If Country is United Kingdom
 UK Country*
 UK County*
 Foreign Postal Code*
o If Country is NOT USA, Canada or United Kingdom
 Foreign State
 Foreign Postal Code

Primary Email address *
(must be unique)

Primary Telephone *

Secondary email address

Primary Telephone *

Mobile Telephone

Linkedin

Participant Biography/CV * (Limit 400 characters including spaces)
This information will appear on the website and in other marketing materials. Please
do not use bullets.
Enter speaker biography/CV here

Has the participant spoken at an RSA Summit before?
Yes/No
RSA Global Summit 2014
RSA Archer Summit 2014
Security Analytics Summit 2013
RSA Archer Summit 2013
NetWitness Summit 2012
RSA Archer Summit 2012
Other
Enter other conference name(s) here

If participant has a blog, please enter blog link here:
Enter blog link here

If participant has a Twitter handle, enter it here (format @Handle):
Enter Twitter handle here
PAGE 6 of 6