fix(azurerm_redis_cache): Update policy to detect non_ssl_port_enabled #7028
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.
User description
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Description
The current Checkov policy is looking for enable_non_ssl_port, which is no longer valid after the change in version 4.0.0. The correct attribute is now non_ssl_port_enabled. This update modifies RedisCacheEnableNonSSLPort.py to align with the latest attribute name, ensuring proper detection of misconfigurations.
Fixes # (issue)
New/Edited policies (Delete if not relevant)
https://docs.prismacloud.io/en/enterprise-edition/policy-reference/azure-policies/azure-networking-policies/ensure-that-only-ssl-are-enabled-for-cache-for-redis
Description
https://registry.terraform.io/providers/hashicorp/azurerm/4.0.0/docs/resources/redis_cache#non_ssl_port_enabled-7
Fix
How does someone fix the issue in code and/or in runtime?
Checklist:
Generated description
Below is a concise technical summary of the changes proposed in this PR:
Updates the
RedisCacheEnableNonSSLPort
check to use the newnon_ssl_port_enabled
attribute for Azure Redis Cache resources in Terraform configurations.Latest Contributors(1)