Vulnerabilities / Threats

7/15/2015
10:30 AM
Rick Howard
Rick Howard
Commentary
Connect Directly
Twitter
LinkedIn
Google+
RSS
E-Mail vvv
100%
0%

The End Of Whac-A-Mole: From Incident Response To Strategic Intelligence

In the face of mounting cybercrime, hacktivism, and espionage, network defenders need to transform their tactical IR groups into full-scale cyber intelligence teams.

I am an old U.S. Army guy. In the early 2000s, I ran the Army’s Computer Emergency Response Team, the ACERT, and my job was to coordinate offensive and defensive operations across the Army. One of my main tasks back then was to respond to computer incidents.

We had teams of incident responders that would wait for an incident to happen, spend weeks trying to determine the exact location of the infected endpoint somewhere in the Army network, travel to said endpoint once the location was known, take the machine off the network, perform some rudimentary forensics on it (because that was all we knew back then), re-image the endpoint, put it back on the network, and wait for the next incident to happen. Even back then, I affectionately referred to that process as playing Whac-a-Mole with the adversary. But back then, Whac-a-Mole is what most network defenders were doing.

Fifteen years later, advanced network defenders have realized that playing Whac-a-Mole with the adversary is not sufficient. It is lacking in several key areas. Whac-a-Mole gives the network defender no intelligence about what these adversary groups were trying to accomplish, why they were trying to accomplish it, where they went once they compromised the endpoint, and whether or not they had the capacity to materially impact their business or organization. Playing Whac-a-Mole with the adversary back in the early 2000s was fine because we did not know any better. Today, the process seems quaint and is very tactical.

Since then, advanced network defender organizations have realized that they need to up their game. We all need to transform our tactical incident response teams into strategic intelligence teams. Here is what I mean.

Adversary groups are made up of people. They have motivations like crime, hacktivism, espionage, and warfare. Successful adversary groups design and execute campaign plans against a target, as opposed to making it up on the fly. In a way, they are similar to the network defenders in the world. Just like us, they do not have unlimited resources and, just like us, they are not superheroes. They put their pants on the same way we do.

Wanted: full-scale intelligence teams
The successful adversary group develops repeatable processes so that it does not have to re-invent the wheel every time it goes after a new victim. Those repeatable processes leave traces in the network. We call them “indicators of compromise” and we can track them. In my day, we assigned this work to the tactical incident responders, but it became clear early on that those groups did not have the skillset needed to track adversary groups with this kind of granularity. We still needed the incident responders to do what they do, but it was not sufficient to gain an understanding of what the adversary group was about in the aggregate. We needed full-scale intelligence teams.

In contrast to an incident response group, an intelligence team collects raw information about adversary groups, transforms that raw information into intelligence through analysis – something a leader can use to make a decision – and then disseminates that intelligence to the people in the organization who can use it. This is called the intelligence life cycle. The U.S. military started to build these new cyber intelligence teams in the early 2000s to track Chinese government-sponsored cyber espionage under a code name called Titan Rain.

The commercial world started to embrace the idea of intelligence teams when the Titan Rain adversary group started hitting the Defense Industrial Base (commercial companies that sell goods and services primarily to the U.S. government, like Raytheon, Lockheed Martin, Boeing and Northrop Grumman) in 2003. But the traditional commercial world –  companies that are not part of the Defense Industrial base (DIB) – really did not embrace the idea until 2010, when Google got hit by an advanced cyber espionage adversary group and publically called the government of China out as being the perpetrator of the attack.

Since then, advanced organizations in the non-DIB space have been slowly warming to the idea that they need strategic cyber intelligence teams in addition to their tactical incident response teams. Some groups have even combined the missions. I believe that if you don’t have an intelligence team in your organization – even if it is just a team of one person – you cannot hope to keep up with the advanced adversary.

The evolution has begun. Advanced organizations have already transformed their tactical incident response teams into strategic intelligence teams. Palo Alto Networks created their team, Unit 42, last year. You are going to have to do this eventually. I recommend that you start now.

Rick Howard is Chief Security Officer for Palo Alto Networks, where he is responsible for internal security of the company as well as developing the Threat Intelligence Team to support the next-generation security platform. He previously served as Chief Information Security ... View Full Bio
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Paladium
100%
0%
Paladium,
User Rank: Moderator
7/26/2015 | 8:57:20 PM
No staff for this...
I agree in principle with your idea.  However, over the past 14 years I have managed SecOps teams in Defense, Energy, and Finance companies and not once did we have the minimum number of staff resources necessary to do our basic jobs.  Based on that real life experience I see no way typical organizations will have the necessary staff to pull this off.  And Please Please Please do not say theres a 3rd party company that can help with that.  In the famous words of Merlin "Never again!!!"

Anyway, this lack of staffing contiunues to push more and more organizations in finding and implementing auto-blocking technologies and real time threat intelligence & monitoring systems like Splunk ES to compensate for the staff shortages.  So no, what you propose is a great idea but that's it.  Until organizations properly invest in the human capital needed in cybersecurity we will have no real choice but to continue to play whack-a-mole.
121 Pieces of Malware Flagged on NSA Employee's Home Computer
Kelly Jackson Higgins, Executive Editor at Dark Reading,  11/16/2017
Mobile Malware Incidents Hit 100% of Businesses
Dawn Kawamoto, Associate Editor, Dark Reading,  11/17/2017
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Managing Cyber-Risk
An online breach could have a huge impact on your organization. Here are some strategies for measuring and managing that risk.
Flash Poll
The State of Ransomware
The State of Ransomware
Ransomware has become one of the most prevalent new cybersecurity threats faced by today's enterprises. This new report from Dark Reading includes feedback from IT and IT security professionals about their organization's ransomware experiences, defense plans, and malware challenges. Find out what they had to say!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2017-0290
Published: 2017-05-09
NScript in mpengine in Microsoft Malware Protection Engine with Engine Version before 1.1.13704.0, as used in Windows Defender and other products, allows remote attackers to execute arbitrary code or cause a denial of service (type confusion and application crash) via crafted JavaScript code within ...

CVE-2016-10369
Published: 2017-05-08
unixsocket.c in lxterminal through 0.3.0 insecurely uses /tmp for a socket file, allowing a local user to cause a denial of service (preventing terminal launch), or possibly have other impact (bypassing terminal access control).

CVE-2016-8202
Published: 2017-05-08
A privilege escalation vulnerability in Brocade Fibre Channel SAN products running Brocade Fabric OS (FOS) releases earlier than v7.4.1d and v8.0.1b could allow an authenticated attacker to elevate the privileges of user accounts accessing the system via command line interface. With affected version...

CVE-2016-8209
Published: 2017-05-08
Improper checks for unusual or exceptional conditions in Brocade NetIron 05.8.00 and later releases up to and including 06.1.00, when the Management Module is continuously scanned on port 22, may allow attackers to cause a denial of service (crash and reload) of the management module.

CVE-2017-0890
Published: 2017-05-08
Nextcloud Server before 11.0.3 is vulnerable to an inadequate escaping leading to a XSS vulnerability in the search module. To be exploitable a user has to write or paste malicious content into the search dialogue.