Panel Discussion Led by – Joshua Corman
summary
Advocates hire developers into security because coding skills shorten ramp time about fivefold and teams prefer people who can write code not just write policies. The demo stack uses Arachni and Garmer (Mozilla script) inside a CI gauntlet to run focused tests—e.g., single-page XSS checks—to avoid five-hour scanners that crash builds. Red/blue/purple practices include game days, a red team no-takedown rule, and container provenance checks for supply‑chain hygiene; several teams report this approach finds meaningful issues and fits into automated pipelines.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:53Which attributes and skill sets are most important
- 2:51What skills do you look for in a developer
- 4:25Who should you hire
- 5:35Security tools
- 7:18Blue and red teams
- 9:55Red teaming
- 12:50Blue teaming
- 15:34Containers
- 17:16Docker
related talks
43mSecurity Kaizen for developers
27mSecurity: The Thing That Everyone...
46mAre Developers the New Front Line of Security?
49mPragmatic Approaches To Building Secure Software
49mPanel: From Code to Defense: Why Developers Are the New Security Leaders
34mPurple Team Strategies for Application Security
29mThe SecDevOpronomicon
42mTest Driven Security in the DevOps pipeline