Automating Cloud Security Compliance: From Patching to Machine Image Building and Auto Scheduling
summary
Automated compliance pipeline that actually runs: GitHub Actions enforce security workflows for static analysis and dependency scanning, Docker base images live in ECR and are scanned nightly with daily base-image patching, OS images are built with Packer-built AMIs with Qualys and MDE and deployed via Terraform into Kubernetes and container services. Non‑prod images auto-build every Friday, nodes shut down off hours, patches apply Monday, production updates trigger on the last Thursday of the month, achieving zero downtime, reduced alert noise, and continuous, auditable compliance.
AI-written summary · about
chapters (9)
- 0:00Cloud security automation intro
- 1:10Compliance requirements & challenges
- 2:37Secure pipelines with zero downtime
- 4:05Security tools in dev workflows
- 5:30OS image building with Packer
- 6:15Deploying with hardened images
- 7:20Monthly automated patching
- 9:49Automation benefits & impact
- 10:34Conclusion & Q&A
related talks
32mAutomating Security Compliance at Scale
32mA Security State Of Mind: Compliance and ...
36mImproving Security while Reducing Toil with DevSecOps
40mSecure by Default: Building an AI-Augmented, OSS-Powered Reusable CI/CD Pipeline
46mA Security State of Mind: Continuous Security with Kubernetes
37mDevOps - The Automation of Compliance
43mSecurity in DevOps Strategies
23mBuilding a Secure By-Design Pipeline with an Open-Source Stack