This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org

Difference between revisions of "2015 BASC Homepage"

From OWASP
Jump to: navigation, search
m
 
(2 intermediate revisions by the same user not shown)
Line 9: Line 9:
 
The BASC will be a free, one day, informal conference, aimed at increasing awareness and knowledge of application security in the greater Boston area. While many of the presentations will cover state-of-the-art application security concepts, the BASC is intended to appeal to a wide-array of attendees. Application security professionals, professional software developers, software quality engineers, computer science students, and security software vendors should be able to come to the BASC, learn, and hopefully enjoy themselves at the same time.
 
The BASC will be a free, one day, informal conference, aimed at increasing awareness and knowledge of application security in the greater Boston area. While many of the presentations will cover state-of-the-art application security concepts, the BASC is intended to appeal to a wide-array of attendees. Application security professionals, professional software developers, software quality engineers, computer science students, and security software vendors should be able to come to the BASC, learn, and hopefully enjoy themselves at the same time.
  
 +
<!--
 
== Call for Papers ==
 
== Call for Papers ==
 
The [[BASC_2015_Call_For_Papers|Call For Papers]] is still open but will close soon!
 
The [[BASC_2015_Call_For_Papers|Call For Papers]] is still open but will close soon!
  
 
+
-->
<!--  
 
  
 
{{2015 BASC:Section Template | Keynote}}
 
{{2015 BASC:Section Template | Keynote}}
  
[[File:DrJared.jpg|left]] '''AppSec: How It Fits into Digital Security'''
+
'''"How I Teach Security"'''
  
Securing code is important. But history has shown us that we can never be certain that our code is 100% perfect. This becomes particularly true in rapidly evolving environments. As an industry we need to take a broader look. What security features are provided by the hardware, OS, language, compiler, and even application type? Join us bright and early as Dr. DeMott kicks off the 2015 Boston Application Security Conference with a Keynote you won’t forget.
+
Rob Cheyne, CEO, Big Brain Security, Executive Director, SOURCE Conference
  
Dr. Jared DeMott is a seasoned security researcher, and has spoken at conferences such as DerbyCon, BlackHat, Defcon, ToorCon, Shakacon, DakotaCon, CarolinaCon, ThotCon, GRRCon, and Bsides*. Past notable research relates to stopping a trendy hacker exploit technique (known as ROP), by placing as a finalist in Microsoft’s BlueHat prize contest, and by more recently showing how to bypass Microsoft’s EMET protection tool.
+
[[File:RobCheyne.jpg|left]]After spending over 10 years as a builder of software systems, and the next five years on the breaking side of things, I then spent over a decade teaching information security concepts to over 25,000 people around the world at leading global organizations.
 
+
Jared is active in the security community by teaching his
+
Over the course of this work, I’ve noticed some interesting patterns across my body of students and clients.
Application Security course, and has co-authored the book –
+
Fuzzing for Software Security Testing and Quality Assurance.  
+
In most organizations, I have seen have at least one critical area of the business where basic information security best practices were not implemented where they should be. In many cases, this is because people are either not factoring in an accurate representation of infosec risks into their planning & project life cycles, or they willfully ignore them.
DeMott has been on three winning Defcon CTF teams, and has the  
+
black badges to prove it. He has been an invited lecturer at
+
The reason for this often boils down to one thing: the overall level of security awareness in most places is pretty low, even amongst developers, and even in organizations where you would think it should be a lot higher. Amongst business and management groups, it can be practically non-existent because security is still often assumed to be the purview of the security group, the infrastructure team, or the developers.
prestigious institutions such as the United States Military
+
Academy, and previously worked for the National Security Agency.
+
In such an environment, business requirements often take precedence over security requirements, even when the security requirements are truly protecting the best interests of the business.
DeMott holds a PhD from Michigan State University.<br clear=all>
+
 
+
I have seen that many people within a typical organization:
-->
+
* have little to no understanding of the actual risks they face.
 +
* have no idea how to balance rational security options against business requirements to mitigate those risks.
 +
* think that security is somebody else’s job, and ignore it accordingly.
 +
* believe that internal systems are somehow safe from attack
 +
* think that the data breach will never happen to them
 +
 +
I have come to believe strongly that this is as much as much our failure to communicate and influence information security initiatives as it is the business' failure to understand. Given the shortage of infosec professionals in the marketplace, I believe the only way we can scale ourselves is to communicate what we know more effectively.
 +
 +
In short, we need to learn how to communicate what we know much, much better than we are doing today.
 +
 +
