Stop Buying Security Tools. Start Discovering What You Actually Have.
- Martin Snyder

- May 13
- 3 min read
The security industry has a buying problem. The average security organization runs 70-plus distinct tools. The annual spend keeps going up. The number of products acquired keeps going up. The pain keeps going up. The breach rate, weirdly, doesn't really go down.
Maybe — and this is going to sound counterintuitive coming from a security vendor — the answer isn't another tool.
The pattern in the buying cycle
Watch how a typical security purchase happens. Some incident, somewhere, exposes a gap. A vendor shows up with a category answer to that gap. The category becomes a Gartner Magic Quadrant. Within 18 months, every CISO is being asked by the board why they don't have one. The purchase happens. The new tool gets onboarded. The team spends six months wiring it up. The dashboards turn green.
Then the next category emerges, and the cycle repeats.
What nobody asks during the cycle is the most basic question: do the tools we already own cover this gap if we just gave them the right inputs? Because the answer is usually yes.
Every tool you own is starving
Pick any tool in your security stack. Your SIEM. Your IGA. Your CSPM. Your DLP. Each one is doing exactly what it was built to do — on the systems it's been told about. The reason your SIEM doesn't catch shadow SaaS incidents isn't because the SIEM is bad. It's because the shadow SaaS logs aren't onboarded. The reason your IGA doesn't review access in unsanctioned tools isn't because the IGA is broken. It's because the unsanctioned tools aren't connected.
The tools are doing the work. They're starving for inputs.
The discovery layer makes everything you own better
This is the bit that the buying cycle skips. A discovery layer underneath your existing tools materially improves every tool you've already paid for. Your SIEM detects on a broader set of sources. Your IGA reviews access on a more complete population. Your CSPM has the cloud tenants it didn't know about. Your DLP can finally enforce policy on the apps where data is actually leaving.
The math here is usually favorable. A single discovery investment unlocks better outcomes from a half-dozen existing investments. The vendor of the discovery tool has every reason to want you to buy more tools afterward — but the immediate win is making the ones you already own actually work.
Discovery before governance is one version of the principle. SSPM vs DSPM and what security teams actually need is another angle on it. The point is the same — capability is plentiful, inventory is rare.
What this looks like in practice
Instead of buying the next-category tool, run a discovery scan against your environment. See what's there. Feed the new inventory into your existing IGA, your existing SIEM, your existing GRC. Watch the dashboards in those tools fill in. Notice that some of the gaps you were about to fill with new purchases were actually inventory problems all along. Use the budget you saved to do something more interesting.
The NIST Cybersecurity Framework 2.0 is unambiguous that asset inventory underpins every other function. CIS Controls v8 puts "Inventory and Control of Enterprise Assets" and "Inventory and Control of Software Assets" at the top of the list. The Cloud Security Alliance's SaaS governance work says you can't secure what you can't see. None of these are radical positions. They're consensus.
The vendor doing the consensus work in 2026 is, in our biased opinion, Waldo Security. We sit underneath the security stack you've already paid for and make the rest of it actually work.
Want to see the discovery layer in action? Demo us. Bring the spreadsheet of tools you already own. We'll point at the gaps the new purchases weren't going to fix.



Comments