Главная
Study mode:
on
1
Introduction
2
Who remembers this game
3
Open Source
4
Security Shift
5
Secrecy
6
Secure Versions
7
Automatic Updates
8
Does it help keep users secure
9
Securing users was complex
10
Educating users is difficult
11
History lesson of WordPress
12
Growth of WordPress
13
Assessing Needs
14
Is it Possible
15
Benefits to Volunteers
16
How do we make this work
17
Our tools
18
Tools dont fix our problems
19
Building relationships
20
QA
21
Lost Gentleman
22
Target on our Back
23
Code Review
24
Friction with Feature Development
25
Bug Bounty
26
Warning Signals
27
Incident Response
28
Lessons Learned
Description:
Explore key insights from the WordPress Security Team's experiences in this 52-minute conference talk delivered at BSidesLV 2018. Delve into the challenges and strategies of maintaining security for open-source software, with a focus on WordPress's journey. Learn about the evolution of security practices, including the shift towards automatic updates and the complexities of user education. Discover the team's approach to assessing needs, building relationships, and implementing effective tools. Gain valuable knowledge on code review processes, bug bounty programs, and incident response techniques. Understand the delicate balance between security measures and feature development, and uncover important warning signals for potential vulnerabilities. Walk away with practical lessons learned from one of the most widely-used content management systems in the world.

Lessons Learned by the WordPress Security Team

BSidesLV
Add to list