How organizations are actually applying AWS security best practices
summary
Security-JAWS publishes a 130‑page survey of AWS security practice in Japan and Korea and finds concrete gaps: 100% of users with 10+ years reference the Well‑Architected docs, 86%+ adoption of Amazon GuardDuty in firms with 300–500 employees, but low use of AWS Shield Advanced and only 20–30% using Security Hub or IAM Access Analyzer. About 60% run ongoing risk assessments, ~50% use AWS Organizations, Control Tower is rare, and many still delete sensitive data without encryption while some very large firms (≈18%) rely on passwords only.
AI-written summary · about
chapters (15)
- 0:00Introduction and team intro
- 1:06Survey background and goals
- 3:18Document references for AWS design
- 4:43Who tracks security best practices
- 5:26Risk assessment adoption rates
- 6:07Access methods to AWS environments
- 6:54Infrastructure protection measures
- 8:41Preventive controls implementation
- 9:48Detective controls and GuardDuty usage
- 11:37CloudTrail log analysis tools
- 12:25Sensitive data disposal methods
- 13:57Japan-Korea security trends comparison
- 15:30Underused AWS services in Japan
- 16:41Key takeaways and report insights
- 17:50Security-JAWS community overview
related talks
38mChanging Perspectives: A Deep Dive into the Security Posture of 600+ Real-World AWS Environments
23mSecurity Best Practices: The Well-Architected Framework
34mWhat “Security Needs to Be Our Top Priority” Means for Aws Builders/Customers
27mIntroduction to AWS Security
27mIntroduction to AWS Security
53mAchieving End-to-end Security on AWS
43mAppSec tooling & culture tips from AWS & Toyota Motor North America
44mGuardrails in the Cloud