Risk
2/6/2011
06:52 PM
George V. Hulme
George V. Hulme
Commentary
Connect Directly
RSS
E-Mail
50%
50%

Nasdaq Hack. Lots of Questions. Few Answers

According to a news report this weekend, hackers breached web-based applications owned by the NASDAQ. How deep did the attacks go, and who was behind them?

According to a news report this weekend, hackers breached web-based applications owned by the NASDAQ. How deep did the attacks go, and who was behind them?A news story from The Wall Street Journal reported that attackers had penetrated, on multiple occasions, the computer networks of the company that runs the Nasdaq Stock Market. According to the story federal investigators are working to uncover the criminals. The Nasdaq trading platform was not affected, the story claimed. The story was based on unnamed sources.

It wasn't the Nasdaq stock market that the attackers were after it turns out, but information from the boards of directors of publicly traded companies. To get that, it was their Web-based collaboration platform – Directors Desk – that was the target.

This statement from Nasdaq says that the company detected suspicious files on U.S. servers and determined: that our web facing application Directors Desk was potentially affected. We immediately conducted an investigation, which included outside forensic firms and U.S. federal law enforcement. The files were immediately removed and at this point there is no evidence that any Directors Desk customer information was accessed or acquired by hackers.

The The Wall Street Journal, in a follow-up story, reported that the exchange will be run as usual for trading on Monday.

According its own Web site, Directors Desk is used by 10,000 directors at Fortune 500 sized companies. That's a trove of information, so no shocker the system was targeted.

The Nasdaq OMX was no slouch when it comes to security, either:

Operational Security

Our policies comply with the ISO27001 security standard, providing multiple levels of protection to guard our clients' confidential data against undesired access. The ISO27001 standard includes employee background screening; policies that restrict physical and logical access to classified information; management of information systems; firewalling; intrusion detection; risk assessment; and guaranteed destruction of expired data.

Application Security

Directors Desk provides multiple layers of security to protect our clients' most vital corporate records.

User authentication is tightly controlled through "strong passwords," fully encrypted transport, procedures surrounding account activation, and encryption of all service level passwords in the system.

Role-based security protocols control which content is available to each user upon logging in.

Network and host-based Intrusion Detection Systems (IDS) protect all hardware and applications in the Directors Desk server farm

Complying with security standards, having good authentication and authorization systems in place is great. So are IDS systems. But no matter how many layers of security are in place, what matters is how well it's all orchestrated together. That's why lists of standards being adhered to, as well as security technologies in place don't really tell us much about how secure an organization is.

So far, not much information about this hack. Hopefully, Nasdaq is correct, and no customer information was stolen. But we still don't know who was behind the attack, and can only assume that it was board secrets that the attackers sought.

For my security and technology observations throughout the day, find me on Twitter.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Cartoon
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-4262
Published: 2014-07-28
svnwcsub.py in Subversion 1.8.0 before 1.8.3, when using the --pidfile option and running in foreground mode, allows local users to gain privileges via a symlink attack on the pid file. NOTE: this issue was SPLIT due to different affected versions (ADT3). The irkerbridge.py issue is covered by CVE-...

CVE-2013-4840
Published: 2014-07-28
Unspecified vulnerability in HP and H3C VPN Firewall Module products SECPATH1000FE before 5.20.R3177 and SECBLADEFW before 5.20.R3177 allows remote attackers to cause a denial of service via unknown vectors.

CVE-2013-7393
Published: 2014-07-28
The daemonize.py module in Subversion 1.8.0 before 1.8.2 allows local users to gain privileges via a symlink attack on the pid file created for (1) svnwcsub.py or (2) irkerbridge.py when the --pidfile option is used. NOTE: this issue was SPLIT from CVE-2013-4262 based on different affected versions...

CVE-2014-2974
Published: 2014-07-28
Cross-site request forgery (CSRF) vulnerability in php/user_account.php in Silver Peak VX through 6.2.4 allows remote attackers to hijack the authentication of administrators for requests that create administrative accounts.

CVE-2014-2975
Published: 2014-07-28
Cross-site scripting (XSS) vulnerability in php/user_account.php in Silver Peak VX before 6.2.4 allows remote attackers to inject arbitrary web script or HTML via the user_id parameter.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Sara Peters hosts a conversation on Botnets and those who fight them.