Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

News & Commentary

12/5/2019
10:00 AM
Lysa Myers
Lysa Myers
Commentary
Connect Directly
Facebook
Twitter
LinkedIn
RSS
E-Mail vvv
100%
0%

The Human Factor: 5 Reasons Why Cybersecurity Is a People Problem

The industry can only go so far in treating security as a challenge that can be resolved only by engineering.

In the early days of computing and connected devices, there was a lot we didn't yet know about designing secure products and environments. Today, there are established, well-known frameworks and lots of advice to help people protect data and devices in their care for everyone from home users to CISOs of Fortune 500 companies.

So, why is it that good security practices are rarely adopted at every level of interaction with technology? It's because we still view the issue as a technology not a people problem. Consider these four human factors that prevent the security industry from moving towards a better future.

Human Factor 1: Usability and Accessibility
There's a kind of inertia that's created by the usability patterns that are baked into popular software (including operating systems), which keeps people from choosing the most secure option because they are designed to make us flow from one app to another naturally and almost without thought. These user-friendly designs do not encourage people to be cautious or wary.

What's worse is the fact that the steps we can and should take to protect ourselves are, more often than not, designed to interrupt this flow. While this is not necessarily a bad thing, our industry still needs to understand why people are practicing poor online hygiene. It is already a Sisyphean task to make things more secure; making things less secure is like rolling that same boulder downhill. This effect is magnified for those with different accessibility requirements, such as people with vision impairment.

Human Factor 2: Cybersecurity Skills
There are many reasons that companies are having a difficult time hiring and retaining people in cybersecurity roles, starting with the widespread assumption that this is a career path suitable only for people who've been immersed in coding and mathematics since the time they could reach a keyboard.

There's also a collective perception that security people can be incredibly hostile and antisocial, especially toward newcomers. Those who decide to seek a career in infosec often find that an entry-level job requires that they already have work experience. Too often, people who actually make it into the industry (especially those from underrepresented groups) leave midcareer due to burnout, an unsupportive culture, or an ill-defined career path.

Human Factor 3: Solutions in Search of a Problem
Technological advances are typically approached as if they're all unquestionably good. We often fail to even ask whether there are downsides to these innovations, much less whether we can mitigate the damage after the fact. At the very least, we should all assume that any given product or service will eventually be misused, no matter how beneficial its original intent.

Human Factor 4: One Size Does Not Fit All
If you've ever gone to battle with your IT department over a policy that treats all employees as if their job functions were identical, you'll understand how frustrating such a cookie-cutter approach can be. Asking people to mold their life or job circumstances to fit a security policy is simply unrealistic. Doing so is a recipe for reduced productivity, and may strongly contribute to employee burnout.

Human Factor 5: Broadening Our Experience and Knowledge Base
The good news is that human problems are neither new nor unique to tech. There are entire industries that focus on studying human behavior, and there are people who specialize in the concerns of marginalized or vulnerable populations. Ideally, we should all be hiring people from these populations. But hiring challenges sometimes mean that there is work to be done on improving company culture, which experts can help with. For example, our industry has a long history of partnering with law enforcement. We should also be working with people specializing in industrial/organizational and educational psychology, as well as social workers and ethicists.

The security industry can only go so far in treating security as a problem that can be solved by engineering alone. Until we couple technology with a better understanding of the humans who are using technology insecurely, there's a limit on how much progress we can ultimately make.

Related Content:

Check out The Edge, Dark Reading's new section for features, threat data, and in-depth perspectives. Today's top story: "Home Safe: 20 Cybersecurity Tips for Your Remote Workers."

Lysa Myers began her tenure in malware research labs in the weeks before the Melissa virus outbreak in 1999. She has watched both the malware landscape and the security technologies used to prevent threats from growing and changing dramatically. Because keeping up with all ... View Full Bio
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Exploits Released for As-Yet Unpatched Critical Citrix Flaw
Jai Vijayan, Contributing Writer,  1/13/2020
Major Brazilian Bank Tests Homomorphic Encryption on Financial Data
Kelly Sheridan, Staff Editor, Dark Reading,  1/10/2020
New Attack Campaigns Suggest Emotet Threat Is Far From Over
Jai Vijayan, Contributing Writer,  1/16/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: It is too bad the ceiling is made of glass!
Current Issue
The Year in Security: 2019
This Tech Digest provides a wrap up and overview of the year's top cybersecurity news stories. It was a year of new twists on old threats, with fears of another WannaCry-type worm and of a possible botnet army of Wi-Fi routers. But 2019 also underscored the risk of firmware and trusted security tools harboring dangerous holes that cybercriminals and nation-state hackers could readily abuse. Read more.
Flash Poll
[Just Released] How Enterprises are Attacking the Cybersecurity Problem
[Just Released] How Enterprises are Attacking the Cybersecurity Problem
Organizations have invested in a sweeping array of security technologies to address challenges associated with the growing number of cybersecurity attacks. However, the complexity involved in managing these technologies is emerging as a major problem. Read this report to find out what your peers biggest security challenges are and the technologies they are using to address them.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-3686
PUBLISHED: 2020-01-17
openQA before commit c172e8883d8f32fced5e02f9b6faaacc913df27b was vulnerable to XSS in the distri and version parameter. This was reported through the bug bounty program of Offensive Security
CVE-2019-3683
PUBLISHED: 2020-01-17
The keystone-json-assignment package in SUSE Openstack Cloud 8 before commit d7888c75505465490250c00cc0ef4bb1af662f9f every user listed in the /etc/keystone/user-project-map.json was assigned full "member" role access to every project. This allowed these users to access, modify, create and...
CVE-2019-3682
PUBLISHED: 2020-01-17
The docker-kubic package in SUSE CaaS Platform 3.0 before 17.09.1_ce-7.6.1 provided access to an insecure API locally on the Kubernetes master node.
CVE-2019-17361
PUBLISHED: 2020-01-17
In SaltStack Salt through 2019.2.0, the salt-api NEST API with the ssh client enabled is vulnerable to command injection. This allows an unauthenticated attacker with network access to the API endpoint to execute arbitrary code on the salt-api host.
CVE-2019-19142
PUBLISHED: 2020-01-17
Intelbras WRN240 devices do not require authentication to replace the firmware via a POST request to the incoming/Firmware.cfg URI.