TL;DR: False positives in AppSec have left most findings unreviewed and many high-severity alerts untouched, according to Nullify. When findings stop looking credible, teams fix less and security debt builds faster.
Editorial analysis by NHI Mgmt Group, based on content published by Nullify: “Death by False Positives: How AppSec & ProdSec Lost The Developers”.
By the numbers:
- Over 2,000 open alerts were reviewed at one financial-services client, but less than 10% had been triaged.
- The same client had only ~15% of its highs and criticals opened by a human.
- Nullify says one limited deployment to ten repositories found 547 false positives against 105 true positives.
Key questions
Q: What happens when developers stop trusting AppSec findings?
A: They begin to triage by habit instead of by severity, which means real vulnerabilities can sit unreviewed while noise keeps arriving.
Q: What are the signs that a vulnerability program is creating too much noise to be effective?
A: A vulnerability program is probably generating too much noise when teams are flooded with red findings, developers ignore tickets, and important issues keep getting buried in the backlog.
Q: How should AppSec teams reduce false positives without losing vulnerability coverage?
A: Use contextual analysis that weighs reachability, data flow, and compensating controls before escalating findings.
Practitioner guidance
- Tighten triage precision before expanding scanner coverage Measure false-positive rates by tool, rule set, and repository so you can remove the worst sources of noise before asking engineers to absorb more findings.
- Track developer trust as an operational security metric Use triage acceptance, reopen rates, and ignored-high-severity counts to show whether findings are still being treated as credible inputs to remediation.
- Route only validated findings into engineering backlogs Separate validation from assignment so developers receive issues that have already been confirmed as real and paired with enough context to fix quickly.
Bottom line: Excessive false positives are not just a tooling nuisance, they weaken the credibility of the entire AppSec workflow.
Glossary terms: False Positive, Triage Fatigue, Security Debt, Validation Pipeline
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
False-positive fatigue is a governance failure, not just a tooling problem. When developers repeatedly see bad alerts, they stop treating the security queue as authoritative. That changes behaviour more than any policy memo can reverse, because trust is a control surface in its own right. For AppSec and ProdSec teams, the issue is not alert count but whether the programme still earns developer attention.
A few things that frame the scale:
- Only 44% of developers are reported to follow security best practices for secrets management, exposing a significant developer behaviour gap, according to the State of Secrets in AppSec.
A question worth separating out:
Q: Why do false positives create governance risk in application security?
A: False positives create governance risk because they train developers to distrust security output. When teams cannot distinguish exploitable issues from noise, they waste time on the wrong work and miss real risk. The result is weaker adoption, slower remediation, and a security programme that measures activity instead of exposure reduction.
👉 Read our full editorial: False positives are breaking AppSec trust with developers