Multi-Cloud Compliance As Code with InSpec
summary
Claims that compliance can be automated across clouds and delivered on a tight schedule using InSpec with concrete tooling: AWS Lambda running InSpec to scan accounts, JSON output into ELK/Splunk for correlation, Vault/OpenFaaS for secrets and on‑prem vSphere scanning. Two companies (650 vs 15 employees) migrate and integrate assets under an eight week deadline, deploy app stacks (nginx/node/mariadb) across dev→test→prod 1→2→3 nodes, and report the portal ships and production turns green.
AI-written summary · about
chapters (20)
- 0:00Start
- 0:21Martez Reed
- 1:43Problem Statement
- 2:09DataPharm
- 3:55Environments
- 4:35Data Environment
- 4:56AWS Infrastructure
- 5:27vSphere Infrastructure
- 5:46Docker Hosts
- 6:09Jenkins Server
- 6:45Vault Server
- 7:34Metrics
- 8:00Chef Compliance
- 8:17Chef Automate
- 9:27Test Infrastructure
- 12:57Overall App Compliance
- 13:50Testing Environment Compliance
- 14:07Production Environment Compliance
- 14:55Project Outcome
- 15:06Questions?
related talks
38mKick Starting our DevOps Transition with Chef Compliance
25mTransform Your Security Practices With DevOps
33mCompliance as Code - Lessons Learned From Regulated Organizations
31mShifting Left Securely
31mInfrastructure and Environment Testing with InSpec
40mMy Journey Into Technology Through InSpec
17mEnhancing cloud security with continuous compliance
54mCompliance-As-Code For API Security