{"id":232926,"date":"2020-06-28T06:58:00","date_gmt":"2020-06-28T04:58:00","guid":{"rendered":"https:\/\/www.borncity.com\/blog\/?p=232926"},"modified":"2021-07-14T11:38:52","modified_gmt":"2021-07-14T09:38:52","slug":"datenschutzproblem-bei-twitter","status":"publish","type":"post","link":"https:\/\/borncity.com\/blog\/2020\/06\/28\/datenschutzproblem-bei-twitter\/","title":{"rendered":"Datenschutzproblem bei Twitter"},"content":{"rendered":"

[English<\/a>]Diese Woche musste Twitter sich bei Kunden wegen eines Datenlecks, bei dem Ungefugte Zugriff auf Gesch\u00e4ftsdaten (Rechnungsdaten) bekamen, entschuldigen.<\/p>\n

<\/p>\n

Ich bin die Tage durch Blog-Leser Tobias W. auf diesen Sachverhalt aufmerksam geworden. Er hat wohl von Twitter folgende Mail erhalten:<\/p>\n

Hello,<\/p>\n

We are writing to let you know of a data security incident that may have
\ninvolved your personal information on ads.twitter.com and
\nanalytics.twitter.com.<\/p>\n

We became aware of an issue that meant that prior to May 20, 2020, if
\nyou viewed your billing information on ads.twitter.com or
\nanalytics.twitter.com the billing information may have been stored in
\nthe browser's cache. Examples of that information include email address,
\nphone number, last four digits of your credit card number (not complete
\nnumbers, expiration dates or security codes), and billing address. If
\nyou used a shared computer, it is possible that if someone used the
\ncomputer after you they could have seen the information stored in the
\nbrowser's cache (most browsers generally store data in their cache by
\ndefault for a short period of time like 30 days).<\/p>\n

On May 20, 2020, we updated the instructions that Twitter sends to your
\nbrowser's cache to stop this from happening. While we have no evidence
\nthat your billing information was compromised, we want to make sure
\nyou're aware of the issue and how to protect yourself going forward. If
\nyou currently use a shared computer to access your Twitter Ads or
\nAnalytics billing information, we recommend clearing the browser cache
\nwhen you log out.<\/p>\n

We're very sorry this happened. We recognize and appreciate the trust
\nyou place in us, and are committed to earning that trust every day. If
\nyou have additional questions, you can write to our Office of Data
\nProtection here <zensiert><\/p>\n

Thank you.<\/p>\n

Twitter International Company
\nOne Cumberland Place, Fenian Street
\nDublin 2, D02 AX07 IRELAND<\/p><\/blockquote>\n

Man hat festgestellt, dass bei den Benutzern vertrauliche Daten \u00fcber Gesch\u00e4ftsvorf\u00e4lle (Name, E-Mail, Kreditkartennummer etc.) w\u00e4hrend der Eingabe im lokalen Cache des Browsers gespeichert werden. Das birgt die Gefahr, dass unbefugte Dritte \u00fcber den Cache an sensitive Daten herankommen.<\/p>\n

Am 20. Mai 2020 hat Twitter die Anweisungen, die den Umgang mit dem Browsercache betreffen, aktualisiert, um den Datenabfluss auf diesem Weg zu verhindern. Obwohl die Leute keine Beweise haben, dass Rechnungsdaten kompromittiert wurden, m\u00f6chten die Twitter-Verantwortlichen sicherstellen, dass die Nutzer sich des Problems bewusst sind und wissen, wie sie sich in Zukunft sch\u00fctzen k\u00f6nnen.<\/p>\n

Wer einen gemeinsam genutzten Computer f\u00fcr den Zugriff auf Twitter-Anzeigen verwendet oder Abrechnungsinformationen abruft, dem empfehlen die Twitter-Leute, den Browser-Cache zu l\u00f6schen, sobald man sich abmeldet. Die BBC hat hier einen Artikel<\/a> dar\u00fcber ver\u00f6ffentlicht \u2013 und hier<\/a> gibt es auch was dazu.<\/p>\n","protected":false},"excerpt":{"rendered":"

[English]Diese Woche musste Twitter sich bei Kunden wegen eines Datenlecks, bei dem Ungefugte Zugriff auf Gesch\u00e4ftsdaten (Rechnungsdaten) bekamen, entschuldigen.<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[908,426],"tags":[451,4328,1267],"class_list":["post-232926","post","type-post","status-publish","format-standard","hentry","category-internet","category-sicherheit","tag-datenschutz","tag-sicherheit","tag-twitter"],"_links":{"self":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/232926","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/comments?post=232926"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/232926\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/media?parent=232926"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/categories?post=232926"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/tags?post=232926"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}