GitLab KICS IaC SAST template using outdated kics version (v2.1.7-alpine) resulting in false positive findings

Summary

GitLab's IaC SAST template is using kics version v2.1.7-alpine, when the current latest version is v2.1.13-alpine. Since v2.1.7-alpine, there have been improvements made to the scanner, including a false positive rule fix (in 2.11.1) for Storage Account Not Forcing HTTPS with Azure (azurerm)

Steps to reproduce

N/A

Example Project

N./A

What is the current bug behavior?

GitLab IaC SAST template is using outdated version of kics, which contains false positive rules that can cause confusion for customers/users.

What is the expected correct behavior?

GitLab IaC SAST template would use the latest or a newer version of kics. 2.1.7-alpine was released in April 2025

GitLab IaC SAST should be using at least 2.1.11 if possible.

Relevant logs and/or screenshots

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check

(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)
(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)
(we will only investigate if the tests are passing)

Possible fixes

Patch release information for backports

If the bug fix needs to be backported in a patch release to a version under the maintenance policy, please follow the steps on the patch release runbook for GitLab engineers.

Refer to the internal "Release Information" dashboard for information about the next patch release, including the targeted versions, expected release date, and current status.

High-severity bug remediation

To remediate high-severity issues requiring an internal release for single-tenant SaaS instances, refer to the internal release process for engineers.