Feature Requests

Similar to how CI can pull JUnit.xml from both the Test-specific steps as well as any arbitrary Run step in CI stages, it would be awesome for Run steps to have an option to pass the location of a SARIF or STO-formatted JSON, as well as the Target/Variant information, to effectively remove the requirement for a downstream Custom Ingest step and save on overall build time and maintenance.

There is a hard limit applied for number of occurrences where after an issue/vulnerability occurred for 1000 times in scan results, harness STO is not scrutinizing the other number of occurrences. Expected Solution: The STO should have an ability to report all the occurrences of the vulnerability/issue in scan results.

Kindly address the SSL issues between the runner and the SMP server so users can remove the "verify_ssl false" setting for enhanced security, and additionally, update the runner to eliminate the need for executing the CP command in the run step, streamlining the deployment process.

The caching steps that are available in the CI module should also be available in the security module. These are particularly handy for SCA scans that download the dependencies before performing the scans.

workspace path in wiz step limited to 128 characters, can we increase the characters?