Developer’s security survival guide
summary
An actionable checklist for developers: use CloudTrail event logs to answer who what where why during an intrusion, onboard Security Hub (expect 11–24 hours for a full org scan), and track suspicious calls in CloudWatch. Favor least-privilege IAM, short‑term credentials and Secrets Manager with rotation, and deliver private files via presigned URLs. Deploy reproducible stacks with SST/CDK for a Next.js App Router site, run CodeGuru scans and add Shield + WAF for DDoS/WAF protection. The repo is runnable and intended to let teams recover faster.
AI-written summary · about
chapters (6)
- 0:00Welcome and introduction
- 1:28DevOps security primer
- 6:46Incident response basics
- 11:23Threat mitigation strategies
- 18:26Architecting secure systems
- 19:50Key takeaways and wrap-up
related talks
38mAdventures in Cloud Security: What DevOps Can Learn from a Security Engineer
46mApplication security from start to finish
27mBridging the Dev-Sec divide: Three tips for agile developers
54mFrom App Security to Dev Security – Shift left with GitHub Advanced Security
19mFrom Code to Cloud: Embedding Security
49mFrom Application Security to Developer Security
34mDevelopers do care about security: Building a more collaborative path
01h 02mStrong security made simple: Putting all the pieces together