Production Is the New Attack Surface: Why Post-Deployment Endpoint Detection Is Now Critical
summary
Claims that most risk appears after deployment and that organizations must add a post-deployment detection layer, backed by Ortelius’ Ortelius deployment-centric SBOM catalog and a digital-twin mapping model that links SBOMs to live endpoints without agents. Presenter cites a 200% CVE surge, about 47 critical/high CVEs per day and typical fleets facing 100 to 300 critical/high issues per year, shows continuous syncing to OSV-dev for near-real-time alerts, and describes auto-remediation via repo/Helm linkage.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:49Production as attack surface
- 6:02Post-deployment security blind spot
- 8:34Pre/post-deployment tool limits
- 13:10Digital twin concept
- 17:30Digital twins for auto-remediation
- 19:40Benefits and security alignment
- 20:22Call to action
related talks
30mSecuring DevOps using OWASP DevSecOps Tools
37mExposure Management: The Rise of Proactive Cybersecurity Platforms
50mSoftware Supply Chain: Panel on Threat Intel, Trends, Mitigation Strategies
32mAdapting DevOps in a World of Growing Software Supply Chain Attacks
21mMake threats visible in your cloud environment — Eric Jung
20mEvolving from patch management to risk mitigation
37mSupply Chain Attacks and the Future of Software Delivery
24mFortiying Tomorrow’s CD Pipelines: Harnessing the Power of DevSecOps Data Using...