Our Veracode is set to fail on Policy, this allows for VMAST to ignore a vuln that is proven to be a false positive for a given team/module.
We found Veracode STO step only support fail_on_severity. So our user will see the discrepancy between harness pipeline status and veracode site status ( see attached). If you look at the veracode report, you can see there's a attribute called "policy_compliance_status", that's the policy status shows up in our veracode site.
Created by zendesk-write-access
September 28, 2023