Risk Management in a Coded Enterprise
summary
Demo uses three compute instances across dev/qa/prod and shows a concrete policy-as-code workflow: a new compliance control is edited, checked into Git, then the pipeline uses Chef Habitat and Terraform to build a signed artifact that is deployed to QA where running instances are flagged non-compliant. A configuration-as-code change is committed, built and promoted through a manual gate to production, production nodes are scanned, and the demo remediation succeeds, proving end-to-end control of change and reduced drift.
AI-written summary · about
chapters (4)
- 0:00Start
- 2:01Security Validation
- 3:04The Coded Enterprise
- 4:05Managing Security and Changes in a Coded Enterprise
related talks
33mCompliance as Code - Lessons Learned From Regulated Organizations
50mFrom Code to Compliance: Enforcing Azure Security with Terraform and...
43mPolicy-as-code for Any Cloud to Any Edge Automation
22mRethinking Risk, Governance, and Compliance Applying Automation
37mDevOps - The Automation of Compliance
18mLet Devs Be Devs Without Sacrificing Security
33mCompliance Without the Chaos: Building It Right Into Your DevOps...
39mTrust teams but verify: compliance as code done right