A static analysis security scanner for Terraform code that identifies misconfigurations across major cloud providers.
tfsec is a static analysis security scanner for Terraform code that identifies potential misconfigurations and security vulnerabilities across major cloud providers. It analyzes Terraform configurations to detect security risks before infrastructure is deployed, helping prevent cloud security breaches and compliance violations.
DevOps engineers, infrastructure developers, and security teams working with Terraform to manage cloud infrastructure across AWS, Azure, GCP, Kubernetes, and other platforms.
Developers choose tfsec for its specialized focus on Terraform security, comprehensive multi-cloud coverage, fast scanning performance, and seamless integration into CI/CD pipelines and development workflows through IDE plugins.
Tfsec is now part of Trivy
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 hundreds of built-in security rules for AWS, Azure, GCP, Kubernetes, and other platforms, as detailed in the checks sections, ensuring broad coverage across major cloud providers.
Evaluates Terraform HCL expressions, functions like concat(), and resource relationships, providing accurate detection beyond simple pattern matching for nuanced security issues.
Offers IDE plugins for VSCode, JetBrains, and Vim, and easy CI/CD integration with GitHub Actions and Azure DevOps tasks, as shown in the usage examples, fitting into existing workflows.
Supports multiple output formats like JSON, SARIF, and CSV, and allows ignoring warnings with comments or CLI flags, including expiration dates for ignores, enhancing customization.
With the announcement of migration to Trivy, tfsec is no longer the primary focus for development, which may lead to slower updates, reduced feature additions, and eventual deprecation.
Only scans Terraform configurations, so it cannot be used for other infrastructure as code tools, limiting its applicability in mixed or non-Terraform environments.
Creating custom security rules requires proficiency in Rego policy language, which can be a barrier for teams without prior experience in policy-as-code, adding complexity.