Seems Legit: Testing Cloud Provisioning with InSpec
summary
Terraform provisions ten resources; plan reports “10 to add” and apply completes successfully, but manual console edits create a rogue security group that opens port 22 to the world. InSpec inspects AWS account state, finds one rogue security group, asserts negative tests like should not allow in 0.0.0.0/0 on port 22, and fails the control. Also demoed inspec-iggy that extracts checks from Terraform state but currently only matches Terraform’s positive view.
AI-written summary · about
chapters (8)
- 0:00Intro
- 0:33Who am I
- 1:38What is this talk about
- 2:58Terraform
- 9:05Security Groups
- 12:52Inspect Shell
- 17:29Inspect exec
- 22:34Profile
related talks
29mShifting Security and Sanity Left by Testing Terraform with InSpec
31mInfrastructure and Environment Testing with InSpec
52mTest Driven Delivery of Infrastructure-As-Code
45mAudit and Assess the Security of Your Infrastructure
37mInfraCoding with Terraform: Writing Tests for Infrastructure-as-Code
36mBuild infrastructure as a code (IaC) using test-later...
46mInfrastructure testing - it's a real thing!
36mIntroduction to Test-kitchen and InSpec