Difference between revisions of "OWASP AppSec Pipeline"

What are DevOp Security Pipeline Tools?

DevOp security pipeline tools are written with the mindset of API first. The goal is that a security tool will expose all the core functionality of the product as an API. Tools need to have an API so that the 'All the things' can be automated. Each tool will be evaluated with the criteria outlined below including example pipeline use cases.

Evaluation Criteria

Application Description: Overview of the security tool, description and product web page.
API: The type of API (REST, SOAP), API coverage (% of total features available via the API) and API Docs.
Pipeline Position: Where in the AppSec pipeline the tool would be best suited to reside
Cloud Scalable: Is the tool cloud aware and can the tool scale based on demand?
Runs as a Service: Can the tool run as a service or in headless mode?
Pipeline Example: Link to an example use case of the tool in the pipeline
Client Libraries: What client libraries are written to assist in integration. For example a python or Go library.
CI/CD Plugins: Does the tool have CI/CD plugins for integration into a DevOps pipeline. For example a Jenkins plugin.
Data Sent to the Cloud: What kind of data, if any, is sent off premise to the cloud? Is there an option to keep all data in-house?

Results

We are currently working on gathering a list of the current tools and evaluating each tool based on the criteria listed. The goal is to create a one page wiki document of the application.

Get Involved

Interested in participating or having your product included in the review? Contact Aaron Weaver

What is an AppSec Pipeline?

• Designed for iterative improvement
• Provides a reusable path for AppSec activities to follow
• Provides a consistent process for both the team and constituency (Developers, QA, Product Managers etc.)
• One way flow with well-defined states
• Relies heavily on automation
• Has the ability to grow in functionality organically over time
• Gracefully interconnects with the development process

Rugged DevOps AppSec Pipeline Template

Pipeline - Intake

“First Impression”
Major categories of Intake

• Existing Application
• New Application
• Previously tested Application
• Application to re-test findings
  

Key Concepts

• Ask for data about Apps only once
• Have data reviewed when an application returns
• Adapt data collected based on broad categories of Apps

Pipeline - The Middle

• Inbound request triage
  • Ala Carte App Sec
  • Dynamic Testing
  • Static Testing
  • Re-Testing mitigated findings
  • Mix and match based on risk

Key Concepts

• Activities can be run in parallel
• Automation on setup, configuration, data export
• People focus on customization rather than setup

Pipeline - The End

Source of truth for all AppSec activities

• Dedupe / Consolidate findings
• Normalize scanner data
• Generate Metrics
• Push issues to bug trackers
• Report and metrics automation REST + tfclient
• Source of many touch points with external teams

AppSec Pipeline Example #1

Example Rugged DevOps AppSec Pipeline

Example AppSec Pipeline

The specific tools used in a pipeline aren't the important part - its making your AppSec engagements as efficient as possible.

AppSec Pipeline Presentations

• Building An AppSec Pipeline Aaron Weaver - AppSec EU 2015
  
• Taking DevOps Practices Into Your AppSec Life Matt Tesauro - AppSec EU 2015

Rugged DevOp Interviews

• DevOps, Security and Development w/ Matt Tesauro, Jez Humble and Shannon Lietz AppSec USA 2015
• Pipeline Project Interview Matt Konda - AppSec USA 2015

Rugged DevOps

• The Road to Being Rugged Shannon Lietz - GOTO 2015
• When Devops Meets Security Michael Brunton-Spall - GOTO 2015
• Rugged Building Materials and Creating Agility with Security David Etue - GOTO 2015
• How to effect change in the Epistemological Wasteland of Application Security James Wickett - GOTO 2015

TBD

Got a question?

Ask us on Twitter:

• @appsecpipeline
• @matt_tesauro
• @weavera

Contributors

Besides the project leaders, contributions have been made by:

• Adam Parsons - Bag of Holding
• Matt Brown - suggestions and review of Bag of Holding
• Lee Thurlow - suggestions and review of Bag of Holding

Future releases will include:

• List of open source tools for each portion of the AppSec Pipeline
• Additional releases of Bag of Holding with new and exciting features
• Documentation and references to integration of the various pieces of the AppSec Pipeline.