Vulnerabilities / Threats //

Advanced Threats

4/8/2014
01:10 PM
Nick Selby
Nick Selby
Commentary
Connect Directly
Twitter
LinkedIn
Google+
Facebook
Twitter
LinkedIn
RSS
E-Mail
50%
50%

One Year Later: The APT1 Report

One of the most positive impacts of APT1 is the undeniable rise in the stature of the threat intelligence industry. "Threat Intelligence" is the SIEM, the NAC of 2014.

In February 2013, Mandiant released a 74-page report, APT1, that told the story of a professional cyber-espionage group based in China and probably funded by the Chinese government. At this year's RSA Security Conference in February, I participated in a panel discussion entitled, "One Year Later: Lessons and Unintended Consequences of the APT1 Report."

The APT1 report included more than 3,000 APT1 indicators -- domain names, IP addresses, X.509 encryption certificates, and MD5 hashes of malware. It made headlines around the world in such mainstream publications as The Wall St Journal and The New York Times. And it was controversial. Detractors within the information security community accused Mandiant of exploiting fear, uncertainty, and doubt; of blowing operational security by revealing specific signatures of tools and methods used by the attackers; and of capitalizing on the woes of its clients for publicity gain.

A couple of months after the report came out, I wrote that it made our industry stronger by encouraging -- if not forcing -- information sharing; that the cost to researchers and investigators with active cases was low, because the data was already known by the people within our community who needed it; and that it added details that allowed an exponentially larger group of defenders to leverage the intelligence for defensive purposes. And I also said that the report was a piece of brilliant marketing.

Now that a year has passed, Gal Shpantzer, John Prisco, Martin McKeay, Lance James, and I discussed what we thought. Here are my views.

First, it's interesting to see so many in an industry that complains bitterly about FUD complain bitterly about fact. The people who gripe about APT1 still do so on the grounds that it blew operational security by discussing how our enemies work. I continue to reject this argument wholesale on the grounds that the good done for the community as a whole, and the information security industry in particular, far outweighed the few investigations that may have suffered. (I still doubt many did.) I have long felt that effectiveness in information security is the ability to detect, scope, and contain issues. Specific, usable threat intelligence like APT1 is crucial to enhancing that ability. That far outweighs any concerns about whether an individual investigation may have been compromised.

One of the undeniable trends that was helped by the release and publicity surrounding the APT1 report is the rise in the threat intelligence industry -- as a concentration, as a practice, and as a product area. The expo floor at RSA 2014 showed that "Threat Intelligence" is the SIEM, the NAC of 2014. That is an important accomplishment; it's providing economic opportunity to entrepreneurs while making some in the industry more effective. That's because the job of information security -- the job of well-leveraged threat intelligence -- is:

  • To prevent losses as best you can
  • To learn about and understand the scope of any security incident as early as possible
  • To move to contain it as quickly and efficiently as possible

Then it's to start the cycle again.

The idea that you're going to do this on your own is as dated as challenging the guy who attacked your network to a duel -- with sabers. Give executives the context and facts about the business impact of security issues, and most of the time they will make the decision that is most efficient. I trust the money. The money has ways of deciding what is best for making more money -- most of the time. That is not, of course, universal.

My favorite CEO quote of all time was something like "Oh, well, the criminals already have all our IP, so why should I spend the money to fix everything now?" Those kinds of executives exist, and it's galling to admit it, but shareholders actually reward them in the short run. By giving these kinds of people more information about why this is not a sustainable strategy, we increase the opportunities for them to make better decisions.

Nick Selby is co-founder and Chief Executive Officer of StreetCred Software Inc., a Texas-based company that provides law enforcement agencies with software that helps them locate and capture fugitives. Nick speaks and writes regularly on issues of information security, ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
nselby
100%
0%
nselby,
User Rank: Author
4/9/2014 | 5:23:21 AM
A clarification
My comment about "fact" and "FUD" has alarmed some: by it, I did not mean to provide a blanket endorsement of the entire APT1 report as "fact" - there is still some controversy over methods and conclusions. I meant rather to refer to the listing of the signatures included in the report. It has faded now, but at the beginning the biggest controversy was over whether Mandiant should have released those signatures at all. It was the release of the signatures I was referring to as fact and not FUD. I apologize for not being clear.
RyanSepe
100%
0%
RyanSepe,
User Rank: Ninja
4/8/2014 | 2:41:23 PM
APT1
Great submission. I agree with you on many of the statements you made. I do believe that delineating the threat landscape of adversaries is important in pushing that these are very real and dangerous situations. I do think APT1 could have done this in a more general sense instead of calling out individual specifics but by the same token specifics hold much more gravity than generalizations. To that end whatever could have been foiled on the security side was most likely trumped by the amount of good APT1 performed. The reward of releasing this outweighed the risk and hopefully that was Mandiants advocator. 
6 Ways Greed Has a Negative Effect on Cybersecurity
Joshua Goldfarb, Co-founder & Chief Product Officer, IDRRA ,  6/11/2018
Weaponizing IPv6 to Bypass IPv4 Security
John Anderson, Principal Security Consultant, Trustwave Spiderlabs,  6/12/2018
'Shift Left' & the Connected Car
Rohit Sethi, COO of Security Compass,  6/12/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
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-2018-12026
PUBLISHED: 2018-06-17
During the spawning of a malicious Passenger-managed application, SpawningKit in Phusion Passenger 5.3.x before 5.3.2 allows such applications to replace key files or directories in the spawning communication directory with symlinks. This then could result in arbitrary reads and writes, which in tur...
CVE-2018-12027
PUBLISHED: 2018-06-17
An Insecure Permissions vulnerability in SpawningKit in Phusion Passenger 5.3.x before 5.3.2 causes information disclosure in the following situation: given a Passenger-spawned application process that reports that it listens on a certain Unix domain socket, if any of the parent directories of said ...
CVE-2018-12028
PUBLISHED: 2018-06-17
An Incorrect Access Control vulnerability in SpawningKit in Phusion Passenger 5.3.x before 5.3.2 allows a Passenger-managed malicious application, upon spawning a child process, to report an arbitrary different PID back to Passenger's process manager. If the malicious application then generates an e...
CVE-2018-12029
PUBLISHED: 2018-06-17
A race condition in the nginx module in Phusion Passenger 3.x through 5.x before 5.3.2 allows local escalation of privileges when a non-standard passenger_instance_registry_dir with insufficiently strict permissions is configured. Replacing a file with a symlink after the file was created, but befor...
CVE-2018-12071
PUBLISHED: 2018-06-17
A Session Fixation issue exists in CodeIgniter before 3.1.9 because session.use_strict_mode in the Session Library was mishandled.