Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Reality-Checking Your Security Testing Program (2.0)

Reality-Checking Your Security Testing Program (2.0)

Most software security testing programs are built to satisfy a compliance requirement or address a pain point. But they're built with misconceptions about what's important, what software quality means, and how software development works in practice.

This presentation explores approaches to improving a security testing practice in an Agile environment, informed by work in and conversations with organizations around the world.

Darren P Meyer (Veracode)

September 23, 2014
Tweet

More Decks by Darren P Meyer (Veracode)

Other Decks in Technology

Transcript

  1. Who am I? Senior Security Researcher Certified Scrum Master Senior

    Security Instructor Senior Technical Architect, IT Security Security Analyst Software Developer/Consultant
  2. You’re not testing Gather Requirements Build & Test Certify Deploy

    Warranty & Support Public Domain Photo provided by Peterrhyslewis via Wikimedia Commons Security “Testing”
  3. Do Assurance not Control Gather Requirements Build & Test Certify

    Deploy Warranty & Support Public Domain Photo provided by Peterrhyslewis via Wikimedia Commons Quality Control
  4. Security is an Assurance Activity Gather Requirements Build & Test

    Certify Deploy Warranty & Support Public Domain Photo provided by Peterrhyslewis via Wikimedia Commons Security Testing Security Testing Security Testing
  5. We are Agile! Signs you’re actually “Fauxgile”: •  Zero product

    documentation •  Lots of project documentation •  Teams bigger than about 9 people •  Testing is only done by “QA” •  Lack of key Agile metrics