Scan Terraform before deployment for cloud security misconfigurations.
Pipeline
Terraform -> Validate -> Checkov -> Trivy -> Policy -> Plan -> Review -> Apply
Validate
terraform fmt -check
terraform validate
Scan
checkov -d .
trivy config .
Check for public resources, weak permissions, missing encryption, open network paths, and insecure Kubernetes/IaC settings.
Security Gates
A starting model:
Critical -> Block
High -> Block or Approval
Medium -> Review
Low -> Track
Tune thresholds using real false-positive and risk data.
Organization Policies
Examples:
- Production storage must be private.
- Production databases require encryption.
- CI identities cannot have Owner.
- Internet-facing resources require approved controls.
Exceptions
Record reason, owner, compensating control, and expiration.
Final Takeaway
IaC scanning works best when it is part of normal pull-request engineering rather than a post-deployment audit.
Responses (0)
Join the technical conversation or share implementation thoughts.
What are your thoughts?
Sign in to join the technical discussion or share feedback.
There are currently no responses for this story. Be the first to respond.