Security Trends and the Economics of “Better”
summary
Regulatory volume is exploding and overlapping rules push teams into checkbox compliance that crowds out higher-value work, not better security. Mandatory practices like static analysis hands source code to third parties create IP and scaling problems, and tools require six to nine months of tuning per team to avoid floods of false positives. Absolute attestations of zero vulnerabilities unrealistic; practical fixes are more supplier transparency, practitioner input via trade associations, and teaching secure engineering at universities.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:47Security evolution
- 4:19Third-party code challenges
- 6:25Cybersecurity economics
- 9:58Regulation consequences
- 14:01Current regulatory trends
- 17:16Problematic regulations
- 20:28Transparency over compliance
- 24:42Secure development attestations
- 27:52Global regulatory pitfalls
- 30:21Security education ethos
- 33:15Systemic security solutions
- 36:28Transparency and optimization
- 40:16Q&A
- 46:39Closing remarks
related talks
49mPragmatic Approaches To Building Secure Software
30mEffective security on a tight budget
03mAn infinite set of security tools
45mState of (Absolute) AppSec
44mApplication Security: Everything we know is wrong
33mBattle Tested Application Security
49mPanel: From Code to Defense: Why Developers Are the New Security Leaders
27mSecurity: The Thing That Everyone...