Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Perimeter

7/25/2013
06:14 AM
50%
50%

Firms Far From Taming The Tower Of APT Babel

Threat intelligence firms continue to have individual lexicons for advanced persistent threats, making information sharing more difficult

Companies looking to learn more about the attackers who are targeting their systems will likely have to translate between reports from different incident-response and security firms.

While early efforts are under way to allow threat-intelligence firms to better exchange information on adversaries and their tools, security companies each have its own naming scheme, making identifying common threats more difficult. Take the Comment Crew, for example. The espionage group, which targets intellectual property in nearly a dozen industry sectors and is thought to be connected to an intelligence component of the People's Liberation Army, is also known as Comment Panda by security startup CrowdStrike and APT-1 by incident-response firm Mandiant. Managed security service provider Dell Secureworks puts the group into a broad bucket known as the Shanghai Group, based on its infrastructure's location.

"Different companies are approaching the same threats from different angles," says Joe Stewart, director of malware research at Dell Secureworks. "I focus on the malware and the IP infrastructure used by the attackers, whereas a response company sees different tools, and that leads them to a different naming scheme."

Like the proverbial blind men describing the elephant, each security firm collects intelligence on specific aspects of targeted attacks, and so tends to see different parts of the overall threat. The result is that different companies tend to group attacks into categories that do not appear to match.

CrowdStrike, for example, uses a cryptonym system, coming up with code names for the actors based on an umbrella term for the type of actor: Panda for China, Kitten for Iran, and Spider for certain criminal groups, for example. The company then adds a second identifier onto the more general name. Anchor Panda is the designation for a group thought to be connected to the Chinese PLA navy.

Mandiant, on the other hand, started with a single designation, APT1, and expanded its lexicon, adding APT2 and APT3 as new espionage groups were discovered. The company has approximately two to three dozen groups it currently tracks.

The problems are apparent when comparing names for another espionage group, which favors a tactic of dynamically calculating the port used for command-and-control communications. It is known as Numbered Panda by CrowdStrike, APT-12 by Mandiant, and by a variety of other common names, such as DynCalc, Ixeshe, and JoyRAT by other security firms.

[Researcher uncovers hundreds of different custom malware families used by cyberspies -- and discovers an Asian security company conducting cyberespionage. See Scope Of APTs More Widespread Than Thought.]

The problem makes it more difficult for threat-intelligence firms to share information with each other about threats, says Adam Meyers, vice president of intelligence for CrowdStrike.

"We've seen a problem in that there is no common lexicon for how we describe targeted attacks," Meyers says. "We are quickly turning into the antivirus industry."

Antivirus companies are well-known for independently choosing names to describe the same malicious program, a problem that has often caused confusion among consumers. In 2005, the MITRE Corp. created an initiative to find common names for malware, but closed down the project in late 2006. Instead, the government contractor began developing a common language to describe malware characteristics, known as the Malware Attribute Enumeration and Characterization (MAEC).

Researchers at the threat-intelligence firms have started informal discussions on similar efforts for describing and comparing attributes of current threats. The companies hope that finding a common lexicon, or finding ways to translate their lexicons, can result in the better identification of threats.

"We think that getting the industry as a whole to share some of this intelligence and to communicate with the same lexicon is going to allow us to be more effective in helping our customers," CrowdStrike's Meyers says.

Yet the companies still need to hash out many of the basic details, such as differentiating the attack campaigns from the attack groups, and determining how much of their proprietary information will be revealed. Mandiant, for example, has focused on releasing indicators of compromise -- specific clues that can help companies identify whether a certain group is in their network. In its APT-1 report released in February, the company released a large number of indicators of compromise that can identify if the group has attacked a network.

A significant problem in sharing the information on threats is that the evidence is tied closely to the way a security firm conducts its investigation, says Aaron Cherrington, a member of the intel team at Mandiant.

"It is one of those things where what you actually observe from your perspective as a security company really defines how you create your groups," he says. "And what information are you collecting allows you to make more of those links between attacks and the attacker."

In most cases, that information is proprietary and sensitive, which makes sharing the information that much more difficult, he says.

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. Veteran technology journalist of more than 20 years. Former research engineer. Written for more than two dozen publications, including CNET News.com, Dark Reading, MIT's Technology Review, Popular Science, and Wired News. Five awards for journalism, including Best Deadline ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
News
Inside the Ransomware Campaigns Targeting Exchange Servers
Kelly Sheridan, Staff Editor, Dark Reading,  4/2/2021
Commentary
Beyond MITRE ATT&CK: The Case for a New Cyber Kill Chain
Rik Turner, Principal Analyst, Infrastructure Solutions, Omdia,  3/30/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2015-20001
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.2.0, BinaryHeap is not panic-safe. The binary heap is left in an inconsistent state when the comparison of generic elements inside sift_up or sift_down_range panics. This bug leads to a drop of zeroed memory as an arbitrary type, which can result in a memory ...
CVE-2020-36317
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, String::retain() function has a panic safety problem. It allows creation of a non-UTF-8 Rust string when the provided closure panics. This bug could result in a memory safety violation when other string APIs assume that UTF-8 encoding is used on the sam...
CVE-2020-36318
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, VecDeque::make_contiguous has a bug that pops the same element more than once under certain condition. This bug could result in a use-after-free or double free.
CVE-2021-28875
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.50.0, read_to_end() does not validate the return value from Read in an unsafe context. This bug could lead to a buffer overflow.
CVE-2021-28876
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.52.0, the Zip implementation has a panic safety issue. It calls __iterator_get_unchecked() more than once for the same index when the underlying iterator panics (in certain conditions). This bug could lead to a memory safety violation due to an unmet safety r...