Organizations today are battling three compounding challenges: complex cyberattacks that shift as they unfold, complicated technology environments and a fast-growing skills gap. As a result, technologies and processes that enable a dynamic, fast and orchestrated response are becoming vital.

IBM Resilient has many enterprise deployments around the world spanning just about every industry. One trend we’ve been expecting and are now starting to see is that more advanced companies are working hard to orchestrate their incident response (IR) and improve their general security operations. The obvious goal is to accelerate response processes and get ahead of attackers.

Earlier this week, we announced our latest advanced orchestration capabilities.

OODA Loops in Security

When we designed Resilient, one of our steering principles was adopted from the military, where it has been battle-tested — literally. That concept is called OODA loops. If you Google the term, you’ll see that Bruce Schneier, our chief technology officer (CTO) at IBM Resilient, has long discussed the applicability of OODA loops to incident response. As IR technology matures, orchestration brings the concept into real-world application.

OODA loops — which stands for observe, orient, decide and act — is a combat method originally developed by a U.S. Air Force colonel to help fighter pilots be more successful in dogfights. It essentially describes all the steps a pilot needs to execute to defeat his or her adversary in the form of continuous loops: observing their environment, orienting that data for context with other information at their disposal, deciding what to do and, finally, acting accordingly. If the pilot could do this faster than the enemy, or slow down the enemy’s ability to execute their loops, he or she would gain an enormous advantage. Pilots were trained to execute this successfully and planes, including the F16, were redesigned to support them. The results were dramatic.

The OODA technique has become a standard combat method in most of the military and is now finding its way into commerce. It was an appropriate way for us to look at system design when we created Resilient. Incident response is becoming more like real-time combat with cybercriminals, and security professionals should view incident response orchestration as a series of OODA loops that need to be executed as fast as possible.

Orchestration in Action

When implemented effectively, orchestration can deliver dramatic time savings. Here’s an example: One global company we work with faced challenges with the speed of its incident response at scale, which was too manual, slow and disjointed. Many parts of its processes, particularly in the orient stage, took analysts up to 10 minutes each to complete. By the company’s calculations, one particular and common type of incident took more than 80 minutes on average to close out.

To accelerate its response, the company began the process of orchestration. Based on Resilient as the security orchestration, automation, and response (SOAR) platform and some straightforward integrations, the organization now has a central hub to assign responsibilities, manage runbooks, coordinate tasks and automate appropriate steps. Analysts can complete certain tasks with the click of a button and fully automate triage and enrichment with a high level of fidelity. Responders get critical information faster and exactly when they need it. As a result, the average time to resolve that 80-minute incident plummeted to an impressive one minute.

Learn how IBM Resilient’s latest features can help orchestrate your incident response and request more information or a live demo today.

More from Incident Response

5 Golden Rules of Threat Hunting

When a breach is uncovered, the operational cadence includes threat detection, quarantine and termination. While all stages can occur within the first hour of discovery, in some cases, that's already too late.Security operations center (SOC) teams monitor and hunt new threats continuously. To ward off the most advanced threats, security teams proactively hunt for ones that evade the dashboards of their security solutions.However, advanced threat actors have learned to blend in with their target's environment, remaining unnoticed for prolonged periods. Based…

Everyone Wants to Build a Cyber Range: Should You?

In the last few years, IBM X-Force has seen an unprecedented increase in requests to build cyber ranges. By cyber ranges, we mean facilities or online spaces that enable team training and exercises of cyberattack responses. Companies understand the need to drill their plans based on real-world conditions and using real tools, attacks and procedures. What’s driving this increased demand? The increase in remote and hybrid work models emerging from the COVID-19 pandemic has elevated the priority to collaborate and…

People, Process and Technology: The Incident Response Trifecta

Let's say you are the CISO or IT security lead of your organization, and your incident response program needs an uplift. After making a compelling business case to management for investment, your budget has been approved and expanded. With your newfound wealth, you focus on acquiring technology that will improve your monitoring, detection and analysis of data traffic. Has the incident program really improved by the technology acquisition, or is the uplift merely cosmetic? If no other changes have been…

Self-Checkout This Discord C2

This post was made possible through the contributions of James Kainth, Joseph Lozowski, and Philip Pedersen. In November 2022, during an incident investigation involving a self-checkout point-of-sale (POS) system in Europe, IBM Security X-Force identified a novel technique employed by an attacker to introduce a command and control (C2) channel built upon Discord channel messages. Discord is a chat, voice, and video service enabling users to join and create communities associated with their interests. While Discord and its related software…