SAST IaC always shows as not enabled in UI

Summary

Projects with SAST IaC scanning enabled have it show as "not enabled" in the UI.

Steps to reproduce

1. Import https://github.com/futurice/terraform-examples to GitLab using Import Repo by URL

2. Add .gitlab-ci.yml containing the following:

   include:
     - template: Security/SAST.gitlab-ci.yml
     - template: Security/SAST-IaC.latest.gitlab-ci.yml
     - template: Security/Secret-Detection.gitlab-ci.yml

3. Commit changes to default branch

4. Verify that kics-iac-sast job successfully executed on the project

5. Go to Security & Compliance > Configuration

6. Verify that SAST and Secret Detection show enabled, but Infrastructure as Code scanning shows "Not enabled".

Example Project

https://gitlab.com/gitlab-org/security-products/tests/ansible/-/security/vulnerability_report

What is the current bug behavior?

• Project with Infrastructure as Code scanning enabled have IaC show as "Not enabled" in Security & Compliance > Configuration
• Banner on vulnerability report page says "Infrastructure as Code (IaC) Scanning [...] are not enabled for this project" even when it is enabled and working as expected

What is the expected correct behavior?

Projects that use IaC scanning have IaC show up as "Enabled" in the UI.

Relevant logs and/or screenshots

Output of checks

This bug happens on GitLab.com

Results of GitLab environment info

This bug happens on GitLab.com

Results of GitLab application Check

This bug happens on GitLab.com

Possible fixes