How Terraform and Behavior-Driven Development Help Shift Security Left
summary
Shows how terraform-compliance and BDD produce an executable specification that runs against terraform plans (prevention only), enforces tag presence and allowed values, and plugs into PR CI in about 20 minutes. Recommends using these readable scenarios instead of Sentinel for clarity, and designing modules deep not wide by minimizing public variables (five binary vars → 32 permutations; five options → 3,125) so secure-by-default modules are adopted and maintainable.
AI-written summary · about
chapters (7)
- 0:00Introduction to BDD
- 2:01BDD for compliance
- 5:12Terraform compliance examples
- 9:43BDD best practices
- 14:40Principles of module design
- 18:02Deep vs. wide modules
- 22:18Adoption and maintenance
related talks
41mTerraform Practices - The Good, the Bad, and the Ugly
35mTerraform Practices - The Good, the Bad and the Ugly
29mTerraform Practices - The Good, the Bad, and the Ugly
15mTerraform Practices: The Good, the Bad, and the Ugly
32mGotchas Using Terraform in a Secure Delivery Pipeline
50mFrom Code to Compliance: Enforcing Azure Security with Terraform and...
52mTest Driven Delivery of Infrastructure-As-Code
30mTerraform Practices to Enable Infrastructure Scaling