Test Driven DevOps
summary
Claims that stuffing InSpec tests into every environment creates a portable, declarative Rosetta stone for heterogeneous government pipelines, with a living meta profiles repo that teams continuously extend. Describes using InSpec (Chef family), Automate, Nessus, vSphere and C2S AWS in air‑gapped and classified flows, running pre-flight checks before deploy, triaging failures into tests, and merging fixes back to master. Reports this reduced blind spots in a 40‑person firm (95% top‑secret cleared) and produced real cross‑team visibility and faster remediation.
AI-written summary · about
chapters (23)
- 0:00Start
- 5:45"Risk Averse" is an Understatement..
- 8:05Unique Challenges
- 12:25Our "Streamlined" Pipeline..
- 14:03Somebody Please Make It Stop Better!
- 15:45There's an app for that....
- 17:00InSpec is great for Compliance
- 17:32Compliance Example
- 18:03InSpec is great for Functional/Integration
- 18:48Functional Example
- 20:13InSpec Everywhere
- 21:58Migrating to InSpec Profiles
- 22:28Extensible and Abstracted
- 23:02Self Documenting
- 23:36The Bigger Picture: Meta-Profiles
- 24:10InSpec Outside of the Cookbook
- 24:56Applying Profiles to the Pipeline
- 25:07Address Disparate Envs: Pre-Flight Checks
- 25:38All Teams Contribute
- 26:08Continuous Testing - TDD Feedback Loop
- 26:42Organization is Key
- 27:29Improving Deployment Confidence
- 30:28Fail Loudly! Outcomes
related talks
22mMoving Fast Together: Test-Driven Infrastructure
36mIntroduction to Test-kitchen and InSpec
33mMario Star Power Your Infrastructure: Getting the Most Out of InSpec
31mShifting Left Securely
41mA Year with Chef and InSpec: A Retrospective with Optum
25mTransform Your Security Practices With DevOps
49mBaking Safety into Infrastructure Testing
39mTrust teams but verify: compliance as code done right