Security Lessons Learned Moving a Bank 100% in the Cloud
summary
Company moves ~1,000 servers and all but two appliances into AWS using a lift & shift to EC2, then shifts toward PaaS/serverless; centralizes logs with VPC Flow Logs and boosts SIEM throughput from events/day to events/second. Security stack enforces IAM with MFA, encryption everywhere, immutable AMIs and infrastructure as code; tagging and governance prove critical. Surprises: AWS security group limits (5 groups per NIC, ~60 rules each), lack of native network TAP/IDS, and immature vendor cloud support lead to microsegmentation issues despite overall success. Strategy expands to 120+ AWS accounts for workload isolation and chargeback.
AI-written summary · about
chapters (7)
- 0:00Introduction to cloud migration
- 8:06Golden rules for cloud security
- 16:28Migration gotchas and surprises
- 22:28Lessons learned from the process
- 29:25Strategic changes and adjustments
- 34:51Post-migration next steps
- 36:19Q&A session
related talks
01h 03mContinuous Security in the Cloud
17mCloud Security in Continuous Delivery
36maccelerates its modernization journey with
17mAdvance securely: Safely migrating to
01h 02mTransforming IT pros to DevOps gurus: Ssecure your new tech stacks
26mCase Study of Success
22mFireside Chat with AWS
53mAchieving End-to-end Security on AWS