Feature Requests

Does sonarqube extraction scan supports pulling pull request scans? Assuming that we enable the API access to the ADO Connecters, how should we pass the pull request id to the sonarqube scan step? If the extraction scan does not support the pull request scan, is there a way to pass the specific analysis id and have it pull that?

Hi team, Since building the arm64 image is on-demand nowdays and harness now supports the build of arm64, however the STO supports amd64 only, can we enhance the STO to support both arm64 and amd64 therefore we don't need to create separate stages between build and scan?

Hello dear support team, looking for your kind support for adding following plugins: . Checkmarx native plugin for checkmarx one . Fluid attacks native plugin It's a very nice feature the integration of results for several AST tools anyways those I mentioned are not available Thanks

Customer wants the ability to override image path similar to CI

STO has it's own way of calculating vulnerabilities than that of the scan tool. We'd like the ability to use the specific calculation of the scan tool instead of what STO returns. For example, we have a medium severity vulnerability reported by Prisma Scan that Harness is reporting as high/critical. Although Harness does provide the raw scan results from the scanner, we'd like the ability to set the default results to be from Prisma instead of taking the calculation from STO in the Harness UI.

The SonarQube Scanner Plugin currently does not support special characters in branch names for automatic target detection. This limitation is causing our pipeline to fail.

We migrated our organization from CxSAST/CxSCA to CxOne. In the meantime, I'm using the Github Action, thanks.

STO step support for gathering code coverage from Sonarqube step in extraction mode

Hi team, We need a feature that enables us to use Quality gate in our sonarqube scan step. The pipeline should fail when it fails the quality gate checks. Can you please help us on this requirement. Thank you.

STO should have the exempted issues with severity details. (Priority : High/Urgent) Harness API should provide the detail for the exempted issue with severity and its meta data (issue description, CVE code) for the specific pipeline, project. (Priority : Moderate) The STO All Issue Summary Dashboard is not loading and keep spinning (Priority : Low)