Panel Discussion: Modern App Security Requires Containers
summary
Argues that containers provide concrete, secure-by-default primitives (names: Notary/TUF, SPIFFE, OPA) that harden the software supply chain and enable immutable infrastructure to cut mean time to patch. Cites real failures — default Kubernetes left open TCP ports leading to credential theft and crypto‑mining — to justify defense‑in‑depth and edge policy enforcement. Describes tooling integration work, audits, and the goal of pluggable identity, signing, and policy systems; notes adoption of TUF-derived signing across many ecosystems.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 3:30QA
- 7:10Kubernetes
- 9:05Showdown
- 12:35Perimeter Security
- 16:30Identity Security
- 19:25Machine Learning
- 21:50Questions
- 22:28Time before Armageddon
- 26:38We are better off now
- 28:25Are we moving too fast
related talks
40mSecuring Containers on the High Seas
29mZero-Trust Containers: Rethinking Security in the Age of Ephemeral...
56mThe Future of AppSec is Cloud-Native
45mCloud, Containers & Security
46mWhat Security People Want: Making DevSecOps Happen with Containers
40mPanel Discussion: Open Source Supply Chain Security - Are Containers..
50mPanel: Whither Security in a Cloud-Native World?
40mClosing Keynote: New Era of Software with modern Application Security
