Turkeuro

RSA and SecurID, 2011

In March 2011 RSA, the security company, said it had been attacked and that information related to its SecurID tokens had been taken. RSA said the attack began with a phishing email sent to an employee. Customers who relied on those tokens, including large firms, had to treat the tokens as exposed and many replaced them. Turkeuro was not the victim.

What people lost was confidence in a second check they had been counting on. A token that was supposed to prove a sign-in had to be replaced because information about the system had left the company. Employees and customers spent time and money on that replacement. The mail that started the public account was the phishing message. This page does not describe the file or any further step.

RSA published an open letter and later said the information taken was related to SecurID. The letter was the company's own account. Turkeuro was not a customer in that story, did not hold the token data, and did not run the investigation.

What a person should do instead is leave an unexpected file closed. Call the person who supposedly sent it, on a number you already have, before you open anything. A message that talks about security is not itself a reason to hurry.

An authenticator app can be saved on a Turkeuro account today. The setup key is shown so you can add it to the app. The sign-in screen does not ask for the app code again. That limit is why a Turkeuro user should not imagine that an app, by itself, replayed the RSA story or prevented it. The habit that matches this history is still the slow one: do not open a surprise file from mail.

Press News