Access member only content, take part in discussions with comments on blogs, news and reviews and receive all the latest security industry news directly to your inbox. Join now for free.
Processing registration... Please wait.
This process can take up to a minute to complete.
A confirmation email has been sent to your email address - SUPPLIED EMAIL HERE. Please click on the link in the email to verify your email address. You need to verify your email before you can start posting.
If you do not receive your confirmation email within the next few minutes, it may be because the email has been captured by a junk mail filter. Please ensure you add the domain @scmagazine.com.au to your white-listed senders.
Five days after RSA revealed its systems were breached by a sophisticated attack, details were scant about how customers of its SecurID two-factor authentication products may be affected.
Still, that hasn't stopped many in the security community from speculating.
Here are latest details emerging:
The US Department of Homeland Security (DHS) has joined the investigation into the compromise.
"Working with RSA, we are leveraging the technical, investigative and mitigation expertise of US Government agencies to address this issue," said Amy Kudwa, a DHS spokesman.
"We take threats to our cyber infrastructure as seriously as we take threats to our conventional, physical infrastructure. DHS is also in the process of distributing similar information to our critical infrastructure partners."
Republican senator Susan Collins chairan of the Homeland Security Committee, said the "need to pass comprehensive cybersecurity legislation is more urgent than ever" following disclosure of the breach.
She said Congress should mandate how private and public sector players collaborate to deter attacks.
Steven Bellovin, a computer science professor at Columbia University in New York, offered a technical analysis of the breach. He provided customer-impact scenarios, but suggested the biggest risk might be that the hackers gained access to the source code of RSA's back-end systems, used to deploy tokens to organisations.
"There's a lot of code needed for maintaining databases, adding and deleting users, making backups, synchronizing master and secondary copies of databases and more," Bellovin wrote.
"An attacker who could penetrate these administrative systems doesn't have to worry about key generation or cryptanalysis; they could simply steal existing keys or insert new ones of their own."
Adam Shostack, author of The New School of Information Security blogged Monday that attackers may be after more than the "seeds," used to generate valid, unique SecurID six-digit token values. The thieves may also have acquired customer lists to target organisations.
"My opinion is that social engineers using the contacts database in some way is more likely than a cryptanalytic attack, and a cryptanalytic attack is more likely than a compromise of a secrets database," he wrote.
"But we don't know. Speculating like mad isn't helping."
Bruce Schneier, chief security technology officer at BT Global Services, opined that because the SecurID tokens have no "upgrade path" RSA stood to lose business from customers opting for a competitor's product. But it was unclear whether users can expect to see targeted or far-reaching attacks.
"One, [the culprits] are a sophisticated organisation who want the information for a specific purpose," Schneier wrote.
"The attackers [in this case] actually are on RSA's side in the public-relations spin, and we're unlikely to see widespread use of this information.
"Or, two, they stole the stuff for conventional criminal purposes and will sell it. In that case, we're likely to know pretty quickly."
This article originally appeared at scmagazineus.com
To begin commenting right away, you can log in below or register an account if you don't yet have one. Please read our guidelines on commenting. Offending posts will be removed and your access may be suspended. Abusive or obscene language will not be tolerated. The comments below do not necessarily reflect the views or opinions of SC Magazine, Haymarket Media or its employees.