One EdTech’s journey to transforming its security practices
summary
D2L moves from hundreds of unmonitored AWS accounts across five regions and 63 services to a centralized regime using Security Hub, AWS Config and GuardDuty plus runbooks; an internal security bot built on EventBridge, DynamoDB, SQS and SNS auto-creates tickets, notifies owners in Slack and performs auto remediation. Time-to-first-response drops from one week to under an hour (≈99.99%); mean time-to-repair falls from ~1 month (42,000 minutes) to 10 minutes.
AI-written summary · about
chapters (10)
- 0:00Introduction and agenda
- 1:13AWS for EdTech overview
- 3:44Shared responsibility model
- 9:10D2L’s security challenges
- 12:27Automating security with Security Hub
- 15:39D2L Security Bot solution
- 17:52Results and benefits
- 19:58Cloud security strategy steps
- 21:02Operating with control and agility
- 22:36Resources and closing
related talks
23mAn EdTech’s journey to transforming its security practices
41mUsing automation to scale security
01h 02mSecuring data and democratizing the alert landscape
35mThe Good, the Bad and the Ugly — one year of integrating AWS security services
32mAdvanced threat detection and response on AWS
29mAutomating Threat Detection and Remediation
44mTackling Toil: SecOps Automation at Amplify Education
53mAchieving End-to-end Security on AWS