The Critical Vulnerability Was a Test Database. That's the Whole Triage Problem.
The New Stack, Thursday, September 17th, 2026
Scanners flag severity but cannot infer business impact, so triage without context wastes scarce engineering hours.
A researcher scanning a 300-person B2B company found an internet-exposed database with weak authentication, rated critical and an obvious first fix. It turned out to be a resettable test database used to screen job candidates, holding no client data at all.
The episode illustrates why severity scores alone cannot drive remediation order: scanners have no way to infer the real cost of a compromise.
Security programs now absorb identity events, firewall logs, endpoint alerts, vendor feeds and threat intelligence, producing far more analysis data than a few years ago, and every item looks urgent. The piece argues for adding business context to triage, increasingly via external partners, so finite engineering hours go to findings that actually matter.