Webinar – How to manage human risk with people working from home

Webinar - How to manage human risk with people working from home

Working from home has now become the default and many organisations are expecting that their employees will continue to work from home post COVID. This  has put a huge strain on IT and Security teams as they grapple with deploying and supporting VPNs and 2FA as standard security measures to their entire workforce.

There is ample evidence to indicate that attackers are exploiting the high volume of remote users. It is now much harder to identify unusual remote logins and detect credential theft. Devices that are used to log in for the first time are no longer an anomaly and may go undetected. Security teams are managing in a world of ‘unknown unknowns’ as user behaviours and access patterns that they have not experienced before have become the ‘new normal’. 

Additionally, moving away from the perceived safety of the office network can be unsettling, especially for employees who are working from home for the first time. Many are not security trained and can be attacked by quite simple social engineering methods. COVID weaponised emails, theft of remote user credentials, SMiShing and spear phishing attacks are on the rise.

On April 29th our Chief Product & Data Officer, Dr. Shorful Islam, will be joined by two industry leaders to discuss how CISO’s and security teams should be managing human risk in these challenging times.

Our CISO panellists will be:

The webinar aims to answer the following questions:

  • What are some of the top risks posed by employees working from home?
  • How should CISOs now manage human risk, when staff are no longer physically present in the office, but are connected to the corporate network ? 
  • How are cyber criminals taking advantage of the current situation and how can organisations equip their people with the knowledge to identify and respond to cyber threats?

Subscribe for updates
Stay on top of the latest news and announcements on human risk

  • This field is for validation purposes and should be left unchanged.