11:19 AM

8 Lessons From Nortel's 10-Year Security Breach

Learn from Nortel's missteps. Security experts warn that more businesses have been hit by ongoing, difficult to detect exploits.

Anonymous: 10 Facts About The Hacktivist Group
Anonymous: 10 Facts About The Hacktivist Group
(click image for larger view and for slideshow)
It is every corporate security manager's worst nightmare.

News surfaced this week that Nortel's network was hacked in 2000, after which attackers enjoyed access to the telecommunications and networking company's secrets for 10 years.

The intrusions reportedly began after attackers used passwords stolen from the company's CEO, as well as six other senior executives, together with spyware. By 2004, a Nortel employee did detect unusual download patterns associated with senior executives' accounts, and changed related passwords. The security team also began watching for signs of suspicious activity, but apparently stopped doing so after a few months. The full extent of the breach wasn't discovered until 2010, by which time hackers had been accessing Nortel secrets--from technical papers and business plans, to research reports and employees' emails--for nearly a decade.

"This is a clear case of a total failure of an information security program and should be a wakeup call for other corporations," said Chris Mark, principal of the Mark Consulting Group, on the Global Security & Risk Management blog.

What should Nortel have done differently, and what can information security professionals learn from this example?

1. Don't Treat Nortel As The Exception. If there's one takeaway from the Nortel breach, it's that the advanced persistent threat is alive and well. "One of the main goals of the so-called APT is in fact its persistence. During recent years we have been seeing a lot of companies publicly reporting breaches, and the number is increasing steeply," said Jaime Blasco, manager of AlienVault Labs, via email. Without a doubt, data breaches now seem so common as to be banal. But what if APTs are just as prevalent, yet even less frequently spotted?

2. Keep Proving You're Not Nortel. Unfortunately, "low and slow" attacks that keep a low profile--so as to facilitate long-term data theft--are extremely difficult to detect, and thus tough to stop. "Although Nortel is in the headlines, this type of attack could be occurring undetected at other companies," said Mike Logan, president of Axis Technology, via email. Accordingly, businesses need to ensure that they have the right policies and procedures in place to help block such attacks, as well as to spot them when they happen.

3. Create A Robust Information Security Program. Blocking low-and-slow attacks requires a robust information security program, backed by the right technology. "Organizations need to ensure they have the proper tools at the perimeter and within their networks, and aggressive monitoring to detect outbound traffic and suspicious activity in the event of a breach," said Neil Roiter, director of research for Corero Network Security, via email. "The Aurora attacks, the RSA breach, and others demonstrate that Fortune 500 companies and other large enterprises are under constant threat from nation states such as China seeking shortcuts to technological advances."

4. Expect Defenses To Fail. Still, an information security program won't be completely effective all of the time. "Nowadays companies spend a lot of money placing prevention mechanisms such as antivirus, intrusion prevention systems, firewalls, and so on. When you are dealing with targeted attacks, these systems will eventually fail," said AlienVault's Blasco. "You often need a dedicated team that monitors the network and systems with advance tools to detect persistent and advanced threats. Companies should accept that they can be compromised and [invest in] detection and forensic tools and processes."

1 of 2
Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
User Rank: Apprentice
2/20/2012 | 5:01:24 PM
re: 8 Lessons From Nortel's 10-Year Security Breach
How bad?

A ten year ongoing breach is about as bad (and embarrasing) as it gets...
User Rank: Ninja
2/18/2012 | 2:21:33 AM
re: 8 Lessons From Nortel's 10-Year Security Breach
@readers: How badly did Nortel drop the ball in its investigation in your opinion?
Brian Prince, InformationWeek/Dark Reading Comment Moderator
Register for Dark Reading Newsletters
White Papers
Current Issue
E-Commerce Security: What Every Enterprise Needs to Know
The mainstream use of EMV smartcards in the US has experts predicting an increase in online fraud. Organizations will need to look at new tools and processes for building better breach detection and response capabilities.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
Published: 2015-10-15
The Direct Rendering Manager (DRM) subsystem in the Linux kernel through 4.x mishandles requests for Graphics Execution Manager (GEM) objects, which allows context-dependent attackers to cause a denial of service (memory consumption) via an application that processes graphics data, as demonstrated b...

Published: 2015-10-15
netstat in IBM AIX 5.3, 6.1, and 7.1 and VIOS 2.2.x, when a fibre channel adapter is used, allows local users to gain privileges via unspecified vectors.

Published: 2015-10-15
Cross-site request forgery (CSRF) vulnerability in eXtplorer before 2.1.8 allows remote attackers to hijack the authentication of arbitrary users for requests that execute PHP code.

Published: 2015-10-15
Directory traversal vulnerability in QNAP QTS before 4.1.4 build 0910 and 4.2.x before 4.2.0 RC2 build 0910, when AFP is enabled, allows remote attackers to read or write to arbitrary files by leveraging access to an OS X (1) user or (2) guest account.

Published: 2015-10-15
Cisco Application Policy Infrastructure Controller (APIC) 1.1j allows local users to gain privileges via vectors involving addition of an SSH key, aka Bug ID CSCuw46076.

Dark Reading Radio