Security foundations for containers
summary
Cloud breaches often come from broad automated scans not targeted hunts, with 51% external breaches and detection times increasing; simple RCEs can turn a probe into full compromise in one hit. Practical controls recommended include network segregation, resource limits, image hardening, and IAM roles for ECS tasks instead of long‑term credentials. Operational pieces are CloudTrail/GuardDuty logs, pre‑ and post‑deployment vulnerability scanning, traffic monitoring and tagging, and using a native container IDS integrated into the AWS stack.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 0:27Why is security important
- 2:03Containers on the rise
- 3:42Cyberkill chain
- 4:47Security foundations
- 5:00segregate your containers
- 6:32container traffic
- 8:46Tagging
- 9:57Logging auditing
- 11:43Monitoring vulnerabilities
- 13:17Summary
- 15:35Alert Logic
related talks
27mContainer Security Best Practices
24mCracking the Code of Cloud Security
41mIdentifying and Mitigating Cloud and Container Threats
05mContainer Security Best Practices
24mDon’t be a fail whale, secure your containers
57mPreventing Attacks at Scale
44mA deep dive into container security on AWS
35mThe 10 steps of Container Security: It's not that hard !