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.

Risk

12/9/2015
01:50 PM
Connect Directly
Twitter
RSS
E-Mail
50%
50%

The Employee Password Habits That Could Hurt Enterprises

While education and efforts around online credentials are improving, password hygiene still has problems
Previous
1 of 10
Next

The lines drawn between personal digital space and work digital space are all but disintegrated as the traditional 40-hour work week in a confined office dissolves away in this gig economy. This makes life difficult when it comes to accessing and securing data. A survey out recently by Ping Identity shows how even though companies my have good credential policies in place, and employees are made aware of security, their password safety still lags. Here's a look at some of the relevant stats. 

 

Ericka Chickowski specializes in coverage of information technology and business innovation. She has focused on information security for the better part of a decade and regularly writes about the security industry as a contributor to Dark Reading.  View Full Bio

Previous
1 of 10
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
12/20/2015 | 4:52:52 PM
Recipe for disaster
The password-changing policy is possibly the worst.  It makes no account for employees who actually have strong passwords and also fails to take into account actual risk.  That's how you get simple-to-guess/hack passwords.
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
12/20/2015 | 4:51:34 PM
Re: Nice compliation of bad habits and statistics
Not to mention family members and friends who may become aware of their loved ones' passwords in other ways.

I once went on a date with someone who told me that because of her company's onerous password-changing requirements, she always just did a minor variation of the same (easy-to-guess) word.
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
12/20/2015 | 4:49:50 PM
Re: We're all guilty
This is exactly why many security experts today advise what was once taboo advice -- that people write down their passwords, specifically to allow for greater complexity and entropy.  Better you write down your password and keep it in a secure place (for instance, not on a sticky note on your computer monitor) and it be super hard to remember than have an easy to remember (and easy to guess/hack) password that you don't write down.
RyonKnight
100%
0%
RyonKnight,
User Rank: Strategist
12/16/2015 | 3:29:56 AM
All on one page please
Article on one page please.  I'd like to read it but I'm not clicking through 10 pages.
BarbaraJohnson
50%
50%
BarbaraJohnson,
User Rank: Author
12/12/2015 | 7:22:21 PM
Nice compliation of bad habits and statistics
I especially like "*54% of employees share login information with family members so they can access their computers, smartphones and tablets" It's a good specific point to add into user awareness material.
Whoopty
50%
50%
Whoopty,
User Rank: Ninja
12/10/2015 | 7:34:49 AM
We're all guilty
I bet we're all guilty of something on this list, even those who are pretty good with password security. They're endlessly annoying though. You have to remember them, yet make them complicated and change them regularly. It's such a headache. 

The amount of services we all use now too, there's no way to remember everything. But then do you change your password storage login often? If you forget that, the pain-in-the-neck of having to reset everything is ridiculous.
News
Inside the Ransomware Campaigns Targeting Exchange Servers
Kelly Sheridan, Staff Editor, Dark Reading,  4/2/2021
Commentary
Beyond MITRE ATT&CK: The Case for a New Cyber Kill Chain
Rik Turner, Principal Analyst, Infrastructure Solutions, Omdia,  3/30/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-23381
PUBLISHED: 2021-04-18
This affects all versions of package killing. If attacker-controlled user input is given, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization.
CVE-2021-23374
PUBLISHED: 2021-04-18
This affects all versions of package ps-visitor. If attacker-controlled user input is given to the kill function, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization.
CVE-2021-23375
PUBLISHED: 2021-04-18
This affects all versions of package psnode. If attacker-controlled user input is given to the kill function, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization.
CVE-2021-23376
PUBLISHED: 2021-04-18
This affects all versions of package ffmpegdotjs. If attacker-controlled user input is given to the trimvideo function, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization.
CVE-2021-23377
PUBLISHED: 2021-04-18
This affects all versions of package onion-oled-js. If attacker-controlled user input is given to the scroll function, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization.