About Us | Contact Us
View Cart

The Password Manifesto Revisited

By Dan Hadaway | Tuesday, May 19, 2015 - Leave a Comment

Password aging should be retired, usually . . .


There is never 100%, even in manifestos!
Another one of those Dan’s New Leaf Posts, meant to inspire thought about IT Governance . . . .


ServIcons_ITAudit_01

So several years back I became known as the auditor who had the audacity to propose that Password Aging was an aged control.  If you don’t know what I mean by password aging, you  could read that article.  But know by the end of this article you’ll have a very good understanding of “aging as a control.”

Since that manifesto, audit Clients everywhere would rejoice as we suggested they tighten other password management controls and then consider lengthening their aging requirements.

That was then.  This is now.

And I still stand by the entire philosophy.   With a twist though.

The twist is really a reminder.  I said “sometimes.”  The twist is this:  Password Aging can sometimes still be an effective control.

More importantly, let’s be teaching our users that password resets should be triggered, not periodic, and in some cases password aging is still an effective control.

Let me explain:

I still maintain that requiring people to change their passwords only increases the likelihood they’ll fight the system, write it down, or whatever.  And now that we all know how to use very strong passwords, pass phrases, and random password generators, the need to change passwords to protect against CRACKING does not justify the cost.

When I heard about the Anthem breach, I did not need to change all my other passwords because I didn’t even remember my Anthem password.  It was not a “theme password,” meaning that it did not have any core passwords (if you’re still not following me you really need to toss in the towel and read my original article.)  I am very organized about my passwords so I knew that, from an authentication perspective, the Anthem breach did not compromise all my other passwords.

However, I did use, a few years back, a certain “core” for my “entertainment” passwords.  Thus, when StubHub was breached, I had to change my password on Ticketmaster, whitesox.com, and the Todd Rundgren website.  Since then I started using random passwords and thus the second time Ticketmaster was breached was only the second time I had to change the password there.

The point being is that the need to change your password is a “triggered need.”  It should be caused by you remaining aware of the health of the systems you have placed confidential information, and if you think somebody has compromised your password, change it.  If you hear that a system was compromised and the password you are using there, or any part of it, may have been compromised, change that password.

Is there still a good use for “password aging” . . . . periodic required password changes?  Yes!  My mother is a bit trusting of people, and has twice now fell pray to credit card pretext calling scams.  So we now change her credit card number bi-annually.  More instructive, we also change our own credit card at infotex once per year.  The security benefits of this are still probably low, but the non-security benefits (that our contracts don’t auto-renew because our credit card has changed) is still worth the effort.

And to protect against bad threat intelligence (you not hearing about the breach of a system that has passwords you use in other systems), password aging is an  effective control.  So a balance needs to be stricken between the cost of changing your password every 42 days and the risk of not changing your password ever.

The point being is that there is never 100% in security.  That’s why we work in layers of controls.  If you’re using the same password everywhere, 42 days is probably too long now that the companies who ignored security are being hacked.  But if you are using strong passwords, unique to each asset, and you are watching the breach news . . . . your aging can be as long as six months, in this auditors’ opinion.

The title of my manifesto is Sometimes Say Never.  Yes, in general password aging is not an effective control.  But in specific situations, it still makes sense.

And password aging makes a great illustration of how the strength of, and need for, any individual control depends greatly upon the entire control structure.


Original article by Dan Hadaway CRISC CISA CISM. Founder and Managing Partner, infotex

“Dan’s New Leaf” is a “fun blog to inspire thought in the area of IT Governance.”

 


same_strip_012513


 

Latest News
    A Webinar-Movie What are the top seven risks your board should know about in 2022? Since his first board presentation in 2000, when Dan presents audit reports to boards of directors, he also talks to the board about the top risks the institution is facing. Since 2006, Dan has been compiling a list of the […]
    Seven Trends . . . that small bank Information Security Officers face in 2022 Another one of those Dan’s New Leaf Posts, meant to inspire thought about IT Governance . . . . Welcome to the Magnificent Seven, my annual predictive article about the seven trends in technology that will impact the Information Security Officers of […]
    Another awareness poster for YOUR customers (and users).  Now that we have our own employees aware, maybe it’s time to start posting content for our customers! Download the large versions here: Awareness Poster (Portrait) Awareness Poster (Landscape)   You are welcome to print out and distribute this around your office. Interested in one of ours […]
    Millions of phishing emails will get through automated defenses this year, are your employees ready? An article review. With cybersecurity threats such as cryptocurrency miners and ransomware seeming to dominate the news, it can be easy to forget about older threats such as phishing…but a recent report from cybersecurity firm Tessian reminds us that criminals […]
    The FFIEC’s latest guidance: The Architecture, Infrastructure, and Operations, has brought many changes to exactly how a small financial institution may look at their Technology Planning for 2022. Included in that will be the opportunity to write your first Architecture Plan and we intend to show you what may be involved in that! Have any […]
    While we’re not a news service, we often use current events to comment on trends and our services. This blog is intended to get people thinking about topics and trends in Technology Risk Management, through our article reviews, as well as through original blog articles about current events and our MSSP services (such as our […]
    Following the contribution, Have I Been Pwned will host more than 800 million compromised credentials… An article review. Have any of your login credentials been revealed in a breach?  If you’re unsure about that, Have I Been Pwned (HIBP) can help you out by letting you check against over 600 million compromised credentials…and with the […]
    infotex and Log4j We are keeping our Clients’ safety in mind. To all infotex managed security service Clients: On Friday December 10th, infotex became aware of a zero-day vulnerability in the Apache Log4j library that allows unauthenticated remote code execution. We began incident response and took steps to proactively disable potentially vulnerable applications until we […]
    Another awareness poster for YOUR customers (and users).  Now that we have our own employees aware, maybe it’s time to start posting content for our customers! Download the large versions here: Awareness Poster (Portrait) Awareness Poster (Landscape)   You are welcome to print out and distribute this around your office. Interested in one of ours […]