Skip to main content
2 min read

Enforce Security and Compliance Before Deploy

Enforce Security and Compliance Before Deploy

Goal: insecure or non-compliant infrastructure never reaches your cloud, and you can prove it.

Without StackGen, scanners run after Terraform is written, often after it is deployed. Findings go back to the author as tickets, and fixes take days.

With StackGen, policies run while the appStack is being designed. Violations show on the canvas next to the resource that causes them, and you can block IaC export until they are fixed.

Steps​

  1. Start with built-in policies. New appStacks include StackGen's built-in security policies by default (Include default policies when you create the appStack). See Policies.
  2. Add your own rules. Write security policies in OPA/Rego, or describe the rule in plain language and let StackGen generate the Rego. See Custom Policies.
  3. Bundle them in a governance configuration. Combine security policies, module restrictions and Terraform version rules, then assign the configuration to workspaces. Every appStack in those workspaces must pass it. See Governance Configuration.
  4. Fix violations where they happen. The Warnings counter on the canvas lists each violation and the resource that causes it. See Policy violations.
  5. Check again after plan. When you deploy from StackGen, select Run policy scan after plan to check the real plan before apply. See Plan & Deploy.
  6. Report on it. The Compliance Dashboard shows policy results across appStacks and exports them as CSV, and Audit Logs record who changed what. See Compliance Dashboard and Audit logs.

What you get​

  • Problems found at design time, when they are cheapest to fix.
  • The same rules applied to every team through governance.
  • Evidence for auditors from the compliance dashboard and audit logs.