{"id":23265,"date":"2021-08-10T18:08:08","date_gmt":"2021-08-10T17:08:08","guid":{"rendered":"https:\/\/www.kaspersky.co.uk\/blog\/5-reasons-not-to-use-corp-e-mail\/23265\/"},"modified":"2021-08-10T18:08:08","modified_gmt":"2021-08-10T17:08:08","slug":"5-reasons-not-to-use-corp-e-mail","status":"publish","type":"post","link":"https:\/\/www.kaspersky.co.uk\/blog\/5-reasons-not-to-use-corp-e-mail\/23265\/","title":{"rendered":"5 reasons not to use work mail for personal matters"},"content":{"rendered":"<p>Many people know that using a personal mail account for business correspondence is a bad idea, yet they see nothing wrong with using a corporate address to register on social networks, online services, and other nonwork resources. It\u2019s handy, after all, to receive all work and personal messages in one mailbox.<\/p>\n<p>That said, you\u2019d be hard-pressed to find a reputable resource recommending it. From work-life imbalance to privacy violations (management and administrators may have access to your work mail), loss of access to services in case of dismissal, and more, the reasons not to mix business e-mail with personal are legion. In fact, the first consideration that should stop an employee from using a corporate mail account for personal matters is information security.<\/p>\n<h2>1. It makes profiling easier<\/h2>\n<p>Before sending a phishing e-mail to a specific employee, cybercriminals <a href=\"https:\/\/www.kaspersky.com\/blog\/spearphishers-information\/25589\/\" target=\"_blank\" rel=\"noopener nofollow\">harvest information<\/a> online, using specialized tools to learn which address someone uses on social networks, online platforms, and so forth. Using a corporate address for nonbusiness purposes makes you easier to profile by helping attackers build a social portrait of you, thereby making you more vulnerable to spear-phishing in the first stage of an attack on the company.<\/p>\n<h2>2. It facilitates spear-phishing<\/h2>\n<p>Cybercriminals choose the tricks they think will best ensnare their victims. If they learn you\u2019ve used your corporate mail address to register elsewhere, they know you\u2019re likely to fall for a phishing e-mail. All they have to do is disguise their message as a legitimate notification from a service that you really are registered on.<\/p>\n<h2>3. It provides criminals with a smoke screen<\/h2>\n<p>Typically, all a cybercriminal needs for an attack to succeed is time. That\u2019s why many services send a note to the account holder if you or anyone else tries to log in from an unknown IP address or attempts to change the password. Of course, to get ahead of the hackers, you need to know about those warnings as soon as possible. To that end, arrange a riot of notifications in your mailbox. If you\u2019ve linked your address to outside resources, when hackers (or their bots) begin trying to brute-force your social network and other personal accounts, your inbox will quickly fill with warnings and alerts.<\/p>\n<h2>4. More mass phishing and malware in the inbox<\/h2>\n<p>When it comes to securing customers\u2019 data, not all online resources were born equal \u2014 hence the near-daily headlines about online leaks. And leaked databases are very popular with mass spammers, who simply buy lists of addresses to flood with malicious links or phishing messages. Essentially, the more resources you tie to your corporate mail account, the more potential threats you\u2019ll see in your inbox.<\/p>\n<h2>5. The eyes glaze over<\/h2>\n<p>Speaking of seeing more messages in your inbox, that extra volume can lead to trouble. With greater variety \u2014 for example, nonwork e-mails among business messages \u2014 dangerous items become harder to spot. The more personal e-mails you read during business hours, the more likely you are to accidentally click on a malicious attachment or follow a phishing link.<\/p>\n<p>Even if you don\u2019t use a work address for personal matters, it\u2019s important to deploy technical means to protect against spam and phishing. The more layers of protection, the better. We recommend securing the corporate infrastructure against phishing at both the <a href=\"https:\/\/www.kaspersky.com\/small-to-medium-business-security\/mail-server?icid=gb_kdailyplacehold_acq_ona_smm__onl_b2b_kasperskydaily_wpplaceholder____ksms___\" target=\"_blank\" rel=\"noopener nofollow\">mail server<\/a> and the <a href=\"https:\/\/www.kaspersky.co.uk\/small-to-medium-business-security?icid=gb_kdailyplacehold_acq_ona_smm__onl_b2b_kasperskydaily_wpplaceholder_______\" target=\"_blank\" rel=\"noopener\">workstation <\/a> levels.<\/p>\n<input type=\"hidden\" class=\"category_for_banner\" value=\"kesb-trial\">\n","protected":false},"excerpt":{"rendered":"<p>Why using a corporate mail account for personal matters is not a good idea<\/p>\n","protected":false},"author":2598,"featured_media":23266,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1836,2360,2361],"tags":[1640,76,990],"class_list":{"0":"post-23265","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-business","8":"category-enterprise","9":"category-smb","10":"tag-e-mail","11":"tag-phishing","12":"tag-spear-phishing"},"hreflang":[{"hreflang":"en-gb","url":"https:\/\/www.kaspersky.co.uk\/blog\/5-reasons-not-to-use-corp-e-mail\/23265\/"},{"hreflang":"en-in","url":"https:\/\/www.kaspersky.co.in\/blog\/5-reasons-not-to-use-corp-e-mail\/23184\/"},{"hreflang":"en-ae","url":"https:\/\/me-en.kaspersky.com\/blog\/5-reasons-not-to-use-corp-e-mail\/18672\/"},{"hreflang":"ar","url":"https:\/\/me.kaspersky.com\/blog\/5-reasons-not-to-use-corp-e-mail\/9314\/"},{"hreflang":"en-us","url":"https:\/\/usa.kaspersky.com\/blog\/5-reasons-not-to-use-corp-e-mail\/25201\/"},{"hreflang":"es-mx","url":"https:\/\/latam.kaspersky.com\/blog\/5-reasons-not-to-use-corp-e-mail\/22556\/"},{"hreflang":"es","url":"https:\/\/www.kaspersky.es\/blog\/5-reasons-not-to-use-corp-e-mail\/25806\/"},{"hreflang":"it","url":"https:\/\/www.kaspersky.it\/blog\/5-reasons-not-to-use-corp-e-mail\/25287\/"},{"hreflang":"ru","url":"https:\/\/www.kaspersky.ru\/blog\/5-reasons-not-to-use-corp-e-mail\/31240\/"},{"hreflang":"tr","url":"https:\/\/www.kaspersky.com.tr\/blog\/5-reasons-not-to-use-corp-e-mail\/9930\/"},{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/5-reasons-not-to-use-corp-e-mail\/41166\/"},{"hreflang":"fr","url":"https:\/\/www.kaspersky.fr\/blog\/5-reasons-not-to-use-corp-e-mail\/17449\/"},{"hreflang":"pt-br","url":"https:\/\/www.kaspersky.com.br\/blog\/5-reasons-not-to-use-corp-e-mail\/17910\/"},{"hreflang":"pl","url":"https:\/\/plblog.kaspersky.com\/5-reasons-not-to-use-corp-e-mail\/15135\/"},{"hreflang":"de","url":"https:\/\/www.kaspersky.de\/blog\/5-reasons-not-to-use-corp-e-mail\/27184\/"},{"hreflang":"ja","url":"https:\/\/blog.kaspersky.co.jp\/5-reasons-not-to-use-corp-e-mail\/31430\/"},{"hreflang":"nl","url":"https:\/\/www.kaspersky.nl\/blog\/5-reasons-not-to-use-corp-e-mail\/27393\/"},{"hreflang":"ru-kz","url":"https:\/\/blog.kaspersky.kz\/5-reasons-not-to-use-corp-e-mail\/24224\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/5-reasons-not-to-use-corp-e-mail\/29538\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/5-reasons-not-to-use-corp-e-mail\/29343\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/www.kaspersky.co.uk\/blog\/tag\/phishing\/","name":"phishing"},"_links":{"self":[{"href":"https:\/\/www.kaspersky.co.uk\/blog\/wp-json\/wp\/v2\/posts\/23265","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kaspersky.co.uk\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kaspersky.co.uk\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kaspersky.co.uk\/blog\/wp-json\/wp\/v2\/users\/2598"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kaspersky.co.uk\/blog\/wp-json\/wp\/v2\/comments?post=23265"}],"version-history":[{"count":0,"href":"https:\/\/www.kaspersky.co.uk\/blog\/wp-json\/wp\/v2\/posts\/23265\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kaspersky.co.uk\/blog\/wp-json\/wp\/v2\/media\/23266"}],"wp:attachment":[{"href":"https:\/\/www.kaspersky.co.uk\/blog\/wp-json\/wp\/v2\/media?parent=23265"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kaspersky.co.uk\/blog\/wp-json\/wp\/v2\/categories?post=23265"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kaspersky.co.uk\/blog\/wp-json\/wp\/v2\/tags?post=23265"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}