Horizon3 says old vulnerability habits still undermine CTEM
Original title: Why Old Vulnerability Management Habits Keep Rising from the Grave
Customer retests cut demonstrated compromise to zero while dozens of minor findings remained.
Horizon3 argues that severity scores, closed tickets, and smaller backlogs still drive vulnerability programs even after Continuous Threat Exposure Management is adopted. In three unnamed customer examples, NodeZero linked an exposed SSH-key test server to possible lateral movement, and later same-scope retests showed prior compromise outcomes were no longer achievable. The post says remaining findings still need tracking and that verification should continue as environments change.
- An equipment rental firm exposed SSH keys through a test PHP server.
- NodeZero reported that exposure roughly eight hours after it was introduced.
- An investment firm's retest dropped demonstrated impacts from 251 to zero.
- A healthcare provider's AWS retest left two low-severity weaknesses.
- Vendors
- Horizon3.ai
- Products
- NodeZero
From the original article
5 min read at horizon3.ai
Three customer stories show how to keep severity-only priorities and closed-ticket counts from undermining your CTEM program by tying findings to attack paths and verifying fixes.
By Stephen Gates · horizon3.ai
A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.