{"id":686,"date":"2018-06-06T18:17:05","date_gmt":"2018-06-06T18:17:05","guid":{"rendered":"https:\/\/bfghs.org\/?p=686"},"modified":"2018-06-06T18:17:05","modified_gmt":"2018-06-06T18:17:05","slug":"myheritage-cybersecurity-incident","status":"publish","type":"post","link":"https:\/\/bfghs.org\/myheritage-cybersecurity-incident\/","title":{"rendered":"MyHeritage Cybersecurity Incident"},"content":{"rendered":"<div class=\"container warp flex\">\n<div>\n<article class=\"main hoverzoompost\">\n<div class=\"single-content hero_overlay\">\n<header class=\"post-header\">\n<h6>Accessed: June 6, 2018, My Heritage Blog<\/h6>\n<h1>MyHeritage Statement About a Cybersecurity Incident<\/h1>\n<ul class=\"post-meta\">\n<li>By Admin\u00a0\u00b7<\/li>\n<li>June 4, 2018<\/li>\n<\/ul>\n<\/header>\n<div class=\"inner-content\">\n<p>Today, June 4, 2018 at approximately 1pm EST, MyHeritage\u2019s Chief Information Security Officer received a message from a security researcher that he had found a file named myheritage containing email addresses and hashed passwords, on a private server outside of MyHeritage. Our Information Security Team received the file from the security researcher, reviewed it, and confirmed that its contents originated from MyHeritage and included all the email addresses of users who signed up to MyHeritage up to October 26, 2017, and their hashed passwords.<\/p>\n<p>Immediately upon receipt of the file, MyHeritage\u2019s Information Security Team analyzed the file and began an investigation to determine how its contents were obtained and to identify any potential exploitation of the MyHeritage system. We determined that the file was legitimate and included the email addresses and hashed passwords of 92,283,889 users who had signed up to MyHeritage up to and including Oct 26, 2017 which is the date of the breach. MyHeritage does not store user passwords, but rather a one-way hash of each password, in which the hash key differs for each customer. This means that anyone gaining access to the hashed passwords does not have the actual passwords.<\/p>\n<p>The security researcher reported that no other data related to MyHeritage was found on the private server. There has been no evidence that the data in the file was ever used by the perpetrators. Since Oct 26, 2017 (the date of the breach) and the present we have not seen any activity indicating that any MyHeritage accounts had been compromised.<\/p>\n<p>We believe the intrusion is limited to the user email addresses. We have no reason to believe that any other MyHeritage systems were compromised. As an example, credit card information is not stored on MyHeritage to begin with, but only on trusted third-party billing providers (e.g. BlueSnap, PayPal) utilized by MyHeritage. Other types of sensitive data such as family trees and DNA data are stored by MyHeritage on segregated systems, separate from those that store the email addresses, and they include added layers of security. We have no reason to believe those systems have been compromised.<\/p>\n<p><strong>Steps We\u2019ve Taken<\/strong><\/p>\n<p>Immediately upon learning about the incident, we set up an Information Security Incident Response Team to investigate the incident. We are also taking immediate steps to engage a leading, independent cybersecurity firm to conduct comprehensive forensic reviews to determine the scope of the intrusion; and to conduct an assessment and provide recommendations on steps that can be taken to help prevent such an incident from occurring in the future.<\/p>\n<p>We are taking steps to inform relevant authorities including as per GDPR.<\/p>\n<p>We will be expediting our work on the upcoming two-factor authentication feature that we will make available to all MyHeritage users soon. This will allow users interested in taking advantage of it, to authenticate themselves using a mobile device in addition to a password, which will further harden their MyHeritage accounts against illegitimate access.<\/p>\n<p>We set up a 24\/7 security customer support team to assist customers who have concerns or questions about the incident.<\/p>\n<p><strong>What Our Users Should Do<\/strong><\/p>\n<p>MyHeritage users who have questions or concerns about this incident can contact our security customer support team via email on <a href=\"mailto:privacy@myheritage.com\">privacy@myheritage.com<\/a> or by phone via the toll-free number (USA) +1 888 672 2875, available 24\/7.<\/p>\n<p><span style=\"color: #ff0000;\">For all registered users of MyHeritage, we recommend that for maximum safety, they change their password on MyHeritage. The procedure for doing this is described in the MyHeritage <a style=\"color: #ff0000;\" href=\"http:\/\/helpcenter.myheritage.com\/Account-Settings\/Change-password-Email\/634030922501487720\/How-do-I-change-my-email-address-and-or-password.htm\" target=\"_blank\" rel=\"noopener\">FAQ article<\/a>. Once MyHeritage releases the upcoming two-factor-authentication feature, we recommend to all our users to take advantage of it.<\/span><\/p>\n<p>For now, there are no other actions that MyHeritage users need to take as a result of this incident. However, we always recommend that you take the time to evaluate your security practices. Please, avoid using the same password for multiple services or websites. It\u2019s good practice to use stronger passwords and to change them often.<\/p>\n<p><strong>Going Forward<\/strong><\/p>\n<p>As always, your privacy and the security of your data are our highest priority. We continually assess our procedures and policies and seek new ways to improve our approach to security. We understand the importance of our role as custodians of your information and work every day to earn your trust.<\/p>\n<p>Thank you for your understanding.<\/p>\n<p><strong>Contact<\/strong><\/p>\n<p>Omer Deutsch<br \/>\nChief Information Security Officer, MyHeritage<br \/>\nEmail: <a href=\"mailto:dpo@myheritage.com\">dpo@myheritage.com<\/a><\/p>\n<div class=\"meta-tags\"><\/div>\n<\/div>\n<\/div>\n<section class=\"related\">\n<header>\n<h3><\/h3>\n<\/header>\n<div class=\"flex\">\n<article>\n<div class=\"single-content\">\n<div class=\"post-meta\">\n<div class=\"sociel-meta\">\n<div class=\"a2a_kit stubbed-fb\">\n<div class=\"fb-stub\"><\/div>\n<\/div>\n<\/div>\n<\/div>\n<p>&nbsp;<\/p>\n<\/div>\n<\/article>\n<\/div>\n<\/section>\n<\/article>\n<div id=\"respond\">\n<form id=\"commentform\" action=\"https:\/\/blog.myheritage.com\/wp-comments-post.php\" method=\"post\" novalidate=\"novalidate\">\n<div class=\"gglcptch gglcptch_v2\">\n<div id=\"gglcptch_recaptcha_1845562274\" class=\"gglcptch_recaptcha\"><\/div>\n<\/div>\n<\/form>\n<\/div>\n<\/div>\n<aside id=\"sidebar\">\n<section class=\"widget popular\">\n<article>\n<div class=\"single-content\">\n<div class=\"post-meta\"><\/div>\n<\/div>\n<\/article>\n<article><\/article>\n<article>\n<div class=\"single-content\">\n<div class=\"post-meta\"><\/div>\n<\/div>\n<\/article>\n<\/section>\n<p>&nbsp;<\/p>\n<\/aside>\n<\/div>\n<footer>\n<div class=\"container\">\n<div id=\"main-footer\">\n<div id=\"et-footer-nav\">\n<div class=\"container\">\n<div class=\"col-row\">\n<div class=\"footer-col\">\n<div class=\"widget\">\n<div class=\"menu-footer-col-1-container\"><\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/footer>\n","protected":false},"excerpt":{"rendered":"<p>Accessed: June 6, 2018, My Heritage Blog MyHeritage Statement About a Cybersecurity Incident By Admin\u00a0\u00b7 June 4, 2018 Today, June 4, 2018 at approximately 1pm EST, MyHeritage\u2019s Chief Information Security Officer received a message from a security researcher that he had found a file named myheritage containing email addresses and hashed passwords, on a private<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_exactmetrics_skip_tracking":false,"_exactmetrics_sitenote_active":false,"_exactmetrics_sitenote_note":"","_exactmetrics_sitenote_category":0,"footnotes":""},"categories":[20,33],"tags":[27,26,32,30,31],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/bfghs.org\/wp-json\/wp\/v2\/posts\/686"}],"collection":[{"href":"https:\/\/bfghs.org\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/bfghs.org\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/bfghs.org\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/bfghs.org\/wp-json\/wp\/v2\/comments?post=686"}],"version-history":[{"count":0,"href":"https:\/\/bfghs.org\/wp-json\/wp\/v2\/posts\/686\/revisions"}],"wp:attachment":[{"href":"https:\/\/bfghs.org\/wp-json\/wp\/v2\/media?parent=686"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/bfghs.org\/wp-json\/wp\/v2\/categories?post=686"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/bfghs.org\/wp-json\/wp\/v2\/tags?post=686"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}