Vulnerabilities / Threats
12/5/2012
04:27 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

Attack Intelligence-Sharing Goes 'Wire-Speed'

STIX standard aimed at eliminating manual process of converting intelligence into useful defense

When a company hit by a cyberattack shares some details of the attack with another firm, it typically gives them a call or shoots them an email with some intelligence on the malware or other fingerprints of the attack. It's then up to the recipient to manually translate that information into a format it can use to automatically protect itself from falling prey to that attack.

That gap of time between receiving the intell and converting it into something useful can make all the difference in deflecting or mitigating an attack. To wit, an industry effort is under way to create a standard, machine-readable language that organizations can use to efficiently incorporate the latest threat information into their security infrastructures, called Structured Threat Information eXpression, or STIX.

"STIX is not a program or policy. It's not a system or application. It's not code or heuristics: It's purely a language," says Sean Barnum, a principal in cybersecurity at Mitre Corp., which is spearheading the project. "It's a way of expressing and specifying cyberthreat information. You can then use it any way you want."

The goal is to help automate the process with a consistent language for speaking intell. "So I can share my detection for your prevention tomorrow, so you can block it," Barnum says. "There's no standard way of doing this today. It's amazing how much time is spent translating [attack and threat] information from different players."

STIX, which is currently available as a 1.0 draft release, would make intell-sharing -- and reaction to new threats --"wire-speed," its backers say. The initial version uses XML Schema and is made up of eight core "constructs," including indicator, incident, exploit target, campaign, and threat actor.

And the project has some heavy-duty players behind it: The U.S. Department of Homeland Security (DHS), U.S. Computer Emergency Readiness Team (US-CERT), National Institute of Standards and Technology (NIST), Financial Services Information Sharing and Analysis Center (FS-ISAC), Depository Trust & Clearing Corporation (DTCC), General Dynamics, Lockheed Martin, NATO, and World Bank are among the contributors.

[Targeted attacks out of China against Google and other U.S. firms forced some chief information security officers to reach out to their counterparts in other organizations and share attack, forensics information. See 'Operation Aurora' Changing The Role Of The CISO.]

Michael "Aharon" Chernin, security automation program manager for corporate information security at DTCC and a contributor to STIX, says the goal of STIX is making intelligence machine-readable in a standard way. "It's not that the intell [today] being shared is bad -- it's that the intell isn't structured, so that when you receive it you have to manually act upon it.

"If I know it's going to be structured, I can develop automated tools to use it. STIX makes it so when you share intell, it's always in machine-readable format," Chernin says. And that way, organizations can respond to threats "at wire speed" as well, he says.

Chernin, whose organization is a participant in the FS-ISAC, describes STIX as the intelligence-sharing language architecture, while a companion standard from DHS, Trusted Automated eXchange of Indicator Information (TAXII), is the protocol for transporting the information. FS-ISAC plans to adopt both STIX and TAXII, he says.

DTCC has been a major contributor to STIX. "DTCC has been involved in security standards for a few years, even before STIX and TAXI. We are one of the top contributors to the OVAL [Open Vulnerability Assessment Language] repository," Chernin says.

Sharing malicious IP addresses, file hashes, URLs, and email addresses used in attacks has been going on for some time. It has just been a mostly manual process, he says. The goal is to make it more costly for the attacker with better defenses that force him to spend more money and time, he says.

RSA, the security division of EMC, had previously offered up its own XML-based language as a solution to the intell-sharing problem. The language is based on its NetWitness framework's technology for taking data from different sources, massaging it, and converting it into machine-readable format, says Eddie Schwartz, CSO at RSA. RSA demonstrated a prototype of the technology at the RSA Conference last year.

"You're going to see more and more of this, with companies like ours looking at different ways to use automated threat intelligence," he says. It's too soon to tell whether STIX will be the language, though, he says.

"It's pointing to the ongoing need for development of a format," he says. Schwartz says STIX and TAXII present intelligence information in a digestible way that can be easily integrated into their existing infrastructures.

The hope is that vendors, too, ultimately will adopt STIX support into their security products. "What we're trying to do is drive demand from the consumer and what the consumer needs, versus having solutions come from vendors," DTCC's Chernin says.

So far, aside from FS-ISAC, the DHS, US-CERT, Mitre, and Japan's Information-technology Promotion Agency have publicly committed to adopting STIX. According to STIX's developers, various U.S. and international organizations are considering adopting the standard, as well.

"In a perfect world, everyone would adopt STIX," Chernin says. "It would be a huge win if just the financial sector adopted it."

Have a comment on this story? Please click "Add Your Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message.

Kelly Jackson Higgins is Executive Editor at DarkReading.com. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading, September 16, 2014
Malicious software is morphing to be more targeted, stealthy, and destructive. Are you prepared to stop it?
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-5316
Published: 2014-09-21
Cross-site scripting (XSS) vulnerability in Dotclear before 2.6.4 allows remote attackers to inject arbitrary web script or HTML via a crafted page.

CVE-2014-5320
Published: 2014-09-21
The Bump application for Android does not properly handle implicit intents, which allows attackers to obtain sensitive owner-name information via a crafted application.

CVE-2014-5321
Published: 2014-09-21
FileMaker Pro before 13 and Pro Advanced before 13 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. NOTE: this vulnerability exists because of an incorrect fix for CVE-2013-2319...

CVE-2014-5322
Published: 2014-09-21
Cross-site scripting (XSS) vulnerability in the Instant Web Publish function in FileMaker Pro before 13 and Pro Advanced before 13 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors. NOTE: this vulnerability exists because of an incorrect fix for CVE-2013-3640.

CVE-2014-6602
Published: 2014-09-21
Microsoft Asha OS on the Microsoft Mobile Nokia Asha 501 phone 14.0.4 allows physically proximate attackers to bypass the lock-screen protection mechanism, and read or modify contact information or dial arbitrary telephone numbers, by tapping the SOS Option and then tapping the Green Call Option.

Best of the Web
Dark Reading Radio