RSA Admits SecurID Tokens Have Been Compromised 219
A few months ago, RSA Servers were hacked, and a few weeks ago Duped tokens were used to hack Lockheed-Martin. Well today
Orome1 writes "RSA has finally admitted publicly that the March breach into its systems has resulted in the compromise of their SecurID two-factor authentication tokens. The admission comes in the wake of cyber intrusions into the networks of three US military contractors: Lockheed Martin, L-3 Communications and Northrop Grumman — one of them confirmed by the company, others hinted at by internal warnings and unusual domain name and password reset process."
Cyber intrusions (Score:4, Insightful)
Dear Customers... (Score:5, Insightful)
Comment removed (Score:5, Insightful)
Re:Dear Customers... (Score:3, Insightful)
I think we're all assuming (for the most part) that the attack was over a network. If the keys were physically stolen from an offline box, then that's a different matter. If they had their high-security seed keys--as GP refers to them--accessible remotely in any manner, that was probably an avoidable mistake.
Re:Dear Customers... (Score:5, Insightful)
Those things should have been deleted upon transfer to the customer or(if so requested) stored on archival media in a vault somewhere unless needed by the customer for recovery purposes.
My point isn't "Ha Ha, their network guys fucked up, I could have done better!" My point is "for something as interesting as the seeds you would find useful in compromising a laundry-list of high-profile, high-security targets, basically no configuration would be sufficiently secure, and storing them in an insufficiently secure manner is hugely irresponsible.
After the the tokens were seeded, there was no further need for RSA to have them anywhere that they could be accessed electronically.
Re:Dear Customers... (Score:5, Insightful)
Re:Dear Customers... (Score:4, Insightful)
Re:RSA is Offering to Replace Tokens (Score:5, Insightful)
We are committed to providing you with a customer experience commesurate with what we can get away with. XOXOXO,
RSA
two factor? (Score:5, Insightful)
All I can find is the usual journalistic garbage, some fear mongering here and there, some harsh comments about RSA, some financial "news" commentary. No real information.
Can anyone on /. with technical knowledge, comment on the hack breaking the entire system (essentially, rooting the auth system) or is it just breaking one of the two factors, that being able to predict the "random" number generation of the keyfobs, so I'm down to merely having a pretty good "one factor"?
Also is the protocol poorly enough designed that the attackers don't need to know anything about the keyfobs, or rephrased, does keeping the serial number info etc about individuals keyfobs secret prevent the break?
Re:Dear Customers... (Score:4, Insightful)
RSA's customers certainly need to have a copy of their tokens' seed keys on their authentication server; but RSA doesn't need a copy of their customers' seed keys...
Unfortunately, I imagine they do need the copy: otherwise how do they make sure they never issue duplicates to different customers?
LOL that one was funny, and some PHB requirement like that is probably the cause of the whole problem. Like intro to crypto 101 problem funny. To the noobs out there, the solution involves storing the hash of the existing keys instead of the keys themselves. Supposedly, can't turn a hash back into a key, but if the hash of your new key matches a pre-existing hash, then its a dupe, make another and try again.
That's only needed if it's required to prove there's no dupes... realistically, if you have a 1024 bit key and 16 bits worth of customers, the odds of a collision, which wouldn't matter anyway, are 1 in 2 ** (1008) or in other words quite unlikely.
Re:Dear Customers... (Score:5, Insightful)
As for the second, I suspect that it is largely a matter of manufacturing convenience and/or fob tamper resistance. With RSA doing the keyfill at point of manufacture, the customer just needs to load the seed file for the entire batch onto their authentication server and then hand out the tokens, which are glued shut with considerable enthusiasm, and have no externally accessible electrical connections of any sort. If the customer did the fill, that would be extra effort (and a step where grunt manual labor would meet very sensitive data, not a pleasant HR situation...) for them, and would mean that RSA would have to validate their design against attacks on the exposed connectors. Neither is impossible to overcome; but under the(now invalid) assumption that RSA wouldn't fuck it up, certainly easier to avoid than to deal with.
Re:two factor? (Score:2, Insightful)
They have got the key to generate the "random" token. So, yes, it's down to one factor.
But I guess the password is the easy part.. Password reuse, keylogger, etc....
Re:Dear Customers... (Score:5, Insightful)
I like how everything is now "under-secured" as if you have any first hand knowledge of the nature of the attack at RSA or the security measures they had in place.
Someone got in. Seems to me that that is a very good, practical definition of "under-secured".
Comment removed (Score:4, Insightful)
Re:Is this an act of war? (Score:4, Insightful)