STO Prisma step currently only ingests vulnerability results and NOT compliance results (despite Prisma producing both).
In Prisma console, we have CI threshold configured to fail on HIGH and CRITICAL findings for Vulnerabilities and Compliance. In Harness, we found that in order to ensure build fails, we need to set threshold on the step within Harness. I set this threshold to HIGH. However we are finding that Harness is only ingesting vulnerability findings and not compliance findings.
The Prisma scan will fail for compliance (which can be seen printed in output), but because Harness does not read compliance findings it is not failing the build nor populating the compliance items into security tab.
Desired outcome: Both vulnerability and compliance findings are ingested by Harness, populated to Security tab, and build failure can be tied to vulnerability AND compliance results based on defined threshold.