The Command Gap: the Real Reason Your Program Feels Like Chaos.
When a security program feels like chaos, the instinct is to call it a technology problem and buy what is missing. Sometimes that is right. More often the gap is not in what the organization can see, but in whether anyone can stand above what it sees and decide. That is a command gap, and no new sensor closes it.
Two Different Gaps
| Question | Capability Gap | Command Gap |
|---|---|---|
| What is missing | The ability to see or stop a kind of attack | A place where everything seen becomes one decision |
| Where the delay sits | Detection | Triage, prioritization and translation to the business |
| Typical symptom | An attack the organization never noticed | An alert that was noticed, and not acted on in time |
| Who feels it first | The security team | The executive team and the board |
| What fixes it | A new capability | A layer that ranks, weighs and hands the decision to a person |
The Evidence That Most Programs Have the Second
Organizations are not short of tools. A Gartner survey of 162 large enterprises, conducted in 2024, found an average of 45 cybersecurity tools, in a market of more than 3,000 vendors. The 2025 study by the IBM Institute for Business Value and Palo Alto Networks put the average at 83 solutions from 29 vendors, and found that 52 percent of executives say this fragmentation limits their ability to deal with threats.
The gap also shows in who is in the room. PwC's 2025 Global Digital Trust Insights survey of more than 4,000 executives found that fewer than half say their CISOs are involved to a large extent in strategic planning, board reporting or overseeing technology deployments, and that only 21 percent say their security teams usually allocate the cyber budget to the organization's top risks. A program can see a great deal and still not be steering by it.
Where the Time Goes
Every significant event passes through four stages before anything changes. The command gap lives in the middle two.
| Stage | What Happens | What Slows It |
|---|---|---|
| Detect | A technology notices something | Missing coverage: a capability gap |
| Triage | Someone decides whether it matters | Volume, and signals that disagree across tools |
| Decide | Someone with authority chooses what to do | No link between the signal and the business process at stake |
| Act and explain | The response happens and is recorded | Evidence scattered across systems, rebuilt by hand |
What the Gap Costs
IBM's 2025 Cost of a Data Breach study found that the global average cost of a breach fell 9 percent to $4.44 million, and credits most of the decline to faster identification and containment. The single largest cost category was detection and escalation, at $1.47 million on average, followed by lost business at $1.38 million. Escalation is the heart of the command gap: the step between knowing and deciding. It is also where the most money is spent.
Why Mature Programs Still Have It
Mature programs have usually spent a decade closing capability gaps, one purchase at a time. Each purchase was rational. Together they produced more places where the truth is partly stored, and more work to assemble it. The more capable the program becomes, the more its leaders' time goes to gathering and reconciling rather than deciding. Maturity in capability can deepen the command gap unless something is built above it.
How to Tell Which Gap You Have
After any significant event, ask how long it took for a person with authority to know it mattered, decide what to do, and be able to explain the decision. If most of that time was spent discovering the event, the gap is capability. If most was spent sorting, escalating and translating, the gap is command.
- Could the program name the three business processes most exposed today, without assembling a report?
- When two tools disagree, is there one place that shows both and says which to trust?
- Can the board be answered from what the program already knows, or does every question start a project?
- Was last year's budget allocated to the top risks to the business, or by technology category?
Closing It in 90 Days
| Period | Focus | Result |
|---|---|---|
| Days 1 to 30 | Map the business processes that matter most, and connect the existing technologies to one view | One picture, tied to the business |
| Days 31 to 60 | Rank decisions by business impact, and name an owner for each accepted risk | A short list of decisions, each with an owner |
| Days 61 to 90 | Report to leadership from the same view, and measure time from signal to decision | A board answer that needs no assembly |
Conclusion
Closing a command gap does not mean buying more, or even consolidating. It means adding the layer the program never had: one place that sees every signal, ranks it against the business, weighs acting against waiting, and puts the decision in front of a person, with the evidence attached. In defense, that layer is called C4I. AQUILA C4I brings it to cybersecurity.
Sources
- Gartner, Top Cybersecurity Trends for 2025, March 3, 2025
- IBM Institute for Business Value and Palo Alto Networks, Capturing the Cybersecurity Dividend, 2025
- PwC, 2025 Global Digital Trust Insights, C-suite playbook
- PwC, 2025 Digital Trust Insights, budget allocation to top risks
- IBM, 2025 Cost of a Data Breach Report
- CyberScoop, on the cost categories in IBM's 2025 report
