IaC SAST Scanning - post process results to replace Unknown with Info

Customer Request

What happens: When enabling IaC scanning it uses the SAST scanner for their findings, these findings can be of different severity "levels" it seems that Best-practice results sometimes gets mapped to the severity Unknown which in turn is equal to Critical in the Vulnerability dashboard.
Expectation:
Best practice findings should probably be mapped to the Info severity or maybe a way is available to globally configure certain finding "ids" to severity "levels" so the vulnerability dashboard stays "clean" for the Security Department.
Nice to have as a beside: The quality of the why something is an issue seems to differ very much per result.
As an example the finding of "Check if CloudWatch logging is disabled for Route53 hosted zones" has a description of: "'aws_route53_query_log' is undefined" which doesn't state why its an issue that query logging is disabled for a R53 zone.

Response on Slack from @jamesliu-gitlab

kics is the underlying scanner we use for IaC, and I think we just pass through whatever severity level it returns for the vulnerability. We do have an opportunity to post-process the results to replace Unknown severities with Info though. We do something similar in security-code-scan to map certain vulnerabilities to a severity level.