Cracking the Code of Cloud Security
summary
Claims that 40% pulled from public registries and 12% run as non-root drive the risk story, with images framed as sensitive data and defaults described as insecure. Gives concrete fixes: integrate Clair or Anchore into CI/CD, use AWS image scanning and Dockerfile Lint, enforce least-privilege containers, immutable deployments, microsegmentation and network policies, and centralize secrets (cloud secret manager). Emphasizes automated image scanning numbers, resource limits and audits to make ephemeral containers auditable.
AI-written summary · about
chapters (15)
- 0:00intro
- 1:43preamble
- 2:27stats
- 3:56about fouad
- 4:22agenda
- 5:04introduction
- 6:56challenges in container security
- 10:45cloud container vulnerabilities
- 13:29containers security : devsecops
- 16:25enhancing security: beyond the defaults
- 19:40automated vulnerability management
- 20:06clair
- 20:44configuration management and network segmentation
- 22:47key takeaways
- 23:53thank you
related talks
27mContainer Security Best Practices
19mFrom Code to Cloud: Embedding Security
41mIdentifying and Mitigating Cloud and Container Threats
46mStories from the cutting edge: Cloud security in 2023
32mHacking the Cloud Native Renaissance: Lowering Risk of Kubernetes Adoption- 41mIdentifying and Mitigating Cloud and Container Threats
26mThe 10 Container Security Tricks That (...)
30mMaster the Container Security Model with