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.


06:00 AM

A Virtual Post-It, Perhaps

Keeping all those passwords straight - not to mention secure - can suck up a lot of brain power

It's only fair to point out I don't like passwords. Oh, I understand their importance in security, but the fact is that we now have so many systems for which security is required, and such high requirements for security, that I either have to sprout a super-Mensa sort of brain to keep up with all the strong passwords, or carry around yet another piece of plastic and metal flotsam to remember them for me. I'm not really a big fan of either solution.

Of course, the fact that I think about this at all seems to put me in a different league than most people. (See Top 10 Admin Passwords to Avoid.) I've always had a system for generating passwords, one that involves stuff that I can remember but isn't obvious to anyone living outside my head. I've got to admit that even the lab passwords I work with are stronger than the strings found by the survey. I've occasionally wondered about the strength of my passwords, but after reading what Bruce Schneier had to say on the subject, I felt much better.

The point is that it isn't all that hard to find passwords that can be remembered and are reasonably secure. It does take paying attention to the issue and not blowing it off by repeating your username or the first six keys on any row of the keyboard. It also means making sure that the password for your network infrastructure equipment isn't on this list.

We do a lot of intrusive, irritating things in the name of security. Making sure our passwords are worth having shouldn't be on that list of things. But it should absolutely be on the list of things that we care enough about to get right.

— Curt Franklin is an enthusiastic security geek who used to be one of the Power Rangers (the red one, we think). His checkered past includes stints as a security consultant, an IT staffer at the University of Florida, security editor at Network Computing, chief podcaster for CMP Technology, and various editorial positions at places like InternetWeek, Byte, and Hog Monthly. Special to Dark Reading.

Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
Inside the Ransomware Campaigns Targeting Exchange Servers
Kelly Sheridan, Staff Editor, Dark Reading,  4/2/2021
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
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
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.2.0, BinaryHeap is not panic-safe. The binary heap is left in an inconsistent state when the comparison of generic elements inside sift_up or sift_down_range panics. This bug leads to a drop of zeroed memory as an arbitrary type, which can result in a memory ...
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, String::retain() function has a panic safety problem. It allows creation of a non-UTF-8 Rust string when the provided closure panics. This bug could result in a memory safety violation when other string APIs assume that UTF-8 encoding is used on the sam...
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, VecDeque::make_contiguous has a bug that pops the same element more than once under certain condition. This bug could result in a use-after-free or double free.
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.50.0, read_to_end() does not validate the return value from Read in an unsafe context. This bug could lead to a buffer overflow.
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.52.0, the Zip implementation has a panic safety issue. It calls __iterator_get_unchecked() more than once for the same index when the underlying iterator panics (in certain conditions). This bug could lead to a memory safety violation due to an unmet safety r...