Cloud Native Security for the Rest of Us
summary
Maps cloud native security into three concrete areas: platform hardening (prefer managed Kubernetes, lock down etcd and the cloud metadata server, enforce Pod Security Standards, keep upgrades current, use quotas/limits and sandbox runtimes like gVisor Arcata Firecracker), user management and permissions (short‑lived TLS/OIDC credentials, RBAC with role/clusterrole bindings, audit with kubectl), and software supply chain controls (signing with Cosign and sigstore, scan with Clair/Trivy, Gatekeeper/OPA policies, Valero backups, minimize long‑lived secrets, use Vault/Sealed Secrets).
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:26FOLLOW SECURITY BEST PRACTICES
- 2:084 C's OF CLOUD NATIVE SECURITY
- 6:54Mini Case Study: Ingress
- 7:53THE WORK OF UPGRADING K8S CLUSTERS
- 10:17MANAGING SECRETS
- 13:09AUTHENTICATION (AUTHN)
- 16:05RBAC AUDITING
- 16:40NAMESPACES vs CLUSTER WIDE
- 19:33ATTESTATION
related talks
41mCloud Native Security For The Rest Of Us
35mCloud Native Security for the Rest of Us
34mCloud Native Security 101: Building Blocks, Patterns and Best Practices
34mCloud Native Security: A New Paradigm for a New World
37mCloud Native Security 101 - Introduction, Workflows and Best practices
39mThe Art of (Cloud Native) Defense: Pillars of Kubernetes Security
44mThe Hitchhiker's Guide to Cloud Native Security on Kubernetes
41mPanel: Securing Cloud Native Applications