Streamlining Compliance: Leveraging OS Terraform AWS modules
summary
Shows using terraform-aws-modules plus a new compliance-tf proxy registry that hardcodes secure defaults so modules enforce controls (example: CloudFront TLS set to TLS1.2_2018), demonstrated by applying the patched module and raising Prowler pass count from 16 to 17. Uses Checkov (noting recent Python 3.13 breakage) for config scanning, Prowler for live AWS posture, and AWS Config rules for continuous checks. The claim: centralizing hardened modules eliminates repeated remediation and prevents developers from reverting to insecure defaults.
AI-written summary · about
chapters (8)
- 0:00Introduction and speaker background
- 6:30What is compliance and frameworks
- 13:16Compliance process explained
- 17:56Implementing compliance controls
- 20:06Live demo of compliance TF
- 33:21AWS Config and automation
- 37:21Summary and compliance TF benefits
- 40:35Q&A session
related talks
45mStreamlining Compliance: Leveraging Open-Source Terraform AWS modules
35mReplace Terraform Module Forks with Automatic Policy Transformation Rules
54mCompliance-As-Code For API Security
50mFrom Code to Compliance: Enforcing Azure Security with Terraform and...
33mCompliance as Code - Lessons Learned From Regulated Organizations
26mAutomating FedRAMP Security Compliance with Terraform
47mHow to build scale & maintain 45 pub Terraform mod. with over 100 million provisions
22mLaunch Control - Automating a Security Baseline...
