A static code analyzer that detects security and compliance violations in Infrastructure as Code before provisioning cloud infrastructure.
Terrascan is a static code analyzer designed to detect security vulnerabilities, compliance violations, and misconfigurations in Infrastructure as Code (IaC) before provisioning cloud-native infrastructure. It scans various IaC formats like Terraform, Kubernetes manifests, and Dockerfiles to mitigate risks early in the development process. The tool helps prevent posture drift by monitoring provisioned infrastructure for configuration changes.
Cloud engineers, DevOps teams, and security professionals who manage infrastructure as code and need to enforce security best practices across Terraform, Kubernetes, and other IaC technologies.
Developers choose Terrascan for its extensive policy library (500+ policies), support for multiple IaC providers and cloud platforms, and seamless integration into CI/CD pipelines. Its ability to scan for both configuration issues and container vulnerabilities in a single tool provides a comprehensive security solution.
Detect compliance and security violations across Infrastructure as Code to mitigate risk before provisioning cloud native infrastructure.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Includes over 500 pre-built policies for AWS, Azure, GCP, Kubernetes, and more, providing broad coverage for common security best practices and compliance checks.
Scans Terraform, Kubernetes manifests, Dockerfiles, Helm charts, and other formats, allowing unified security analysis across diverse infrastructure codebases.
Combines IaC misconfiguration detection with container image vulnerability scanning from registries like AWS ECR and Azure, offering a comprehensive security approach.
Designed with exit codes and pipeline integration examples, enabling seamless adoption in CI/CD workflows to enforce security gates automatically.
The project is no longer updated, meaning policies may become stale, security vulnerabilities won't be patched, and support is unavailable for issues or new features.
Custom policies require writing in Rego, a niche DSL that adds a learning curve and maintenance burden for teams wanting to tailor rules beyond defaults.
While it covers major clouds and IaC tools, it lacks support for newer or less common formats like Bicep, potentially missing misconfigurations in evolving ecosystems.