Analytics // Threat Intelligence
6/25/2013
09:18 AM
Tim Wilson
Tim Wilson
Commentary
Connect Directly
RSS
E-Mail
50%
50%
Repost This

CrowdStrike Turns Security Fight Toward Attacker

CrowdStrike Falcon platform is first to focus on the source of the attack, rather than stopping malware

In medicine, there are two types of treatment: those that treat the symptoms and those that cure the disease. Many doctors -- and most pharmaceutical companies -- devote the majority of their time toward managing and relieving symptoms, rather than stopping a disease at its source.

Enterprise security professionals -- and most security vendors -- are in this same mode today. We focus a great deal of attention on technical analysis of malware and security events, but precious little time asking questions about who the attackers are or why they are targeting us. As a result, enterprises have built defenses that are somewhat effective in preventing the symptoms of an attack -- but the attackers themselves work in a relatively safe environment where it is unlikely they will be identified and even less likely they will suffer any consequences of their actions.

A week ago, I had a chance to meet with George Kurtz, co-founder and CEO of CrowdStrike, about the rollout of Falcon, the company's new platform for identifying and responding to the sources of targeted attacks. Falcon is the realization of CrowdStrike's concept of "Active Defense," which involves not only identifying the malware, but identifying its source and then taking steps to make the attacker's life more difficult. CrowdStrike calls this "raising the adversary's costs" -- the company does not use terms such as "strike back" or "hack back," which sometimes involve tactics that cause enterprises to get into legal problems. CrowdStrike's defenses are designed to frustrate attackers within legal limits.

CrowdStrike has been talking about Active Defense for more than 18 months now, but last week's announcements were the first real chance for the industry to see how this concept would be manifested in a product. In a nutshell, Falcon is a cloud service that correlates intelligence and security events in real-time from a global network of agent applications -- CrowdStrike calls them "sensors" -- that are deployed to endpoints and devices. By storing and analyzing a vast amount of event data gathered from all of these sensors, CrowdStrike has created a massive intelligence repository that is constantly mined, and advanced analytics are used to reveal threat intelligence insights that may escape currently available anti-malware and threat intelligence products and services.

In the future, CrowdStrike plans to instrument the event data so that it can be shared, enabling enterprises to share information on new attacks and respond more quickly to them, Kurtz says.

Running on top of the Falcon platform are two applications: CrowdStrike Threat Protect and CrowdStrike Adversary Intelligence. Threat Protect uses the CrowdStrike sensors to identify the adversary's mode of operation and create a profile that can be matched up with known attacks and attackers. Instead of focusing on only the malware itself, Threat Protect identifies mission objectives of the adversary leveraging the Kill Chain model and provides real-time detection by focusing on what the attacker is doing, such as reconnaissance, exploitation, privilege escalation, lateral movement, and exfiltration. It also records this activity with CrowdStrike's Activity Flight Recorder (AFR) technology so that the attacks can be analyzed at a later date.

Adversary Intelligence Intelligence is a Web-based intelligence subscription service that provides strategic analysis and customized views of advanced attacker activity. CrowdStrike says it can provide an extremely granular view into specific adversary campaigns and use that data to proactively defend against future attacks.

Just how effective the Falcon platform and applications will be remains to be seen. CrowdStrike is approaching the malware problem from an entirely new direction, and at this point, there's no way to predict what the bad guys' reaction will be. But the fact that a company is focusing on the source of the problem -- the attacker -- rather than simply treating the malware seems like a step in the right direction. Finding a cure usually starts with asking the right questions and coming up with a plan to fight the infection at its source, rather than just treating the symptoms. Tim Wilson is Editor in Chief and co-founder of Dark Reading.com, UBM Tech's online community for information security professionals. He is responsible for managing the site, assigning and editing content, and writing breaking news stories. Wilson has been recognized as one ... View Full Bio

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2012-0360
Published: 2014-04-23
Memory leak in Cisco IOS before 15.1(1)SY, when IKEv2 debugging is enabled, allows remote attackers to cause a denial of service (memory consumption) via crafted packets, aka Bug ID CSCtn22376.

CVE-2012-1317
Published: 2014-04-23
The multicast implementation in Cisco IOS before 15.1(1)SY allows remote attackers to cause a denial of service (Route Processor crash) by sending packets at a high rate, aka Bug ID CSCts37717.

CVE-2012-1366
Published: 2014-04-23
Cisco IOS before 15.1(1)SY on ASR 1000 devices, when Multicast Listener Discovery (MLD) tracking is enabled for IPv6, allows remote attackers to cause a denial of service (device reload) via crafted MLD packets, aka Bug ID CSCtz28544.

CVE-2012-3062
Published: 2014-04-23
Cisco IOS before 15.1(1)SY, when Multicast Listener Discovery (MLD) snooping is enabled, allows remote attackers to cause a denial of service (CPU consumption or device crash) via MLD packets on a network that contains many IPv6 hosts, aka Bug ID CSCtr88193.

CVE-2012-3918
Published: 2014-04-23
Cisco IOS before 15.3(1)T on Cisco 2900 devices, when a VWIC2-2MFT-T1/E1 card is configured for TDM/HDLC mode, allows remote attackers to cause a denial of service (serial-interface outage) via certain Frame Relay traffic, aka Bug ID CSCub13317.

Best of the Web