{"id":15059,"date":"2015-04-07T16:37:23","date_gmt":"2015-04-07T16:37:23","guid":{"rendered":"http:\/\/kasperskydaily.com\/b2b\/?p=3804"},"modified":"2020-02-26T11:01:09","modified_gmt":"2020-02-26T16:01:09","slug":"apparent-reasons-a-few-examples-of-why-it-security-breaches-happen","status":"publish","type":"post","link":"https:\/\/www.kaspersky.com\/blog\/apparent-reasons-a-few-examples-of-why-it-security-breaches-happen\/15059\/","title":{"rendered":"Apparent reasons: a few examples of why IT security breaches happen"},"content":{"rendered":"

Over the last few years we have witnessed a number of high-profile, large scale security breaches with quite dramatic consequences, such as massive leaks of personally identifiable data. It ranges from something rather innocuous, albeit displeasing, like the real names of the MMO players, to something extremely dangerous such as credit card and social security numbers. So why does this happen? The reasons may be different in every specific case, but most of the time they can be described with just three words.<\/p>\n

Severe Cases<\/strong><\/p>\n

The incidents with Sony Playstation Network and Sony Pictures \u2013 that led to the leakage of terabytes of sensitive data \u2013 now feel almost iconic. And while attacks on their own could be quite sophisticated, the actual reason behind the catastrophic proportions of the leaks are the same in both cases. Sony divisions IT workers kept that data less than secure: passwords in plain texts, unencrypted documents, folders openly called \u201cPasswords\u201d, \u2013 in other words, all of these \u201cvaluable assets\u201d were lying around in plain sight.<\/p>\n

IT #security breaches: the major factors<\/p>Tweet<\/a><\/blockquote>\n

These are the most outrageous cases, directly affecting thousands of (sometimes dozens and hundreds of thousands, or even millions) people around the globe.<\/p>\n

But there are always more subtle \u2013 and less public \u2013 incidents happening, and they don\u2019t attract the same amount of attention as the\u00a0Sony Megahacks<\/a>, but they still lead to leaks of data or financial losses.<\/p>\n

What can be done to minimize the risks of \u201ccommon mistakes\u201d made by employees? Take a look at our practical guide<\/a>!<\/em><\/p>\n

Mundane examples<\/strong><\/p>\n

A high-ranking corporate officer has to handle a daunting number of various passwords; unsurprisingly he uses both his smartphone and tablet to store them. After all, he has to stay connected wherever possible, even when using a laptop isn\u2019t an option.<\/p>\n

The most common mistake even rather advanced users make is to re-use passwords for a multitude of resources. It\u2019s not as bad a mistake as using\u00a01234 as a password to a critical e-mail account<\/a>. It\u2019s probably worse.<\/p>\n

But the fact remains: According to Kaspersky Lab\u2019s surveys, 59% of people fail to store their passwords securely, 63% use \u201ceasy-to-guess\u201d passwords and up to 39% use the same combination for all their accounts. In case hackers get one such password, the domino effect begins.<\/p>\n

Most of the time the reason for a breach can be described with just three words. #enterprisesec<\/p>Tweet<\/a><\/blockquote>\n

\"wide2\"<\/p>\n

Mobiles are everywhere, and so are the risks attached. Reducing them may seem daunting, but, as our new Practical Guide shows, they are not that much of a chore<\/a>.<\/p>\n

Yet another mundane example<\/strong><\/p>\n

A certain company CFO had some serious documents in his smartphone; someone knew about it so a busy airport and a couple of deft hands was all that was needed\u00a0to relieve him of both a device and sensitive information, which later landed\u00a0in the hands of a top bidder. An artificial scenario, perhaps, but not unrealistic. Regardless of what actually happens to the lost device, it\u2019s a risk on its own.<\/p>\n

Kaspersky Lab survey shows that 1\/3 of businesses have experienced loss or theft of staff mobile devices, and 1\/4 of those know they have lost data as a result.<\/p>\n

Just Three Words<\/strong><\/p>\n

As said before, the major factors of security breaches generally come down to just three words. What are they? \u2013 The first one is \u201cbad\u201d, the second is \u201csecurity\u201d, and the third is \u201cpolicy\u201d. i.e. misplaced rules, bad password hygiene, unprotected mobile devices, etc.<\/p>\n

But \u201cbad\u201d doesn\u2019t mean \u201cimpossible to improve.\u201d<\/p>\n","protected":false},"excerpt":{"rendered":"

Over the last few years we have witnessed a number of high-profile, large scale security breaches with quite dramatic consequences, such as massive leaks of personally identifiable data.<\/p>\n","protected":false},"author":209,"featured_media":15632,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1999,3052],"tags":[2298,422],"class_list":{"0":"post-15059","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-business","8":"category-smb","9":"tag-security-breaches","10":"tag-threats"},"hreflang":[{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/apparent-reasons-a-few-examples-of-why-it-security-breaches-happen\/15059\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/apparent-reasons-a-few-examples-of-why-it-security-breaches-happen\/15059\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/apparent-reasons-a-few-examples-of-why-it-security-breaches-happen\/15059\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/www.kaspersky.com\/blog\/tag\/security-breaches\/","name":"security breaches"},"_links":{"self":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/15059","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=15059"}],"version-history":[{"count":4,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/15059\/revisions"}],"predecessor-version":[{"id":33498,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/15059\/revisions\/33498"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/media\/15632"}],"wp:attachment":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/media?parent=15059"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/categories?post=15059"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/tags?post=15059"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}