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 incident response 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.