Red Team, Blue Team Or White Cell? Trends In IT
summary
Argument that security must behave like an immune system with fast feedback loops not hard shells backed by examples and a working pipeline: an automatic image builds process uses Jenkins to run unit tests for shellshock so images never ship vulnerable, API endpoints get unit tests for auth and CSRF, and critical code carries signature checks that fail builds until peer review occurs. The claim includes incidents rising from about 0–1 to six or seven in 2014 to justify speeding incident response and shifting left.
AI-written summary · about
chapters (10)
- 0:00Immune system parallels
- 3:48Adaptive immune systems
- 7:49Threat detection in immune system
- 11:24Infosec barriers and feedback
- 14:57Learning from failures
- 18:10Feedback loops with unit tests
- 21:53Testing negative space
- 24:30End of infosec island
- 25:53DevOps and system thinking
- 27:38Q&A
related talks
39mColorful AppSec - Red, Blue, or Purple?
49mTraining for Incident Response: The Red, the Blue, and the Ugly
34mPurple Team Strategies for Application Security
33mBuilding Red Team Capability
46mBlue Team Security Actual Security work for Actual Developers
43mGuerrilla Warfare for the Blue Team
56mOn Building Teams
42mRed vs. Bank: Surviving a Three Year Red Team