How to stop worring about application Container security
summary
USCIS runs 30 microservices in production today with a plan for ~200 in a year and processes 7.6M applications annually; the team moves security left with Jenkins-driven CI/CD, image scans plus runtime profiling, and a trusted internal registry that enforces metadata and promotion rules. Images bake patches and avoid baked secrets by using runtime environment variables; hosts segregate public and sensitive clusters on AWS, orchestration limits privileges so there are no root users and many services run as read‑only to enable automated redeployments and faster releases.
AI-written summary · about
chapters (12)
- 0:00Intro
- 2:41Our Application Challenges
- 4:09Our Security Challenges
- 5:56Understanding the basic tech
- 7:41Your app container is on fire...
- 12:11Moving Security Upstream
- 15:37Building an Container Ecosystem
- 18:15Learning Secure App Containers
- 23:37Countermeasures for Major Risks
- 30:22Host Security Management
- 32:17Image Security Management
- 35:24Data & Ops Management
related talks
15mContainerization and micro-services in real life change security and vulnerability management
48mSecurity and compliance for container-based microservices
27mContainer Security Best Practices
35mThe 10 steps of Container Security: It's not that hard !
32mA Security State Of Mind: Compliance and ...
05mContainer Security Best Practices
21mHow containers make security and compliance instantly easier
35mContaining the Container: Developer Experience vs Strict Security Posture