Analytics // Threat Intelligence
5/9/2013
03:55 AM
Tim Wilson
Tim Wilson
Commentary
Connect Directly
RSS
E-Mail
50%
50%

Five Questions To Ask When Choosing A Threat Intelligence Service

Threat intelligence services are becoming an essential weapon in the enterprise security arsenal. Do you know how to choose one?

Today's emerging threat intelligence services have the potential to change the way enterprises measure security risk and prepare their defenses for the next wave of attacks. If you subscribe to the Art of War's mantra, "know your enemy," threat intelligence is a key weapon in any IT security arsenal.

As they hit the market, however, it's becoming painfully clear that there is a huge disparity between the offerings that vendors are calling "threat intelligence service." Some of them are single-source RSS feeds, not too much different than what you might get from CERT (or even Dark Reading). Others are in-depth analytical services that can not only report and analyze the threats, but also tell you how they might affect your specific IT environment.

Dark Reading filed a report on how to choose threat intelligence tools last year, but at that point, a lot of these services were still in their formative stages. So recently I spoke to Lance James, director of threat intelligence services at security vendor Vigilant, and asked him for some thoughts on what questions security professionals should ask of prospective service providers. I should note that James, like most threat intelligence experts, recommends that enterprises should use multiple services, rather than just one. But if your organization is not made of money, you may have to be selective. Here are some questions that may be helpful in researching and choosing a threat intelligence service.

1. How many sources does the threat intelligence service pull from?
Some services are a single feed from a specific vendor's research arm, or even a white-labeled feed from another company. Other threat intelligence services collect and correlate data from dozens of different sources, giving a more comprehensive view of the threats.

"That's not to say that all the data has to be confirmed by multiple sources," James notes. "Sometimes a single anomaly from a single source is your first indication of a zero-day attack."

2. How frequently is the threat intelligence updated?
Different threat intelligence services approach their reporting with different philosophies. Some send out data constantly, offering just the basics on what they are seeing. Others take time to analyze the data and correlate it before they publish it. Timing may be important to some providers and not to others.

3. How are the threats evaluated?
Some threat intelligence services simply send out the data they collect, without ranking or evaluating it. Others offer a simple ranking, similar to the "critical" and "important" rankings used to measure new vulnerabilities.

In some cases, the threats may be given a specific score, using a system that ranks criteria such as potential damage and likelihood of infection. Some services correlate this data from many different sources and come up with an overall ranking.

4. How is the data formatted?
Particularly in cases where the threat intelligence comes from multiple sources, it can be extremely difficult to interpret and manage. Different sources have different ways of measuring and interpreting threat data, and getting a feed from all of those sources can result in a jumble of information that isn't much more helpful than no data at all.

A useful threat intelligence service will provide a way to normalize the threat information and present it in a way that can be reported consistently over a particular time period and plugged into reports that the enterprise already does.

5. Can the threat data be correlated with information that the enterprise already has about its security posture?
One of the great promises of threat intelligence is that it might be tailored so that it doesn't just give general threat information, but also provides insight as to whether a particular threat might affect a specific organization. Correlating threat data with information about the current state of the enterprise defenses allows an organization to come up with a real assessment of risk.

In many cases, however, the threat data you receive from an intelligence service does not reflect the specific systems your organization has, or the specific data it's trying to protect. A sophisticated attack against Unix devices might be ranked highly on the threat meter, but it may be moot if your enterprise is an all-Windows shop.

Over time, many threat intelligence services are tying into security information and event management (SIEM) systems that collect and correlate enterprise security posture data. The combination of current threat data and up-to-the-minute security posture information may eventually make it easier for enterprises to make defensive decisions that fit their specific situation, and to more accurately assess the risks they face from a particular threat. 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
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-3352
Published: 2014-08-30
Cisco Intelligent Automation for Cloud (aka Cisco Cloud Portal) 2008.3_SP9 and earlier does not properly consider whether a session is a problematic NULL session, which allows remote attackers to obtain sensitive information via crafted packets, related to an "iFrame vulnerability," aka Bug ID CSCuh...

CVE-2014-3908
Published: 2014-08-30
The Amazon.com Kindle application before 4.5.0 for Android does not verify X.509 certificates from SSL servers, which allows man-in-the-middle attackers to spoof servers and obtain sensitive information via a crafted certificate.

CVE-2010-5110
Published: 2014-08-29
DCTStream.cc in Poppler before 0.13.3 allows remote attackers to cause a denial of service (crash) via a crafted PDF file.

CVE-2012-1503
Published: 2014-08-29
Cross-site scripting (XSS) vulnerability in Six Apart (formerly Six Apart KK) Movable Type (MT) Pro 5.13 allows remote attackers to inject arbitrary web script or HTML via the comment section.

CVE-2013-5467
Published: 2014-08-29
Monitoring Agent for UNIX Logs 6.2.0 through FP03, 6.2.1 through FP04, 6.2.2 through FP09, and 6.2.3 through FP04 and Monitoring Server (ms) and Shared Libraries (ax) 6.2.0 through FP03, 6.2.1 through FP04, 6.2.2 through FP08, 6.2.3 through FP01, and 6.3.0 through FP01 in IBM Tivoli Monitoring (ITM)...

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
This episode of Dark Reading Radio looks at infosec security from the big enterprise POV with interviews featuring Ron Plesco, Cyber Investigations, Intelligence & Analytics at KPMG; and Chris Inglis & Chris Bell of Securonix.