Tool sprawl gets most of the attention. In many SOCs, though, the handoffs between people eat more analyst time than the number of tools does.
How much a handoff costs depends on what gets passed along. If the next person receives the timeline, the evidence and a note on what’s already been ruled out, they can pick up where the last one stopped. If they get a two-line ticket and a handful of IPs, they’re starting from zero.
The trouble is that in a fragmented incident response workflow, cases tend to move by tool ownership. Network data belongs to the network team, cloud logs to the cloud team, so the case ends up wherever the next piece of evidence happens to live. Who ought to make the call gets decided late, or not at all.
CIS Control 17[1], Incident Response Management, tackles this head-on. It asks organizations to name the people responsible for incident handling, define their roles, and document the process. Put simply, decide who owns which decision before the incident, not during it.
Skip that, and two costs creep in: