Preventative+Detective Control for Security
summary
Advocates a concrete balance: use pipeline-driven preventative controls for below-the-line fundamentals (SDN, routing, IAM) so misconfigured S3 buckets and internet-facing security groups never reach cloud, and use tag-and-kill ephemeral instances plus event-driven auditing and automated remediation for above-the-line serverless/VMs; notes detector latency can be minutes—unacceptable for some risks—so implement policy controls to block or audit actions via consumable libraries and IaC pipelines.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 0:20Professional controls are for everyone
- 0:34Security Control Framework
- 0:48Cloud Consumption
- 1:02Dynamic Consumption
- 1:16Security Controls
- 1:31Pipelines
- 1:45Speed vs Regulation
- 1:58Detective Controls
- 2:12Audit
- 2:27S3 buckets
- 2:41Problem with detective controls
- 2:55Maturity
- 3:10Detective Control
- 3:24Lambda
- 3:38Policy Controls
- 4:06Standard Audits
related talks
31mA Comprehensive Approach to Cloud Security Posture Management
47mDetection as Code: The Engineering-Focused Future...
21mRecognizing and avoiding cloud security survival mode
27mProactively identifying threats & protecting sensitive data in S3
01h 02mSecuring data and democratizing the alert landscape
37mOptimizing Cloud Detection & Response With Security Chaos Engineering
44mGuardrails in the Cloud
15mHelping security and developers to understand one another