fix(password): fix missing positive results from Password and Secrets query

[ArturRibeiro-CX]

Reason for Proposed Changes

• Three positive files were missing from the results (positive 8, positive 44, positive 49).

Proposed Changes

• Update positive and negative files that were invalid and not parsed by KICS.
• Fix the numeric naming of negative tests to follow the existing logic.

I submit this contribution under the Apache-2.0 license.

[gitguardian]

⚠️ GitGuardian has uncovered 6 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
4266030	Triggered	Generic Password	c01414b	assets/queries/common/passwords_and_secrets/test/positive8.json	View secret
4266030	Triggered	Generic Password	c01414b	assets/queries/common/passwords_and_secrets/test/positive8.json	View secret
4266030	Triggered	Generic Password	c01414b	assets/queries/common/passwords_and_secrets/test/positive8.json	View secret
4266030	Triggered	Generic Password	c01414b	assets/queries/common/passwords_and_secrets/test/positive8.json	View secret
4266006	Triggered	Generic Password	c01414b	assets/queries/common/passwords_and_secrets/test/negative42.yaml	View secret
4266006	Triggered	Generic Password	c01414b	assets/queries/common/passwords_and_secrets/test/negative32.yaml	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.}

[github-actions]

KICS version: v2.1.1

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 48 Queries failed to execute 0 Execution time 0

[github-actions]

Checkmarx One – Scan Summary & Details – 714338eb-3c38-445d-8137-5e0f5a84c25a

No New Or Fixed Issues Found

[EduardoSemanas]

LGTM

[EduardoSemanas]

LGTM