# How do you handle HCL AppScan build failures when critical issues are found?

We use HCL AppScan in our pipeline so builds fail automatically when a critical issue is detected, and the scan report gets attached to the release record. That removes a lot of back-and-forth before launch, and we have OWASP-grouped findings mapped to the severity levels already in our release policy. The downside is that AppScan can stop builds while we are still building, so someone has to clear the blocked queue and manage exceptions. How are you balancing strict build blocking with keeping delivery moving?

##### Post Metadata
- Posted at: 20 days ago
- Author title: Delivery Manager Middleware &amp;amp; Automation (Technology Integration) at Indra Group
- Net upvotes: 1



## Related Product
[HCL AppScan](https://www.g2.com/products/hcl-appscan/reviews)

## Related Category
[Dynamic Application Security Testing (DAST)](https://www.g2.com/categories/dynamic-application-security-testing-dast)

## Related discussions
- [How well does Trello scale into a larger team?](https://www.g2.com/discussions/1-how-well-does-trello-scale-into-a-larger-team)
  - Posted at: over 13 years ago
  - Comments: 6
- [Can we please add a new section](https://www.g2.com/discussions/2-can-we-please-add-a-new-section)
  - Posted at: over 13 years ago
  - Comments: 0
- [Quantifiable benefits from implementing your CRM](https://www.g2.com/discussions/quantifiable-benefits-from-implementing-your-crm)
  - Posted at: over 13 years ago
  - Comments: 4


