KloudSec IaC Security vs kube-score

KloudSec IaC Security scans Terraform and CloudFormation changes in pull requests to identify infrastructure misconfigurations before they merge. Its GitHub App runs scans automatically and reports findings as check runs and inline comments, without requiring CI pipeline changes. Teams can configure critical findings to stop a merge until they are resolved or explicitly acknowledged. The analysis considers relationships among resources, including network exposure, IAM permissions, encryption, and public access. Findings include AI-generated corrected Terraform blocks or CloudFormation snippets. The platform maps nine frameworks: CIS, PCI-DSS, SOC 2, ISO 27001, GDPR, HIPAA, NIST, DORA, and FFIEC. AWS is available, while Google Cloud Platform and Microsoft Azure are listed as coming soon. The Free plan allows five code scans per month and includes email support. A 14-day trial is offered without a credit card; paid plans start at $79 a month. KloudSec describes its intended users as startups, small and medium-sized businesses, and enterprises.

kube-score statically analyzes Kubernetes object definitions and recommends changes intended to improve application security and resilience. Its checks cover container limits, NetworkPolicy targeting, PodDisruptionBudget, Pod anti-affinity, container probes, security context, and stable APIs. Optional checks include matching resource requests and limits, container ports, and seccomp profile configuration. You can configure tests to be ignored or enabled globally or for individual objects. kube-score works with Helm, Kustomize, static YAML files, Docker, and resources retrieved from a Kubernetes cluster. Its browser demo accepts Kubernetes YAML or JSON and, according to the maker, processes it in the browser without sending data to a server. Local options include prebuilt binaries for Linux, macOS, and Windows, along with Docker, Homebrew, and Kubernetes Krew. Output formats include human-readable, JSON, CI, and SARIF. In CI/CD, critical errors return exit code 1; warnings can also be set as the exit threshold. The free, MIT-licensed project recommends analyzing all applications deployed to the same namespace together. Building from source requires Go 1.21 or later.