{"id":5081,"date":"2016-01-27T15:48:51","date_gmt":"2016-01-27T15:48:51","guid":{"rendered":"https:\/\/kasperskydaily.com\/b2b\/?p=5081"},"modified":"2020-12-18T12:10:54","modified_gmt":"2020-12-18T17:10:54","slug":"hyatt-hotel-chain-hit-by-financial-malware-how-to-prevent-such-things","status":"publish","type":"post","link":"https:\/\/www.kaspersky.com\/blog\/hyatt-hotel-chain-hit-by-financial-malware-how-to-prevent-such-things\/5081\/","title":{"rendered":"Hyatt hotel chain hit by financial malware; how to prevent such things?"},"content":{"rendered":"

The Hyatt hotel chain has revealed<\/a> recently that 250 of 627 of its properties worldwide were infected with money-stealing malware. Customer financial data may have been compromised, as well.<\/p>\n

The malware in question was designed specifically to steal financial data, including: cardholder names, card numbers, expiry dates, and the internal verification codes used to verify on-site transactions.<\/p>\n

Hyatt hotel chain hit by financial malware; how to prevent such things? #protectmybiz<\/p>Tweet<\/a><\/blockquote>\n

According to a statement issued by the company, the malware harvested credentials as they passed through Hyatt\u2019s infected payment processing systems. The information-stealing malware was active between August 13 and December 8, 2015, but some locations may have been infected as early as July 30, 2015. Fifty-four countries, including the US, UK, Germany, Russia, France, and Japan were affected, ZDNet<\/a> informed, providing a link to a global list of compromised sites<\/a>. If you visited one, chances are you may be a potential victim.<\/p>\n

This is clearly a \u201cfail\u201d case, but is it unique?<\/p>\n

It is not<\/strong><\/p>\n

The Hyatt chain doesn\u2019t look to be the only victim. Just the most recent. Last November, Hilton hotels reported a very similar cyberattack: hackers infected some of its point-of-sale computer systems with malware crafted to steal credit card information.<\/a><\/p>\n

Four days prior to Hilton\u2019s revelations, Starwood Hotels said<\/a> its payment systems in 54 hotels have also been infected with credit card data \u201charvesters\u201d.<\/p>\n

Earlier in 2015, Mandarin Oriental chain discovered<\/a> malware in its payment processing. Somebody had also been \u201ccollecting\u201d credit card data from The Trump Hotel Collection between May 2014 and June 2015.<\/a><\/p>\n

So, as we can see, attacks on hotels are not anywhere near unique. Unfortunately. We have previously addressed<\/a> cybersecurity in hotels worldwide \u2013 in relation to Darkhotel APT<\/a>, at least, and there\u2019s really room for improvement, which is clearly shown by these attacks upon the world\u2019s leading hotel chains.<\/p>\n

Late in 2014<\/a>, we covered cybersecurity issues in the hospitality industry, and there are lots of them aside from malware in payment systems and\/or APTs targeting the top-tier residents; attacks upon the payment processing, apparently, is the most immediate problem, as a lot of people and businesses appear to be at risk.<\/p>\n

Hotel chains have been hit before. Attackers want to be \u201cclose to money\u201d\u00a0#protectmybiz<\/p>Tweet<\/a><\/blockquote>\n

What can be done against such incidents?<\/strong><\/p>\n

There are a number of cybesecurity tools and approaches available which can help the hospitality industry to prevent such disastrous experiences like that of Hyatt and others.<\/p>\n

First of all, wherever significant volumes of personal, financial, or other sensitive data is involved, policies covering data storage and access should be especially strict. Properly set data access rules are a very significant part of establishing secure environment. Then there are the practical applications:<\/p>\n

    \n
  1. Data storage security should be a top priority. This includes File Level encryption, Portable Storage encryption and perhaps even Full Disk encryption. All three are available as part of Kaspersky Endpoint Security for Business Advanced. Take a look on our whitepaper<\/a> describing our approach to encryption as a security measure.<\/li>\n
  2. Restrict access to the web and the use of personal storage. For this, Web Control and Device Control are available in Kaspersky Endpoint Security for Business (tiers Select and Advanced).<\/li>\n
  3. Restrict the use of unsolicited applications, even considering a Default Deny scenario for certain endpoints (such as reception), whereas running any software which is not in the permitted list is denied \u2013 by default, apparently. Default Deny may seem complex, however, at times it\u2019s the only way to ensure the necessary level of security, especially when critical data is in question. Also, the limited number of tasks undertaken by the users of such endpoints makes this scenarios less complex to deploy. Application Control technology allowing the Default Deny scenario is available in Kaspersky Endpoint Security for Business (tiers Select and Advanced).<\/li>\n<\/ol>\n

    More information on Kaspersky Endpoint Security for Business is available here<\/a>.<\/p>\n

    The cases of top hotel chains, as well as earlier attacks on payment systems of large retailers<\/a>, make it obvious personal data and payment systems require strong protection (in many cases, it should be stronger than it is now). The right approach and the use of proper technologies is a sort of insurance against massive data leaks and the reputation damage that would follow. And a reputation\u2019s cost is very high everywhere, especially for businesses processing other people\u2019s data and payments.<\/p>\n

    Stay safe!<\/p>\n","protected":false},"excerpt":{"rendered":"

    The Hyatt hotel chain has revealed recently that 250 of 627 of its properties worldwide were infected with money-stealing malware. <\/p>\n","protected":false},"author":209,"featured_media":15342,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1999,3052],"tags":[2071,2383,36,97],"class_list":{"0":"post-5081","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-business","8":"category-smb","9":"tag-cyberattacks","10":"tag-hotel","11":"tag-malware-2","12":"tag-security-2"},"hreflang":[{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/hyatt-hotel-chain-hit-by-financial-malware-how-to-prevent-such-things\/5081\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/hyatt-hotel-chain-hit-by-financial-malware-how-to-prevent-such-things\/5081\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/hyatt-hotel-chain-hit-by-financial-malware-how-to-prevent-such-things\/5081\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/www.kaspersky.com\/blog\/tag\/cyberattacks\/","name":"cyberattacks"},"_links":{"self":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/5081","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/users\/209"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/comments?post=5081"}],"version-history":[{"count":5,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/5081\/revisions"}],"predecessor-version":[{"id":38142,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/5081\/revisions\/38142"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/media\/15342"}],"wp:attachment":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/media?parent=5081"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/categories?post=5081"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/tags?post=5081"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}