The power of preventative cloud security with Tenable and
summary
Argues that shifting security left with policy as code prevents most cloud exposure by enforcing checks before deployment, showing an example where one misconfiguration touches 13,000 resources. Demonstrates pipeline scans (sample Jenkins flow), inline IDE scans for CloudFormation, and Tenable One + CloudFormation integration that auto-generates pull requests to apply remediations as code. Points to the open source tool Terrascan as the practical scanner; claims fewer runtime alerts and much faster remediation when merged.
AI-written summary · about
chapters (7)
- 0:00The conflict in cloud scaling
- 1:27Challenges of visibility
- 2:45Contextualizing risk
- 5:40Policy as code
- 7:30Reactive vs. preventative
- 9:32Automated pipelines
- 11:41Empowering developers
related talks
12mCloud security: A critical part of your exposure management program
20mFrom humans to machines: Mitigate risk for all identities in the cloud
22mSecurity vs Dev Experience Threat … or Opportunity
18mManaging your cloud security universe as one
33mAutomating Cloud Security and Incident Response (DevSecOps)
31mA Comprehensive Approach to Cloud Security Posture Management
47mFuture-proofing cloud security: A new operating model
29mShifting Terraform Configuration Security Left