feat(query): implementation of DAX_Cluster_Not_Encrypted for CloudFormation/aws

[cx-andre-pereira]

Reason for Proposed Changes

• This query flags samples where a AWS::DAX::Cluster type resource does not have SSE enabled. (SSEEnabled field set to true)
• It serves an identical purpose to the Terraform equivalent query.

Proposed Changes

• First i implemented a check for the resource.Properties.SSESpecification.SSEEnabled to ensure it is not set to false.
• Through the documentation for the AWS::DAX::Cluster and SSESpecification i realised that both the SSESpecification and SSEEnabled are optional fields; given this i added case handling for missing either one of these fields.
• For the tests, positive1/2 and positive5/6 represent the most simple SSEEnabled set to false scenario, in JSON and YAML formats for false/"false" values.
• The rest of the positive tests are missing either the SSESpecification or SSEEnabled field and flag accordingly.

I submit this contribution under the Apache-2.0 license.

[github-actions]

KICS version: v2.1.11

Category Results CRITICAL 0 HIGH 0 MEDIUM 0 LOW 0 INFO 0 TRACE 0 TOTAL 0	Metric Values Files scanned 1 Files parsed 1 Files failed to scan 0 Total executed queries 47 Queries failed to execute 0 Execution time 0

[cx-eduardo-semanas]

LGTM

[gitguardian]

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
4266022	Triggered	Generic Password	02c7fa8	assets/queries/cloudFormation/aws/amplify_branch_basic_auth_config_password_exposed/test/negative7.yaml	View secret
9419039	Triggered	Username Password	02c7fa8	assets/queries/cloudFormation/aws/amplify_app_basic_auth_config_password_exposed/test/positive6.json	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}