Achieve your identity, security, and compliance goals on
summary
AWS recommends a concrete, automated program: enforce least privilege and multi‑account isolation, ban long‑lived keys in favor of short‑term credentials, and define account baselines implemented by Control Tower or Landing Zone plus CloudTrail and Config for detection. Use GuardDuty/Detective for incidents and Artifact for audit reports. APN offers delivery programs like SaaS Factory and guided FedRAMP/A2O work that cut timelines — one partner cites 50% faster time‑to‑market, another achieved FedRAMP moderate in under 60 days.
AI-written summary · about
chapters (14)
- 0:00Introduction and welcome
- 1:04Why security matters for partners
- 4:32Shared responsibility model
- 5:56Identity strategies and best practices
- 13:40Security controls and AWS services
- 16:49Baseline security for AWS accounts
- 21:23Testing and automating security
- 24:09Data classification and protection
- 25:53Compliance goals and AWS support
- 30:07Deploying solutions with AWS programs
- 31:10Addressing cybersecurity talent gaps
- 33:16SAS Factory program overview
- 37:14FedRAMP and ATO compliance programs
- 41:26Key takeaways and next steps
related talks
44mGuardrails in the Cloud
57mBest practices for cloud governance at scale
21mSecuring hundreds of AWS accounts for streamlined governance
23mGetting started with identity on AWS
27mIntroduction to AWS Security
40mCreating a managed, governed, and secure SaaS foundation on
53mAchieving End-to-end Security on AWS
58mCreate enterprise-wide preventive guardrails