DASTProxy: Donโ€™t let your automated security testing program stall on crawlInstead focus on business context

By Kiran Shirali , Srinivasa Rao Chirathanagandla on 25 Jan 2017 @ Owasp App Sec California
๐Ÿ“Š Presentation ๐Ÿ“น Video ๐Ÿ”— Link
dynamic-analysis dast devsecops secure-development web-security automation-framework
Focus Areas: Application Security , DevSecOps , Malware Analysis , Web Application Security

Presentation Material

Abstract

Many automated security programs look at crawling through a website before testing as a measure to build security automation. However, such an approach has limited success when you are dealing with huge applications that have numerous teams working on modular components or subsections. At eBay, it was instantly clear that such an approach was doomed to fail. Instead the Secure Development Life Cycle Team leveraged the knowledge and business context that our product development teams had built into functional testing, to enhance our dynamic security testing automation. This let us further our goal to make security a responsibility of every product development team at eBay. This talk is about our journey and the open sourced automation framework (https://github.com/eBay/DASTProxy) that we built to make our dreams and goals a reality.