added policy to check in_transit encryption enable or not for elastic…

avd_docs/aws/elasticache/AVD-AWS-0198/docs.md

@@ -0,0 +1,13 @@
+
+Ensure that your AWS ElastiCache Redis clusters have encryption in-transit enabled.
+
+### Impact
+<!-- Add Impact here -->
+
+<!-- DO NOT CHANGE -->
+{{ remediationActions }}
+
+### Links
+- https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/in-transit-encryption.html
+
+

avd_docs/kubernetes/general/AVD-KSV-01010/docs.md

@@ -2,7 +2,7 @@
 Storing sensitive content such as usernames and email addresses in configMaps is unsafe
 
 ### Impact
-Unsafe storage of sensitive content in configMaps could lead to the information being compromised.
+<!-- Add Impact here -->
 
 <!-- DO NOT CHANGE -->
 {{ remediationActions }}

avd_docs/kubernetes/general/AVD-KSV-0108/docs.md

@@ -2,8 +2,8 @@
 Services with external IP addresses allows direct access from the internet and might expose risk for CVE-2020-8554
 
 ### Impact
-Kubernetes API server in all versions allow an attacker who is able to create a ClusterIP service and set the spec.externalIPs field, to intercept traffic to that IP address. Additionally, an attacker who is able to patch the status (which is considered a privileged operation and should not typically be granted to users) of a LoadBalancer service can set the status.loadBalancer.ingress.ip to similar effect.
-https://www.cvedetails.com/cve/CVE-2020-8554/
+<!-- Add Impact here -->
+
 <!-- DO NOT CHANGE -->
 {{ remediationActions }}
 

avd_docs/kubernetes/general/AVD-KSV-0109/docs.md

@@ -2,7 +2,7 @@
 Storing secrets in configMaps is unsafe
 
 ### Impact
-Unsafe storage of secret content in configMaps could lead to the information being compromised.
+<!-- Add Impact here -->
 
 <!-- DO NOT CHANGE -->
 {{ remediationActions }}

internal/rules/policies/cloud/policies/aws/elasticache/enable_in_transit_encryption.rego

@@ -0,0 +1,25 @@
+# METADATA
+# title: "ElastiCache Redis Cluster Encryption In-Transit"
+# description: "Ensure that your AWS ElastiCache Redis clusters have encryption in-transit enabled."
+# scope: package
+# schemas:
+# - input: schema.input
+# related_resources:
+# - https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/in-transit-encryption.html
+# custom:
+#   avd_id: AVD-AWS-0198
+#   provider: aws
+#   service: elasticache
+#   severity: HIGH
+#   short_code: enable-in-transit-encryption
+#   recommended_action: "Enable in-transit encryption for ElastiCache clusters"
+#   input:
+#     selector:
+#     - type: cloud
+package builtin.aws.elasticache.aws0198
+
+deny[res] {
+	group := input.aws.elasticache.replicationgroups[_]
+	not group.transitencryptionenabled.value
+	res := result.new("Replication group does not have transit encryption enabled.", group.transitencryptionenabled)
+}

internal/rules/policies/cloud/policies/aws/elasticache/enable_in_transit_encryption_test.rego

@@ -0,0 +1,11 @@
+package builtin.aws.elasticache.aws0198
+
+test_detects_when_disabled {
+	r := deny with input as {"aws": {"elasticache": {"replicationgroups": [{"transitencryptionenabled": {"value": false}}]}}}
+	count(r) == 1
+}
+
+test_when_enabled {
+	r := deny with input as {"aws": {"elasticache": {"replicationgroups": [{"transitencryptionenabled": {"value": true}}]}}}
+	count(r) == 0
+}