Web Developer Security: Best Practices & Beyond
summary
Last year’s workshop launches an ongoing community group (SWAG) that gathers W3C, OpenSSF, Open Web Docs, Mozilla, Google, OpenJS, BBC and others to fix concrete gaps: developers are confused about threats and terminology, so the group maps web security features, pushes content security policy and CORS guidance into MDN, prototypes package security scoring for npm, and publishes minutes and a public GitHub repo. Work starts June and is active but practical deliverables are guidelines and docs not formal specs.
AI-written summary · about
chapters (6)
- 0:00Introduction and speaker background
- 3:39Why web security matters
- 9:01W3C and security initiatives
- 12:20Developer confusion on security
- 13:04SWAG Community Group goals
- 17:04Call to action and resources
related talks
22mSecurity, Privacy & Authenticity on the Web
26mOpenSec and Why WebAppSec Matters
58mPractical Secure Development and Operations with JavaScript in 2020
32mSAFE WG Intro – Jeyappragash J J, padme.io, & Ray Colline, Google
30mWeb Service Workers - Breaking The Web Because It Would Be A Sh...
18mWeb Application Security & Mentoring
14mDeveloper Guide
41mWeb Security