Attacks/Breaches
3/21/2011
11:51 AM
Connect Directly
RSS
E-Mail
50%
50%

SecurID Customers Advised To Prepare For Worst Case

EMC's RSA hasn't detailed exactly what was stolen, so security experts advise the authentication system's customers to implement a more layered network defense.

10 Massive Security Breaches
(click image for larger view)
Slideshow: 10 Massive Security Breaches
How serious is the security threat posed by the theft of inside information about SecurID, the two-factor authentication system sold by EMC division RSA? "It is important enough that it required an official note to the stock markets," said Martin Kuppinger, founder and principal analyst at KuppingerCole, in a blog post.

But, despite the apparent severity of the breach, RSA's failure to detail what was stolen is generating an immense amount of customer frustration, because they don't know if their SecurID hardware fobs are still secure, or if they might provide attackers with a conduit through enterprise defenses.

Here's the worst-case scenario: "The worry is that source code to the company's SecurID two-factor authentication product was stolen, which would possibly allow hackers to reverse-engineer or otherwise break the system," said Bruce Schneier, chief security technology officer of BT, in a blog post. In that case, attackers could spoof SecurID to access corporate systems.

Until RSA coughs up more information, security experts advocate conducting a thorough and immediate SecurID risk assessment. "Our recommendation for customers which have RSA SecurID cards implemented is to first carefully analyze the situation and their specific risks -- [for example] which type of information is at risk if the RSA SecurID-based authentication is not only at risk -- like now -- but an attack actually takes place?" said Kuppinger.

Next, identify specific technologies and remediation activities for securing at-risk data or accounts. "These actions might range from increased threat analysis and forensics to adding other authentication technologies," said Kuppinger.

But rather than just shopping for a SecurID replacement, numerous experts are recommending that security managers turn this situation into an opportunity to create a more layered security defense. "Many organizations rely too heavily on two-factor authentication and they have historically seen it as a silver bullet," said William Beer, PricewaterhouseCoopers (PwC) director of OneSecurity, in an emailed statement.

Stay tuned for more details about the extent of the attacks, their effect on RSA, and the security and IT management ramifications for their customers. "RSA Data Security, Inc. is probably pretty screwed if SecurID is compromised," said BT's Schneier. "Those hardware tokens have no upgrade path, and would have to be replaced."

That would be no small task. RSA had 40 million SecurID hardware token customers by 2009, as well as 250 million users of SecurID software.

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-2009-5142
Published: 2014-08-21
Cross-site scripting (XSS) vulnerability in timthumb.php in TimThumb 1.09 and earlier, as used in Mimbo Pro 2.3.1 and other products, allows remote attackers to inject arbitrary web script or HTML via the src parameter.

CVE-2010-5302
Published: 2014-08-21
Cross-site scripting (XSS) vulnerability in timthumb.php in TimThumb before 1.15 as of 20100908 (r88), as used in multiple products, allows remote attackers to inject arbitrary web script or HTML via the QUERY_STRING.

CVE-2010-5303
Published: 2014-08-21
Cross-site scripting (XSS) vulnerability in the displayError function in timthumb.php in TimThumb before 1.15 (r85), as used in multiple products, allows remote attackers to inject arbitrary web script or HTML via unspecified vectors related to $errorString.

CVE-2014-0965
Published: 2014-08-21
IBM WebSphere Application Server (WAS) 7.0.x before 7.0.0.33, 8.0.x before 8.0.0.9, and 8.5.x before 8.5.5.3 allows remote attackers to obtain sensitive information via a crafted SOAP response.

CVE-2014-3022
Published: 2014-08-21
IBM WebSphere Application Server (WAS) 7.0.x before 7.0.0.33, 8.0.x before 8.0.0.9, and 8.5.x before 8.5.5.3 allows remote attackers to obtain sensitive information via a crafted URL that triggers an error condition.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Three interviews on critical embedded systems and security, recorded at Black Hat 2014 in Las Vegas.