Madness of Vulnerability Management in Modern Cloud, Container, How to Win the Battle...
summary
Modern cloud vulnerability counts jump ~40x since 2015 with the NVD showing ~262,000 entries and projections near a million by 2031, so the practical claim is to cut noise by tracing findings to running containers, registry images and owners, then apply reachability analysis plus EPSS/CTI to score exploitability. The team-level solution combines a four‑dimensional risk model (CVSS, business impact, reachability, exploit likelihood), container lineage and asset ownership mapping, registry scanning before deploy, and measured remediation SLAs.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 3:10Cloud impact on vulnerability management
- 8:04Vulnerability explosion and threats
- 15:53Cloud-native asset complexity
- 20:30Building vs buying solutions
- 26:14Threat-centric vulnerability prioritization
- 31:51Attribution in cloud environments
- 36:06Duplication and reachability analysis
- 41:02Risk-based prioritization
- 44:54Threat-centric DNA analysis
- 51:19Conclusion and Q&A
related talks
27mEffective Vulnerability Management for a DevSecOps Pipeline
33mFrom Chaos to Calm: Vulnerability Management for a Dynamic, Sprawling Technology Estate
33mVulnerability Management Lifecycle in DevSecOps
32mIs Vulnerability Management Dead? A Security Architect’s...
43mThe Art of Vulnerability Management - Practical Application of Cyber Triage
24mOvercoming CVE Shock - Adding Perspective in Vulnerability Scanning
20mEvolving from patch management to risk mitigation
58mWhy Can't We All Just Get Along? Bridging the Gap in Vulnerability Prioritization Standards