{"id":45684,"date":"2022-09-27T13:03:53","date_gmt":"2022-09-27T17:03:53","guid":{"rendered":"https:\/\/www.kaspersky.com\/blog\/?p=45684"},"modified":"2022-09-27T13:03:53","modified_gmt":"2022-09-27T17:03:53","slug":"ex-employees-access","status":"publish","type":"post","link":"https:\/\/www.kaspersky.com\/blog\/ex-employees-access\/45684\/","title":{"rendered":"Might your ex-employees still have access to corporate data?"},"content":{"rendered":"<p>How confident are you that your former employees no longer have access to corporate information? As practice shows, this isn\u2019t an irrelevant question. Recently, our colleagues <a href=\"https:\/\/www.kaspersky.com\/blog\/smb-cyber-resilience-report-2022\/\" target=\"_blank\" rel=\"noopener nofollow\">analyzed<\/a> how well small and medium-sized businesses (SMBs) are prepared for cyberincidents in an unpredictable world. The study found that nearly half of the SMBs surveyed were not 100 percent sure that dismissed employees could not still access their business data through cloud services or corporate accounts.<\/p>\n<h2>What harm can an ex-employee with access to corporate data do?<\/h2>\n<p>If an ex-employee still has access to work services or information systems, they could do plenty of harm to their former employer \u2013 should that float their boat. SMBs usually worry about fairly phantom threats, such as a former employee using corporate data to launch their own rival business or taking a job with a competitor and stealing the company\u2019s customers. But in terms of business damage, these are way down the list.<\/p>\n<p>If an ex-employee has access to a customer database that contains personal data, what they could do is leak it into the public domain (for example, as revenge for dismissal) or sell it on the dark web. For a start, that would damage the reputation of your business. Second, it could jeopardize your customers, who might take legal action \u2013 if not for damages, then at least for having their personal data leaked. Third, you could receive a hefty fine from the regulators. This latter one depends of course on the laws of the country where you operate, but there\u2019s a growing trend worldwide toward tightening the penalties for leaks of this kind.<\/p>\n<h2>Potential problems without malicious intent<\/h2>\n<p>Some issues are not the result of scheming ex-employees, or even direct leaks. An ex-colleague may not even remember they had access to such-and-such resource. But a routine check by those same regulators might reveal that unauthorized persons do in fact have access to confidential information, which would still result in a fine.<\/p>\n<p>And even if you\u2019re absolutely certain you parted ways on good terms with everyone, that doesn\u2019t mean you\u2019re out of the woods. Who can guarantee they didn\u2019t use a weak or non-unique password to access work systems, which attackers could brute-force or come across in an unrelated leak? Any redundant access to a system \u2013 be it a collaborative environment, work e-mail or virtual machine \u2013 increases the attack surface. Even a simple chat among colleagues about non-work issues could be used for social-engineering attacks.<\/p>\n<h2>How to minimize the risks<\/h2>\n<p>Most of the measures to combat data leaks through ex-employees\u2019 accounts are organizational. Thus, we recommend:<\/p>\n<ul>\n<li>Minimizing the number of people with access to important corporate data.<\/li>\n<li>Setting strict access policies for corporate resources \u2013 including e-mail, shared folders and online documents.<\/li>\n<li>Keeping a strict access log: record what access was granted and to whom. Revoke it immediately if the employee leaves the company.<\/li>\n<li>Creating clear instructions for creating and changing passwords.<\/li>\n<li>Introducing regular <a href=\"https:\/\/www.kaspersky.com\/enterprise-security\/security-awareness?icid=gl_kdailyplacehold_acq_ona_smm__onl_b2b_kasperskydaily_wpplaceholder____\" target=\"_blank\" rel=\"noopener nofollow\">cybersecurity awareness training<\/a> for employees.<\/li>\n<\/ul>\n<input type=\"hidden\" class=\"category_for_banner\" value=\"kaot\">\n","protected":false},"excerpt":{"rendered":"<p>Are you sure your former colleagues don\u2019t have access to corporate data or systems?<\/p>\n","protected":false},"author":2581,"featured_media":45685,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1999,3052],"tags":[1616,2388,732],"class_list":{"0":"post-45684","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-business","8":"category-smb","9":"tag-access","10":"tag-employees","11":"tag-research"},"hreflang":[{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/ex-employees-access\/45684\/"},{"hreflang":"en-in","url":"https:\/\/www.kaspersky.co.in\/blog\/ex-employees-access\/24670\/"},{"hreflang":"en-ae","url":"https:\/\/me-en.kaspersky.com\/blog\/ex-employees-access\/20137\/"},{"hreflang":"en-us","url":"https:\/\/usa.kaspersky.com\/blog\/ex-employees-access\/27123\/"},{"hreflang":"en-gb","url":"https:\/\/www.kaspersky.co.uk\/blog\/ex-employees-access\/25004\/"},{"hreflang":"es-mx","url":"https:\/\/latam.kaspersky.com\/blog\/ex-employees-access\/25348\/"},{"hreflang":"es","url":"https:\/\/www.kaspersky.es\/blog\/ex-employees-access\/27747\/"},{"hreflang":"tr","url":"https:\/\/www.kaspersky.com.tr\/blog\/ex-employees-access\/11065\/"},{"hreflang":"fr","url":"https:\/\/www.kaspersky.fr\/blog\/ex-employees-access\/19533\/"},{"hreflang":"pt-br","url":"https:\/\/www.kaspersky.com.br\/blog\/ex-employees-access\/20105\/"},{"hreflang":"de","url":"https:\/\/www.kaspersky.de\/blog\/ex-employees-access\/29341\/"},{"hreflang":"ja","url":"https:\/\/blog.kaspersky.co.jp\/ex-employees-access\/32629\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/ex-employees-access\/31064\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/ex-employees-access\/30773\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/www.kaspersky.com\/blog\/tag\/access\/","name":"access"},"_links":{"self":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/45684","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\/2581"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/comments?post=45684"}],"version-history":[{"count":2,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/45684\/revisions"}],"predecessor-version":[{"id":45687,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/45684\/revisions\/45687"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/media\/45685"}],"wp:attachment":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/media?parent=45684"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/categories?post=45684"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/tags?post=45684"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}