Code Quality and Security for Infrastructure-as-Code

This SonarSource project is a static code analyzer for Infrastructure-as-Code (IaC) languages such as CloudFormation, Kubernetes, and Terraform. It is a component of the SonarQube platform, and it runs the IaC features on SonarCloud.

It allows you to produce stable and easily supported Clean Code by helping you find and correct vulnerabilities and code smells in your projects.

Features

• 100+ rules
• Supports Azure Resource Manager JSON/Bicep
• Supports CloudFormation JSON/YAML
• Supports Kubernetes YAML and Helm Charts
• Supports Dockerfiles
• Supports Terraform for AWS
  • HCL native syntax for files named with a .tf suffix (JSON format not supported)
  • Terraform for Azure and GCP: coming soon
• Supports configuration files for Spring and Micronaut
• Domains Covered:
  • AWS S3 Buckets
  • Permissions
  • Encryption at Rest
  • Encryption at Transit (coming soon)
  • Traceability (coming soon)
• Metrics (number of lines, comments, etc.)
• Import of cfn-lint results

Useful links

• SonarSource Community Forum
• Issue tracking

Structure

This project is one analyzer/plugin that scans and raises issues on files associated with multiple languages.

The main registration point of the plugin to the API is in sonar-iac-plugin. The analyses of the different languages are separated into "extensions", which get loaded by the main plugin class and are structured similarly to other analyzers (i.e., parser, visitors, checks, rule resources, etc.)

Build & Test

Requirements

• Java 17
• Go 1.21 and the following dependencies:
  • musl on Linux (musl-gcc should be present on PATH)
• Alternatively, Docker should be installed to perform the build of the Go part inside a container
  • In some environments, importing a custom certificate must be performed during the Docker build. Refer to the dedicated readme for more details.

Build and run unit tests:

./gradlew build

Build without running unit tests:

./gradlew build -x test

Fix code formatting issues

During the Gradle build, a spotless formatting check is executed. This check can also be triggered manually with ./gradlew spotlessCheck. It checks if the code is correctly formatted using standard Sonar rules. If your build failed, you can fix the formatting just by running:

./gradlew spotlessApply

Update rule description

Update all rule descriptions.

./gradlew ruleApiUpdate

Update all rule descriptions for a specific language.

./gradlew ruleApiUpdateArm
./gradlew ruleApiUpdateCloudformation
./gradlew ruleApiUpdateDocker
./gradlew ruleApiUpdateKubernetes
./gradlew ruleApiUpdateTerraform

Generate new rule description

To fetch static files for a rule SXXXX from RSPEC for one of the languages, execute the following command:

./gradlew ruleApiGenerateRuleArm -Prule=SXXXX
./gradlew ruleApiGenerateRuleCloudformation -Prule=SXXXX
./gradlew ruleApiGenerateRuleDocker -Prule=SXXXX
./gradlew ruleApiGenerateRuleKubernetes -Prule=SXXXX
./gradlew ruleApiGenerateRuleTerraform -Prule=SXXXX

Additionally, an optional property -Pbranch=<branch name> can be set to fetch rule metadata from a specific branch.