Policy as [versioned] Code
summary
Argument: store policy in git, publish it as a versioned artifact, and treat it like any other dependency so apps and infra declare which policy version they use. Prototype uses Terraform and Kubernetes manifests, semantic versions (1.0.0 → 2.0.0 → 2.1.0), signed releases, tests that run locally and in CI, renovate creating automatic pull requests, and an admission-controller-style evaluator that accepts multiple policy versions so org-wide compliance is measurable and updatable. policy as a dependency semantic versioning renovate auto-PRs
AI-written summary · about
chapters (7)
- 0:00Introduction with lift analogy
- 5:35Meet the speaker Chris Nesbitt Smith
- 7:20Policy problems in real life
- 11:16Policy as versioned code
- 15:47Demo with Terraform and Kubernetes
- 20:46Culture change and next steps
- 21:51Q&A and closing remarks
related talks
25mPolicy as [versioned] Code
34mPolicy As [Versioned] Code
10mLightning Talk: Policy as [Versioned] Code - You're Doing It Wrong.
41mModern Policy Management Putting responsibility where it belongs
30mEnhance your Compliance with Policy-Based CI/CD
41mPolicy as Code with Sentinel Language
23mPolicy-driven Deployments in Spinnaker
45mCatching Commits to Secure Infrastructure as Code
