MC-397-Add cli support to SCS

[diogo-fjrocha]

Description

This PR adds Supply Chain Security (SCS) to the engines that can be scanned. It adds SCS results to the console report and the jsonSummary report

References

https://checkmarx.atlassian.net/browse/AST-38888

Testing

Added unit tests to verify the presence of the SCS summary in the console report, including checking an added summary with the results per each micro-engine covered by Checkmarx's SCS.

Integration tests for result and scan commands are still being added

Checklist

• [ ] I have added documentation for new/changed functionality in this PR (if applicable).
• [ ] I have updated the CLI help for new/changed functionality in this PR (if applicable).
• [ ] All active GitHub checks for tests, formatting, and security are passing
• [ ] The correct base branch is being used

[github-actions[bot]]

Checkmarx One – Scan Summary & Details – 41e27807-0d97-47d6-9399-aebf29267987

Policy Management Violations

Policy Name	Rule(s)	Break Build
[SAST-ML0] Not allowed NEW Sast vulnerabilities		true

No New Or Fixed Issues Found

[gitguardian[bot]]

⚠️ GitGuardian has uncovered 16 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
11482443	Triggered	Generic Password	a133046e4dcccf62c2f8ddcac6e39894398a832a	internal/commands/data/python-vul-file.py	View secret
11482443	Triggered	Generic Password	06c8cbb2eb0ca6bde607620ef39f629673c3c0a3	internal/commands/data/python-vul-file.py	View secret
11482444	Triggered	Username Password	a133046e4dcccf62c2f8ddcac6e39894398a832a	internal/commands/data/python-vul-file.py	View secret
11482444	Triggered	Username Password	06c8cbb2eb0ca6bde607620ef39f629673c3c0a3	internal/commands/data/python-vul-file.py	View secret
11482445	Triggered	Generic Password	a133046e4dcccf62c2f8ddcac6e39894398a832a	internal/commands/data/python-vul-file.py	View secret
11482445	Triggered	Generic Password	06c8cbb2eb0ca6bde607620ef39f629673c3c0a3	internal/commands/data/python-vul-file.py	View secret
11482446	Triggered	Generic Password	a133046e4dcccf62c2f8ddcac6e39894398a832a	internal/commands/data/python-vul-file.py	View secret
11482446	Triggered	Generic Password	06c8cbb2eb0ca6bde607620ef39f629673c3c0a3	internal/commands/data/python-vul-file.py	View secret
11482448	Triggered	Generic Password	a133046e4dcccf62c2f8ddcac6e39894398a832a	internal/commands/data/python-vul-file.py	View secret
11482448	Triggered	Generic Password	06c8cbb2eb0ca6bde607620ef39f629673c3c0a3	internal/commands/data/python-vul-file.py	View secret
11482449	Triggered	Generic Password	a133046e4dcccf62c2f8ddcac6e39894398a832a	internal/commands/data/python-vul-file.py	View secret
11482449	Triggered	Generic Password	06c8cbb2eb0ca6bde607620ef39f629673c3c0a3	internal/commands/data/python-vul-file.py	View secret
11482450	Triggered	Generic Password	a133046e4dcccf62c2f8ddcac6e39894398a832a	internal/commands/data/python-vul-file.py	View secret
11482450	Triggered	Generic Password	06c8cbb2eb0ca6bde607620ef39f629673c3c0a3	internal/commands/data/python-vul-file.py	View secret
11482451	Triggered	Generic Password	a133046e4dcccf62c2f8ddcac6e39894398a832a	internal/commands/data/python-vul-file.py	View secret
11482451	Triggered	Generic Password	06c8cbb2eb0ca6bde607620ef39f629673c3c0a3	internal/commands/data/python-vul-file.py	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.}