{"id":2527,"date":"2020-07-28T08:59:57","date_gmt":"2020-07-28T12:59:57","guid":{"rendered":"https:\/\/zzzptm.com\/wordpress\/?p=2527"},"modified":"2020-07-28T08:59:57","modified_gmt":"2020-07-28T12:59:57","slug":"5-ways-coronavirus-remote-work-can-compromise-your-security","status":"publish","type":"post","link":"https:\/\/zzzptm.com\/wordpress\/?p=2527","title":{"rendered":"5 Ways Coronavirus Remote Work Can Compromise Your Security"},"content":{"rendered":"\n

Can coronavirus<\/a> COVID-19 impact your network? The short answer is “yes”, if your firm hastily adopts a remote<\/a> work policy<\/a> without considering some common sense<\/a> security precautions.<\/p>\n\n\n\n

1. No personal <\/strong>email<\/strong>. The only exception for this would be to contact helpdesk about being unable to access<\/a> corporate<\/a> email. Personal email is not typically set up to properly archive and retain messages that could later be subject to a legal<\/a> hold. The very use of personal email for business<\/a> purposes can potentially expose your firm to liability<\/a> costs that would exceed the value of whatever business you planned to get done.<\/p>\n\n\n\n

2. No personal file sharing<\/strong>. This is right up there with personal email. Personal anything is not allowed for business use, mmmkay?<\/p>\n\n\n\n

3. No Remote Desktop Protocol (RDP) use over unsecured Internet<\/strong>. If I had a nickel for every person that told the network team<\/a> to open up port 3389 on the firewall<\/a> so that they could work from home, I’d be comfortably well off. Yes, RDP<\/a> means you can access your desktop<\/a> or server<\/a> from home. It also opens up great work from home capabilities for attackers. They will <\/em>guess your username<\/a> and password. It’s only a matter of brute force<\/a> time.<\/p>\n\n\n\n

4. No low-security options on the VPN configuration<\/strong>. While I’ll allow you to use RDP through a VPN connection<\/a>, I’ll only allow it if your VPN<\/a> is not just secure<\/a>, not just really secure, but only if it is really really <\/em>secure. That means not just IKEv2 and the best AES<\/a> that your system will support, but also secured authentication<\/a> that uses more than a username\/password combo. Let there be a certificate<\/a> or software token<\/a> as part of 2-factor authentication.<\/p>\n\n\n\n

5. No split tunnels<\/strong>. It’s tempting to let a local ISP<\/a> handle all the Facebook<\/a> and YouTube<\/a> traffic<\/a> that users<\/a> consume in between productivity<\/a> spurts, but don’t. Either pass all that traffic through your own network<\/a>, or block it with a message that VPN bandwidth<\/a> is limited due to whatever reason you want to provide in order to justify blocking<\/a> that traffic. My point being that a split tunnel approach allows for an attacker<\/a> on the Internet<\/a> to bridge their attack<\/a> through your user’s PC.<\/p>\n\n\n\n

Can there be more possible pitfalls? Sure. These are just the five biggest ones. If your firm is anticipating a stretch where a large percentage of employees<\/a> must work remotely, then take the time to bake some security into that plan so that reducing health<\/a> risk<\/a> doesn’t increase IT risk.<\/p>\n","protected":false},"excerpt":{"rendered":"

Can coronavirus COVID-19 impact your network? The short answer is “yes”, if your firm hastily adopts a remote work policy without considering some common sense security precautions. 1. No personal email. The only exception for this would be to contact helpdesk about being unable to access corporate email. Personal email is not typically set up to properly archive and retain messages that could later be subject to […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[12],"tags":[],"class_list":["post-2527","post","type-post","status-publish","format-standard","hentry","category-security"],"_links":{"self":[{"href":"https:\/\/zzzptm.com\/wordpress\/index.php?rest_route=\/wp\/v2\/posts\/2527","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/zzzptm.com\/wordpress\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/zzzptm.com\/wordpress\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/zzzptm.com\/wordpress\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/zzzptm.com\/wordpress\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2527"}],"version-history":[{"count":1,"href":"https:\/\/zzzptm.com\/wordpress\/index.php?rest_route=\/wp\/v2\/posts\/2527\/revisions"}],"predecessor-version":[{"id":2528,"href":"https:\/\/zzzptm.com\/wordpress\/index.php?rest_route=\/wp\/v2\/posts\/2527\/revisions\/2528"}],"wp:attachment":[{"href":"https:\/\/zzzptm.com\/wordpress\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2527"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/zzzptm.com\/wordpress\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2527"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/zzzptm.com\/wordpress\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2527"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}