We use a few cookies

Essential cookies keep the library working. With your permission, we'd also like to use analytics to see what's useful and improve the experience. Read our Privacy Policy or Cookie Policy.

Skip to main content
Home/e-Resources/Software Engineering/Scaling Security Assessment at the Speed of DevOps - AppSecUSA 2016
Educational VideosSoftware Engineering

Scaling Security Assessment at the Speed of DevOps - AppSecUSA 2016

Checking your access to this record.

Abstract & Overview

Recorded at AppSecUSA 2016 in Washington, DC https://2016.appsecusa.org/ Scaling Security Assessment at the Speed of DevOps Recent software development trends, namely DevOps, Continuous Integration, Continuous Delivery, and Continuous Deployment, have empowered developers and drastically reduced the DevTest window forcing teams to adopt highly automated test infrastructures. While the adoption of these trends and automated test frameworks have improved feature delivery and time to market, they have complicated security assessment, producing substantial gaps between the current release and the last security audited code. Consumers are now being forced to adopt new code releases daily or hourly without substantive security review, especially in the Software as a Service (SaaS) sector. As engineering teams rapidly embrace these development methodologies, the community must evolve security testing strategies so as to enhance the security posture of products, services, and solutions. This evolution must address three primary problems elucidated by the aforementioned development trends: 1. Testability: Security requirements should be testable and verifiable. 2. Scalability: Security requirement should be capable of being automated in a best-effort fashion so as to scale effectively. 3. Accessibility: Security tools and results should be easily digestible by software engineers and testers, and new security tools should be accessible to all development and test engineers. Therefore, we have developed and are preparing to open source a new distributed security testing framework called Norad which facilitates security assessment at scale. This framework automates multiple open-source and vendor security tools and aggregates their results for review. It also provides an SDK which promotes the development of community developed security test content. This talk will explain Norad's design philosophy, architecture, and demonstrate its usage. Speakers Blake Hitchcock Software Engineer, Cisco Blake Hitchcock has been building and breaking web applications for 6 years with Cisco. He loves writing in Ruby, and 'Burp' is not just something he does after a few too many kielbasas. When he's not doing web stuff, Blake enjoys fitness, food, sports, and cheering for his beloved Tennessee Volunteers. Brian Manifold Cisco Brian Manifold has worked as a software/security engineer at Cisco for the past 4 1/2 years. His main areas of interest at work are web development and web security. Outside of work he enjoys playing music, anything CNC (milling, 3d printing, etc..) related, hardware electronics, and spending time with his family. Roger Seagle Principal Engineer, Cisco Roger Seagle Jr. is a Principal Engineer in the STO TIP team at Cisco. Previously, he worked in Cisco's Advanced Security Initiatives Group (ASIG) where he assessed the security posture of Cisco products and advised product teams on patching and mitigating vulnerabilities. - Managed by the official OWASP Media Project https://www.owasp.org/index.php/OWASP_Media_Project Source: https://www.youtube.com/watch?v=hEHCB7iWUzk Uploader: OWASP

Cite this record

OWASP (2016). Scaling Security Assessment at the Speed of DevOps - AppSecUSA 2016. Internet Archive. https://library.shubhaarti.in/content/0bea8740-123a-4a62-ae76-e8ea70862bda

Copy in another style

OWASP. (2016). Scaling Security Assessment at the Speed of DevOps - AppSecUSA 2016. Internet Archive. https://library.shubhaarti.in/content/0bea8740-123a-4a62-ae76-e8ea70862bda
Author names are used as deposited, so check their order before you submit.

Metadata is harvested from open-access indexes and can be incomplete. Check a citation against the published version before relying on it — see our open access & attribution policy.