leaks:chore - Adding improvements on leaks rules

[wiliansilvazup]

In this commit I changed to add Safe and Unsafe code
in all rules of the leaks. Reference from issue #630 and #1020.

Signed-off-by: Wilian Gabriel wilian.silva@zup.com.br

[gitguardian]

⚠️ GitGuardian has uncovered 23 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	Secret	Commit	Filename
615391	AWS Keys	0eaacbd	internal/services/engines/leaks/rules_test.go	View secret
615400	Amazon MWS Token	0eaacbd	internal/services/engines/leaks/rules_test.go	View secret
615386	Square Token	0eaacbd	internal/services/engines/leaks/rules_test.go	View secret
1596062	Stripe Keys	0eaacbd	internal/services/engines/leaks/rules_test.go	View secret
1596063	Stripe Keys	0eaacbd	internal/services/engines/leaks/rules_test.go	View secret
615376	Generic High Entropy Secret	0eaacbd	internal/services/engines/leaks/rules_test.go	View secret
615380	Generic High Entropy Secret	0eaacbd	internal/services/engines/leaks/rules_test.go	View secret
1596064	Generic High Entropy Secret	0eaacbd	internal/services/engines/leaks/rules_test.go	View secret
1596065	Generic High Entropy Secret	0eaacbd	internal/services/engines/leaks/rules_test.go	View secret
615391	AWS Keys	0eaacbd	internal/services/engines/leaks/samples.go	View secret
615391	AWS Keys	0eaacbd	internal/services/engines/leaks/samples.go	View secret
615400	Amazon MWS Token	0eaacbd	internal/services/engines/leaks/samples.go	View secret
615400	Amazon MWS Token	0eaacbd	internal/services/engines/leaks/samples.go	View secret
615386	Square Token	0eaacbd	internal/services/engines/leaks/samples.go	View secret
615386	Square Token	0eaacbd	internal/services/engines/leaks/samples.go	View secret
1596062	Stripe Keys	0eaacbd	internal/services/engines/leaks/samples.go	View secret
1596063	Stripe Keys	0eaacbd	internal/services/engines/leaks/samples.go	View secret
1596062	Stripe Keys	0eaacbd	internal/services/engines/leaks/samples.go	View secret
1596063	Stripe Keys	0eaacbd	internal/services/engines/leaks/samples.go	View secret
615376	Generic High Entropy Secret	0eaacbd	internal/services/engines/leaks/samples.go	View secret
615380	Generic High Entropy Secret	0eaacbd	internal/services/engines/leaks/samples.go	View secret
615376	Generic High Entropy Secret	0eaacbd	internal/services/engines/leaks/samples.go	View secret
1596064	Generic High Entropy Secret	0eaacbd	internal/services/engines/leaks/samples.go	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.

---

<sup>🦉 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.

Our GitHub checks need improvements? Share your feedbacks!</sup>