Infrastructure-as-code scanning
IaC scanning articles
Terraform, Kubernetes manifests and Helm charts checked before apply, and linked to the resources they become.
Infrastructure-as-code (IaC) scanning checks Terraform, Kubernetes manifests and Helm charts for misconfiguration before they are applied. These articles cover scanning on the pull request before apply, and handling IaC drift so a finding closes on evidence from the live account rather than on merge.
- Terraform drift: reconcile an emergency changeReview Terraform drift after an emergency change by comparing configuration, state and live resources before choosing a controlled reconciliation. · Sujan Singh
- IaC drift: close findings on live evidence, not on mergeIaC drift means a merged fix is not a deployed one. Link each IaC finding to the cloud resource it created and close it on evidence from the account. · Sujan Singh
- IaC scanning before apply: catch misconfigurations in the PRIaC scanning catches Terraform, Kubernetes and CloudFormation misconfigurations at pull-request time, while the fix is still a one-line change. · Sujan Singh
See it on your stack
See connected security in action.
Explore the workflow with your engineering, security and compliance teams. No repository access is needed for the initial demonstration.