{"id":2229,"date":"2020-10-21T11:14:20","date_gmt":"2020-10-21T10:14:20","guid":{"rendered":"http:\/\/www.intelligentcio.com\/apac\/?p=2229"},"modified":"2020-10-21T15:10:51","modified_gmt":"2020-10-21T14:10:51","slug":"keep-learning-at-the-forefront-to-sharpen-employees-cybersecurity-skills","status":"publish","type":"post","link":"https:\/\/www.intelligentcio.com\/apac\/2020\/10\/21\/keep-learning-at-the-forefront-to-sharpen-employees-cybersecurity-skills\/","title":{"rendered":"Keep learning at the forefront to sharpen employees\u2019 cybersecurity skills"},"content":{"rendered":"\n

Jason Whyte, MD Trustwave A\/NZ explains how technology leaders can ensure the work practices of their colleagues do not put their company\u2019s cybersecurity at risk.<\/em><\/p>\n\n\n\n

If you want to ensure work practices deliver on cybersecurity, you need to ensure you don\u2019t build an environment of fear around it. <\/p>\n\n\n\n

While the consequences of a breach can be severe, you should encourage transparency and openness in your colleagues. After all, they are often the front-line in understanding what risks your company is actually facing in its real-world, day-to-day operations.<\/p>\n\n\n\n

To quote Frank Herbert\u2019s Dune: \u2018Fear is the mind killer\u2019. It is better for cybersecurity to be boring than terrifying. Fear is also the communication killer and open internal communications regarding your team\u2019s business practices is critical to determining where any potential issues lie and then appropriately dealing with them.<\/p>\n\n\n\n

The core principle should be \u2018make the secure way the easy way.\u2019 When the pandemic hit and people started using unauthorized cloud services it wasn\u2019t because they were being mischievous or wilfully trying to put the company at risk, they were trying to do their job the best they could – and those cloud services were the fast-track to doing that. If the easy way was a secure cloud service that worked for them, there would never have been a problem in the first place.<\/p>\n\n\n\n

Prohibitions of certain behavior without thinking about the consequences will almost always go wrong. If you need someone to get a large file from Point A to Point B, but there is no authorized file sharing service and you have also banned USB drives, you\u2019re eventually going to have a bad day.<\/p>\n\n\n\n

As technology leaders, here are three key points worth following:<\/p>\n\n\n\n

        (a) Understand the work practices of our colleagues, in very practical and realistic terms<\/p>\n\n\n\n

        (b) Have an amnesty to get people to \u2018fess up to non-compliant stuff they do without fear of getting in trouble<\/p>\n\n\n\n

        (c) Put in place enabling technologies with proper security that address (a) and (b)<\/p>\n\n\n\n

For example, if you give someone a popup that says: \u2018Would you like to be secure today, yes\/no\u2019, everyone will click \u2018yes\u2019\u2026 unless the implication of clicking \u2018yes\u2019 is that half their applications don\u2019t work\u2026 in which case they\u2019ll click \u2018no\u2019. Think like them and security and best business practices will follow.<\/p>\n\n\n\n

And keep learning at the forefront. A work environment that remains open to learning about possible risk will invariably reduce that risk when it finds it. The best source of information on non-compliance and on risky business practices, is simply asking employees and supporting their awareness, not punishing it. <\/p>\n\n\n\n

You want your colleagues to push the envelope when it comes to getting important work done. We all know shortcuts will sometimes happen. We just need to make it OK for them to tell us.<\/p>\n","protected":false},"excerpt":{"rendered":"

Jason Whyte, MD Trustwave A\/NZ explains how technology leaders can ensure the work practices of their colleagues do not put their company\u2019s cybersecurity at risk. If you want to ensure work practices deliver on cybersecurity, you need to ensure you don\u2019t build an environment of fear around it.  While the consequences of a breach can […]<\/p>\n","protected":false},"author":18,"featured_media":2230,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[4,18,51,55,44,54],"tags":[174,1187,1186,1183,1185],"class_list":["post-2229","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-analysis","category-enterprise-security","category-intelligent-technology-newsletter","category-oceania","category-top-stories","category-used","tag-cybersecurity","tag-dune","tag-frank-herbert","tag-jason-whyte","tag-trustwave"],"acf":[],"publishpress_future_workflow_manual_trigger":{"enabledWorkflows":[]},"_links":{"self":[{"href":"https:\/\/www.intelligentcio.com\/apac\/wp-json\/wp\/v2\/posts\/2229","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.intelligentcio.com\/apac\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.intelligentcio.com\/apac\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.intelligentcio.com\/apac\/wp-json\/wp\/v2\/users\/18"}],"replies":[{"embeddable":true,"href":"https:\/\/www.intelligentcio.com\/apac\/wp-json\/wp\/v2\/comments?post=2229"}],"version-history":[{"count":5,"href":"https:\/\/www.intelligentcio.com\/apac\/wp-json\/wp\/v2\/posts\/2229\/revisions"}],"predecessor-version":[{"id":2253,"href":"https:\/\/www.intelligentcio.com\/apac\/wp-json\/wp\/v2\/posts\/2229\/revisions\/2253"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.intelligentcio.com\/apac\/wp-json\/wp\/v2\/media\/2230"}],"wp:attachment":[{"href":"https:\/\/www.intelligentcio.com\/apac\/wp-json\/wp\/v2\/media?parent=2229"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.intelligentcio.com\/apac\/wp-json\/wp\/v2\/categories?post=2229"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.intelligentcio.com\/apac\/wp-json\/wp\/v2\/tags?post=2229"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}