Yandex announced a leak of archived client data of the Yandex.Food service. The incident led to an internal investigation.
The leaked archive included customer phone numbers, order data, namely content and delivery time. According to Yandex, the leak was due to the fault of an unnamed employee. It is noted that payment details, logins and passwords are not shared.
Following the completion of the investigation, the company decided to expand controls to ensure the confidentiality of sensitive data related to orders. Now this information will be assigned a level of protection similar to the level of confidentiality of payment data. In addition, the number of employees with access to this information will decrease, and its manual processing will be excluded. The perpetrator of the incident will be sanctioned in accordance with applicable law.
The service also apologized to users and assured that it would send a letter with all the details about the incident to those customers who were affected by the leak. How many accounts appeared in the leak, "Yandex" does not report.
The leaked archive included customer phone numbers, order data, namely content and delivery time. According to Yandex, the leak was due to the fault of an unnamed employee. It is noted that payment details, logins and passwords are not shared.
Following the completion of the investigation, the company decided to expand controls to ensure the confidentiality of sensitive data related to orders. Now this information will be assigned a level of protection similar to the level of confidentiality of payment data. In addition, the number of employees with access to this information will decrease, and its manual processing will be excluded. The perpetrator of the incident will be sanctioned in accordance with applicable law.
The service also apologized to users and assured that it would send a letter with all the details about the incident to those customers who were affected by the leak. How many accounts appeared in the leak, "Yandex" does not report.
Login or register to post comments
Comments 0