Feature Requests

In harness STO platform, we need a centralized view of exemptions raised across all the projects. Also, whenever there is an exemption raised, there should be an notification shown/sent.

Currently, Jira creation from the pipeline is proxied through the delegate, while Jira creation from STO initiates directly from the server. In cases where this involves a protected Jira instance (e.g., passing through a firewall to an on-prem Jira), the STO call won’t be allowed unless firewall settings are adjusted.

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.

We would love to have the ability to excempt vulnerabilities by Target or HCR Code Repository.

Hi Team, I'm trying to build a STO dashboard. I'm trying to add a feature where the list of pipelines which has issues and which do not have issues are also added. Right now, I'm only able to see pipelines list which has issues. I'm not able to see pipelines does not have issues. https://app.harness.io/ng/account/H6rHO8vtQYKelD_wgjnMpA/dashboards/folder/shared/view/26443 Can you please help me with that. Regards, Janish

The Checkmarx step only display and evaluate how many types of vulnerabilities identified by Checkmarx. When I scan the project for the 1st time, I got 27 occurrences of SQL Injection: Java High Risk. Pipeline is failed because SQL injection is a new type of vulnerabilities for this pipeline. https://app.harness.io/ng/account/vGS8Qq_fSJik8VyI4rwqHQ/ci/orgs/Corporate/projects/bus0011_INFOSEC/pipelines/Jeremy/executions/BlzR5TNlSMCm5c__pcPyTA/security?storeType=INLINE&pageSizeOccurrences=20&pageOccurrences=0&issue=M5GDsq9z9UIt1UeDtJnudr The second time I run it, I got 28 occurrences of SQL Injection: Java High Risk. Pipeline is success because SQL Injection is an existing type of vulnerabilities. https://app.harness.io/ng/account/vGS8Qq_fSJik8VyI4rwqHQ/ci/orgs/Corporate/projects/bus0011_INFOSEC/pipelines/Jeremy/executions/xYSS-ozVRXSpJfPAQrf3sw/security?storeType=INLINE&pageSizeOccurrences=20&pageOccurrences=0&issue=M5GDsq9z9UIt1UeDtJnudr In case, the product team is introducing another new occurrence of SQL injection. Harness policy is not able to catch this new vulnerability as SQL injection type already exist.