Security is arguably much more of a people problem than a technology problem, and the ability to communicate rational security wisdom to people outside of the “InfoSec echo chamber” is a highly underrated skill. There are many areas of security where we have solid best practices, but they aren’t followed because the people who need to hear the message the most simply never receive it.  
 +
 +
Please join me in this frank & interactive discussion of what it means to communicate information security outside of our echo chamber, and discuss some specific strategies for doing so.  
  
 
{{2015 BASC:Section Template | The Details}}
 
{{2015 BASC:Section Template | The Details}}
Line 41: Line 53:
 
* [[2015_BASC_Speakers | Speakers]]
 
* [[2015_BASC_Speakers | Speakers]]
 
* [[2015_BASC_Presentations | Presentations]]
 
* [[2015_BASC_Presentations | Presentations]]
 +
* [[2015 BASC InfoSec Communication Workshop|InfoSec Communication Workshop]]
 
* LinkedIn [https://www.linkedin.com/groups/Boston-Application-Security-Conference-BASC-4631647 Group]
 
* LinkedIn [https://www.linkedin.com/groups/Boston-Application-Security-Conference-BASC-4631647 Group]
 
* Twitter: Follow [http://twitter.com/#!/BASConf @BASConf] HashTag: #basc2015
 
* Twitter: Follow [http://twitter.com/#!/BASConf @BASConf] HashTag: #basc2015

Latest revision as of 23:31, 30 September 2015

Boston-Banner-468x60.gif 2015 BASC: Home | Agenda | Presentations | Speakers

Platinum Sponsors

Rapid7

Silver Sponsors

bugcrowd


Sponsorships are available: See Sponsorship Kit
Please help us keep BASC free by viewing and visiting all of our sponsors.


Welcome

This is the homepage for the 2015 Boston Application Security Conference (BASC). This free conference will take place on Saturday, October 3rd at Microsoft New England Research and Development Center (NERD). Note the location is different from last year.

The BASC will be a free, one day, informal conference, aimed at increasing awareness and knowledge of application security in the greater Boston area. While many of the presentations will cover state-of-the-art application security concepts, the BASC is intended to appeal to a wide-array of attendees. Application security professionals, professional software developers, software quality engineers, computer science students, and security software vendors should be able to come to the BASC, learn, and hopefully enjoy themselves at the same time.


Keynote

"How I Teach Security"

Rob Cheyne, CEO, Big Brain Security, Executive Director, SOURCE Conference

RobCheyne.jpg
After spending over 10 years as a builder of software systems, and the next five years on the breaking side of things, I then spent over a decade teaching information security concepts to over 25,000 people around the world at leading global organizations.

Over the course of this work, I’ve noticed some interesting patterns across my body of students and clients.

In most organizations, I have seen have at least one critical area of the business where basic information security best practices were not implemented where they should be. In many cases, this is because people are either not factoring in an accurate representation of infosec risks into their planning & project life cycles, or they willfully ignore them.

The reason for this often boils down to one thing: the overall level of security awareness in most places is pretty low, even amongst developers, and even in organizations where you would think it should be a lot higher. Amongst business and management groups, it can be practically non-existent because security is still often assumed to be the purview of the security group, the infrastructure team, or the developers.

In such an environment, business requirements often take precedence over security requirements, even when the security requirements are truly protecting the best interests of the business.

I have seen that many people within a typical organization:

  • have little to no understanding of the actual risks they face.
  • have no idea how to balance rational security options against business requirements to mitigate those risks.
  • think that security is somebody else’s job, and ignore it accordingly.
  • believe that internal systems are somehow safe from attack
  • think that the data breach will never happen to them

I have come to believe strongly that this is as much as much our failure to communicate and influence information security initiatives as it is the business' failure to understand. Given the shortage of infosec professionals in the marketplace, I believe the only way we can scale ourselves is to communicate what we know more effectively.

In short, we need to learn how to communicate what we know much, much better than we are doing today.

Security is arguably much more of a people problem than a technology problem, and the ability to communicate rational security wisdom to people outside of the “InfoSec echo chamber” is a highly underrated skill. There are many areas of security where we have solid best practices, but they aren’t followed because the people who need to hear the message the most simply never receive it.

Please join me in this frank & interactive discussion of what it means to communicate information security outside of our echo chamber, and discuss some specific strategies for doing so.

The Details

Registration

Admission to the BASC is free but registration is required for breakfast, lunch, and the evening social time. We will do everything possible to accommodate late registrants but the facility and food are limited. Online registration is now open and you are encouraged to register early.

You can find out more about this conference at the 2015 BASC Homepage
Conference Organizer: Jim Weiler