jeudi 26 mai 2016

Important information about LinkedIn accounts

Notice of Data Breach
You may have heard reports recently about a security issue involving LinkedIn. LinkedIn would like to make sure you have the facts about what happened, what information was involved, and the steps they are taking to help protect their users.
What Happened?
On May 17, 2016, LinkedIn became aware that data stolen from LinkedIn in 2012 was being made available online. This was not a new security breach or hack. LinkedIn took immediate steps to invalidate the passwords of all LinkedIn accounts that they believed might be at risk. These were accounts created prior to the 2012 breach that had not reset their passwords since that breach.
What Information Was Involved?
Member email addresses, hashed passwords, and LinkedIn member IDs (an internal identifier LinkedIn assigns to each member profile) from 2012.
What LinkedIn Are Doing
LinkedIn invalidated passwords of all LinkedIn accounts created prior to the 2012 breach that had not reset their passwords since that breach. In addition, they are using automated tools to attempt to identify and block any suspicious activity that might occur on LinkedIn accounts. LinkedIn are also actively engaging with law enforcement authorities.
LinkedIn has taken significant steps to strengthen account security since 2012. For example, LinkedIn now use salted hashes to store passwords and enable additional account security by offering their members the option to use two-step verification.
What You Can Do
LinkedIn have several dedicated teams working diligently to ensure that the information members entrust to LinkedIn remains secure. LinkedIn always suggest that their members visit the Safety Center to learn about enabling two-step verification, and implementing strong passwords in order to keep their accounts as safe as possible. LinkedIn recommend that you regularly change your LinkedIn password and if you use the same or similar passwords on other online services, we recommend you set new passwords on those accounts as well.

Aucun commentaire: