Главная
Study mode:
on
1
Introduction
2
What is a security vulnerability
3
The Venn diagram
4
What are security vulnerabilities
5
Is it secure
6
Is it compromised
7
Is it vulnerable
8
WordPress vulnerability
9
Traditional hacker
10
Money
11
Chromium Bug Bounty
12
How Much Do They Pay
13
What Is A CVE
14
The Silent Bug Fix
15
How Does This Help Me
16
Include An Update Mechanism
17
How To Track Vulnerabilities
18
Ikey Aikido Dirty
19
Attackable Surface Area
20
Privilege
21
Code Reviews
22
Should an outside company seek outside expertise
23
Are there plans to put CVE messages in kernel commits
Description:
Explore strategies for managing and surviving the onslaught of security vulnerabilities in open source products. Learn about Common Vulnerability Enumeration (CVE) IDs, privately known security vulnerabilities, and 0-day vulnerabilities. Discover techniques to effectively manage product security, improve over time, and avoid feeling overwhelmed. Gain insights into the nature of security vulnerabilities, the importance of update mechanisms, and methods for tracking vulnerabilities. Examine concepts such as attackable surface area, privilege management, and code reviews. Consider the value of seeking outside expertise and understand the potential for including CVE messages in kernel commits. Equip yourself with the knowledge to protect your open source product and thrive in the face of constant security challenges.

Surviving the CVE Firehose: Strategies for Open Source Product Security

Linux Foundation
Add to list
0:00 / 0:00