Difference between revisions of "Salt Lake City"

From OWASP
Jump to: navigation, search
(→‎The next meeting is scheduled for Thursday January 5th, 2017 in conjunction with UtahSec)
Line 1: Line 1:
−
== ''The next meeting is scheduled for Thursday January 5th, 2017 in conjunction with [http://www.utahsec.org UtahSec]'' ==
+
== ''The next meeting is scheduled for Thursday May 4th, 2017 in conjunction with [http://www.utahsec.org UtahSec]'' ==
  
  
 
'''''Date:'''''
 
'''''Date:'''''
  
−
''' Thursday January 5th, 2017'''
+
''' Thursday May 4th, 2017'''
  
  
Line 14: Line 14:
 
'''''Meeting location:'''''
 
'''''Meeting location:'''''
  
−
'''LDS Riverton Office Building'''
+
'''801 Labs'''
  
−
'''3740 W 13400 S'''
+
'''353 East 200 South Suite #B'''
  
−
'''Riverton, UT 84065'''
+
'''Salt Lake City, UT 84111'''
  
−
'''(Inform security guard at the front desk that you are attending OWASP)'''
 
  
  
 
'''''Presentations:'''''
 
'''''Presentations:'''''
  
−
'''''"ISACA is presenting first.'''''"
+
'''''"Jon Jarvis from SecureUtah.org will be presenting on data privacy and surveillance capitalism.'''''"
  
−
'''''"Followed by OWASP: How to integrate security into Agile SDLC using OWASP Application Security Verification Standard and how data is exfiltrated out of your web applications "'''''
+
'''''"Presenter from 801 Labs"'''''
−
 
 
−
'''By Dmitry Dessiatnikov of Security Aim'''
 
−
 
 
−
'''''Agenda: '''''
 
−
 
 
−
OWASP Top 10 awareness document debuted in 2003, but it only covers top 10 risks, what about #11? Now in 2017 meet OWASP Application Security Verification Standard (ASVS) v.3.0.1.
 
−
 
 
−
This is an introductory presentation about what OWASP ASVS is and how to use it to integrate security into the aspects of Agile software development process. Such activities as definition of security-focused user stories, both functional and non-functional requirements will be discussed. The presentation will cover how to inject security and privacy considerations into the early phases of the Agile software development process to address the risks of security bugs pushed to production during frequent releases.
 
−
 
 
−
As a bonus we will discuss a Same Origin Policy bypass that allows data exfultration that most applications are not protected from.
 
  
 
''Everyone is welcome to join us at our chapter meetings'''
 
''Everyone is welcome to join us at our chapter meetings'''
Line 49: Line 38:
 
<!-- maybe need this link https://www.owasp.org/index.php/File:UtahSec-Software_Assurance_Maturity_Model.pptx  
 
<!-- maybe need this link https://www.owasp.org/index.php/File:UtahSec-Software_Assurance_Maturity_Model.pptx  
 
!-->
 
!-->
−
 
 
[[Category:Utah]]
 
[[Category:Utah]]

Revision as of 02:51, 3 May 2017

The next meeting is scheduled for Thursday May 4th, 2017 in conjunction with UtahSec

Date:

Thursday May 4th, 2017


Time:

6 - 8 pm


Meeting location:

801 Labs

353 East 200 South Suite #B

Salt Lake City, UT 84111


Presentations:

"Jon Jarvis from SecureUtah.org will be presenting on data privacy and surveillance capitalism."

"Presenter from 801 Labs"

Everyone is welcome to join us at our chapter meetings'

Past Meetings

OpenSAMM Project - Alan Jex - 3 Jan 2013

Alan discussed the Open Security Assurance Maturity Model (OpenSAMM) including his success at leveraging it to do a successful crawl/walk/run expansion of AppSec at his day job. HP hosted and served food (thanks!). Slides are available by clicking here.

Retrieved from "https://wiki.owasp.org/index.php?title=Salt_Lake_City&oldid=229353"