Checkov

checkov.io ↗

Scans infrastructure-as-code and related artifacts for cloud misconfigurations and security policy failures.

SI Score
80/100
Pricing
Open Source AI reading, not confirmed
Free plan
Not confirmed
Sign-up required
Not confirmed

Ask SI about Checkov

Answers use saved listing facts and recorded sources.
Homepage screenshot
Screenshot of the Checkov homepage

What it does

Checkov is a command-line static analyzer for infrastructure as code. It checks supported configuration files and plans against security and compliance policies, reporting which checks pass, fail, or are skipped. Its repository also describes software composition analysis for container images and open-source packages. These are checks on supplied files or artifacts, not tests of a running application.

Run a scan on infrastructure files

Install Checkov from PyPI, then point it at the directory containing the infrastructure you want to inspect. The official quick-start example is checkov -d /user/tf; replace that example path with your own directory. The GitHub repository also documents scanning an individual file or a Terraform plan in JSON form.

The input is your infrastructure configuration or plan. Checkov compares it with built-in policies for misconfigurations and security or compliance concerns, then reports results with file and resource context. The project lists support for formats including Terraform, CloudFormation, Kubernetes, Helm, Dockerfiles, Bicep, and OpenTofu. It also supports scans in CI systems such as GitHub Actions and GitLab CI.

For a simple local infrastructure scan, the quick start shows installation and a directory path, with no account setup described. Some optional capabilities have different access requirements: the repository's examples for severity filtering and scans of images or packages show a Prisma Cloud API key; image and package examples also use a repository ID. Check those prerequisites for the specific scan you plan to use.

Checkov analyzes configuration and package or image data; it does not validate how an application behaves when running. Its repository notes the scope limitation of static analysis, including resources managed manually rather than through scanned configuration. The command above is the vendor's documented example, not a scan run for this listing.

Strengths

  • A local CLI scan can start from an infrastructure directory or an individual file.
  • The project documents a broad range of infrastructure formats and CI integrations.
  • The repository is published under the Apache License 2.0.

Watch out for

  • Static analysis is limited to the inputs and checks supplied; it does not test application behavior at runtime.
  • Some documented severity-filtering and software-composition scans require a Prisma Cloud API key.

Best for

  • Checking infrastructure configuration for security and compliance issues before deployment
  • Adding IaC policy checks to a CI pipeline
  • Scanning supported container images or open-source packages when the required API access is available

Sources