RSA SecurID Breach Shows Why Everybody Must Stay Vigilant

 
 
By Wayne Rash  |  Posted 2011-03-20 Email Print this article Print
 
 
 
 
 
 
 

News Analysis: The theft of unspecified information relating to the two-factor identification technology from the depths of RSA's SecurID security system should help corporate IT managers remember to do what they should have been doing all along.

Two-factor authentication has been considered by many to be the gold standard for secure IT access. The idea is that you must have two things, something you have such as a token and something you know, such as a password. Many companies, for example, require a smart card with an embedded identity chip to be inserted into a card reader. Once the smart card is inserted, you're then prompted for your password. 

The SecurID security device was a token that you didn't have to insert. It would present a number to the user that changed every 30 seconds. By typing in the number to a SecurID prompt, it demonstrated evidence that you had the token and would then let you enter a password. Exactly how RSA knew what number was the correct number at any given time was part of its strength-you didn't need to equip your computers with card readers to have two-factor authentication. 

The algorithm that lets RSA know what number is the correct number may be part of what was stolen in a security breach of RSA's data systems. Right now, RSA is frantically telling customers that their data is still safe. RSA is probably right. The simple possession of the algorithm isn't enough to allow someone to break into an existing secure system.  

The algorithm may tell how the process is accomplished, but in itself it isn't going to reveal those numbers that change every 30 seconds. Even stealing a company's key from RSA probably won't help because it won't reveal the correct number for the token at any given moment. 

What's more likely is that someone really wanted to know how the RSA SecurID worked, either so they could make their own competing product or so they could reverse engineer a device that eventually might be able to help gain access to protected information. But in reality, we don't know for sure because all that RSA has revealed is that information related to SecurID was taken, but they aren't saying what that information was. 

What this means to you is there's not an immediate threat, even if whoever stole the information from RSA figures out how to hack the SecurID code. What it means is you need to make sure you practice and enforce good password discipline in addition to using the SecurID token.  




 
 
 
 
Wayne Rash Wayne Rash is a Senior Analyst for eWEEK Labs and runs the magazine's Washington Bureau. Prior to joining eWEEK as a Senior Writer on wireless technology, he was a Senior Contributing Editor and previously a Senior Analyst in the InfoWorld Test Center. He was also a reviewer for Federal Computer Week and Information Security Magazine. Previously, he ran the reviews and events departments at CMP's InternetWeek.

He is a retired naval officer, a former principal at American Management Systems and a long-time columnist for Byte Magazine. He is a regular contributor to Plane & Pilot Magazine and The Washington Post.
 
 
 
 
 
 
 

Submit a Comment

Loading Comments...
 
Manage your Newsletters: Login   Register My Newsletters























 
 
 
 
 
 
 
 
 
 
 
Thanks for your registration, follow us on our social networks to keep up-to-date
Rocket Fuel