How do you handle security alert fatigue in your dev team?

Hey Product Hunt community

While building DevAIOpsHub, the #1 problem I kept hearing from engineering teams was this:

We have a security scanner. We ignore it.

Not because they don't care about security — but because it fires 400 alerts and nobody has time to figure out which 3 actually matter. So the whole queue gets deprioritized indefinitely.

This is what we're trying to solve with AI-powered SAST/DAST — ranking findings by real exploitability, not just pattern matches, and generating the fix so developers can act immediately.

Curious how other teams deal with this:

→ Do you have a security scanner in your CI/CD pipeline?

→ What % of alerts do you actually act on?

→ What would make you actually fix security issues faster?

Would love honest answers — even if it's "we just ignore everything below Critical." That feedback directly shapes what we build next.