Keynote
summary
Verizon data show about 78% low difficulty exploits and most breaches are opportunistic, so focus is on eliminating trivial entry points not debating theory. Build framework-level guards, ship libraries for crypto and input handling, and centralize practices so developers make the safe choice by default — secure by default and a framework security project are practical steps. Measure outcomes and publish metrics, invest in scalable services and tooling like the Z attack proxy and stop treating security as an isolated checklist.
AI-written summary · about
chapters (10)
- 0:00Conference kickoff
- 1:48OWASP introduction
- 3:35Security breaches and threats
- 5:43Effective security programs
- 7:31Security and developer incentives
- 9:15Framework security automation
- 11:40Metrics for scaling security
- 13:04Balancing security and practicality
- 14:30OWASP projects
- 16:15Getting involved in OWASP
related talks
42mKeynote: How much security is too much?
01h 00mKeynote - Our Kryptonite: A Defendable Internet
58mKeynote: What Got Us Here Wont Get Us There
39mKeynote - The Infosec Survival Field Guide
57mMaking Security Priority Zero
46mKeynote: The Moral Imperatives and Challenges for Modern Application Security
01h 06mKeynote: Devaluing Attack: Disincentivizing Threats Against The Next Billion Devices
56mKeynote: AppSec: From Outsiders to Allies