Steve Schmidt, AWS | AWS Re:Invent 2013
summary
Amazon says it shrinks information perimeters, adds CloudTrail logs every five minutes so customers see every API call and service-initiated call, and offers CloudHSM where only customer holds keys so Amazon staff can’t access crypto. Regions require explicit data-location tags and transfers, govcloud is identical security run by U.S. persons, and independent audits (Ernst & Young SOC reports) validate physical and operational controls. Redshift powers behavior analytics for faster detection.
AI-written summary · about
chapters (22)
- 0:00Introduction and welcome
- 1:09Security as top cloud concern
- 3:34Lessons from FBI to AWS
- 5:00Security the Amazon way
- 6:23Advantage of DC location
- 7:05Art and science of security
- 8:06Industry shift to real-time security
- 9:09Physical access philosophy
- 10:55Certifications and accreditations
- 12:40Cloud security vs on-premise
- 14:04Data residency requirements
- 15:08Equal security for all customers
- 15:51Shared responsibility model
- 16:53AWS GovCloud security
- 17:14CloudHSM explained
- 18:18Redshift for security analytics
- 19:24Machine learning in security
- 20:26Customer trust and brand expectations
- 21:31Security as a do-over opportunity
- 22:13Diverse security approaches
- 23:16Auto scaling security
- 23:57Final thoughts and bumper sticker
