Consolidation vs. Command: Why Fewer Tools Won't Fix Your Program.
Consolidating security vendors is sensible, and nearly every organization is doing it. It is also routinely mistaken for something it cannot deliver. Consolidation reduces how many products an organization operates. It does not change whether anyone is in command of the program those products serve.
The Scale of the Move
Gartner's 2024 survey of 162 large enterprises found an average of 45 cybersecurity tools, in a market Gartner describes as more than 3,000 vendors. A 2025 Gartner survey found that 62 percent of companies are actively consolidating suppliers, with another 36 percent planning to within three years. The trend is not new: in 2022, Gartner reported that 75 percent of organizations planned to consolidate security vendors, up from 29 percent in 2020.
Why Organizations Consolidate
Cost is rarely the main reason. In Gartner's 2022 research, more than half of security respondents said they were consolidating to improve the productivity of scarce security staff, the efficacy of the security stack, and visibility and reporting. Only 35 percent cited spending and procurement ease. Organizations consolidate because they are overwhelmed, and they hope fewer products will mean clearer decisions.
Two Axes, Not One
| Axis | What Moves You Along It | What It Changes |
|---|---|---|
| How many products you operate | Consolidation | Fewer consoles, contracts and renewals |
| Whether the program is commanded | A command layer | Faster decisions, ranked by business impact, with evidence |
An organization can consolidate aggressively and remain exactly where it was on the second axis. Merging ten consoles into three leaves the same questions unanswered: what is at risk now, which decision needs attention today, what acting costs against waiting, and how to explain it to the board. The reasons organizations give for consolidating are second-axis problems. Consolidation addresses the first axis.
What Consolidation Does and Does Not Deliver
| Outcome | Consolidation | Command |
|---|---|---|
| Lower license and management cost | Yes | Not its purpose |
| Fewer integrations to maintain | Yes | Not its purpose |
| One ranked view of risk to the business | Rarely | Yes |
| Decisions tied to cost and obligation | No | Yes |
| A board answer from what the program already knows | No | Yes |
The Risks of Consolidating Badly
Consolidation has its own failure modes. Vendors often grow by acquisition, and industry commentary notes that many platforms become loosely connected portfolios of products with a shared interface rather than genuinely integrated architecture. An organization that consolidates onto such a portfolio pays for integration it does not receive, and deepens its dependence on one vendor's roadmap.
| Risk | What It Looks Like | How to Avoid It |
|---|---|---|
| A portfolio posing as a platform | One login, separate data underneath | Ask to see one finding travel between two products, on live data |
| Losing the best specialist | A strong product replaced by a weaker bundled one | Keep the specialists that are best at their task |
| Lock-in | Data that cannot leave the platform | Require that findings can be exported and used elsewhere |
| A false sense of command | Fewer consoles mistaken for clearer decisions | Measure time from signal to decision before and after |
The Evidence That Integration Matters More Than Count
The 2025 study by the IBM Institute for Business Value and Palo Alto Networks, co-sponsored by a platform vendor and worth reading with that in mind, reports that organizations with consolidated estates detected incidents 72 days faster and contained them 84 days faster. The mechanism behind that result is not the smaller number of vendors. It is that signals reach a decision sooner. Gartner makes a related recommendation: consolidate and validate core security controls, and focus on architecture that makes data portable between them.
A Practical Order
- Consolidate where products overlap and the savings are clear.
- Keep the specialists where they are best, and make sure their data can leave them.
- Add one command layer above what remains, where every signal is ranked against the business and decided by a person.
- Measure the result in decision time, not in vendor count.
Conclusion
Consolidate if it reduces the load. Just do not confuse it with command. Consolidation that leaves findings in separate places has reduced cost. Integration that brings them to one decision has reduced risk. The command layer is what AQUILA C4I provides, above whatever an organization decides to keep.
Sources
- Gartner, Top Cybersecurity Trends for 2025, March 3, 2025
- The Hacker News, on Gartner's 2025 supplier consolidation survey and platform portfolios
- Cybersecurity Dive, on Gartner's 2022 vendor consolidation research
- CSO Online, on Gartner's 2022 consolidation survey
- IBM Institute for Business Value and Palo Alto Networks, Capturing the Cybersecurity Dividend, 2025
