fix(queries): fix policy evaluation when scanning Terraform plan vs HCL files#7926
Merged
Merged
Conversation
Contributor
… improve maintenance
cx-miguel-dasilva
approved these changes
Feb 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.








Reason for Proposed Changes
jsonencode()are parsed as escaped JSON strings (e.g., "policy": "{"Statement":[...]}")json_unmarshal()which only handles string inputs, causing queries to silently fail on plan files where policies are already objects. This results in various different vulnerabilities being missed when scanning Terraform plans;Proposed Changes
terraform.regoto usecommon_lib.get_policy()instead ofcommon_lib.json_unmarshal()for policy parsing. Theget_policy()function handles both string and object formats consistently;Note
search_lineandsearch_keyare still having problems detecting the same resource each time (depends on the other of the payload structure). When KICS engine is able to point to the root of the project, this query will have the expected behaviour.I submit this contribution under the Apache-2.0 license.