Cloud Security in Continuous Delivery
summary
Cloud migration leaves encryption, region placement and cost policies as concrete failure points — an AWS EBS volume left unencrypted exposes data and linked services. The workflow maps stakeholders (DevOps, Sec, FinOps), prescribes centralized log retention across accounts, uses MITRE mappings to prioritize risks, and replaces manual scripts with an engine that enables automated remediation and forensic traces. Expect guidance on one customizable toolset, retention limits to avoid provider gaps, and automating policy enforcement rather than manual reviews.
AI-written summary · about
chapters (10)
- 0:00Start
- 0:11A few words about me
- 0:50On the agenda
- 3:19The Big Picture - Shared Responsibility
- 4:56The Big Picture - Find the Context
- 6:08Challenge no. 5
- 12:56In conclusion
- 13:06Choosing a tool
- 13:17Here's how to choose a security tool
- 15:59Key takeaways for cloud security in continuous delivery
related talks
01h 03mContinuous Security in the Cloud
45mSecurity Lessons Learned Moving a Bank 100% in the Cloud
28mSecuring Multi-Cloud and Hybrid Environments
17mAdvance securely: Safely migrating to
39mPerils of the cloud
26mCloud Security Lessons
12mArmor cloud security: Security & compliance in the public cloud
53mAchieving End-to-end Security on AWS
