I was so happy when we finally hired a director of security and the first thing he did was stop forcing us to rotate passwords every month.
It was so fucking insane.
I was so happy when we finally hired a director of security and the first thing he did was stop forcing us to rotate passwords every month.
It was so fucking insane.
I've done a lot of internal infrastructure pentests, for companies of various sizes, and there wasn't a single pentest where spraying MonthYYYY for the past two months wouldn't get at least one hit.
That, and the fact that every company has at least one server hidden somwhere that's still vulnerable to MS17-010, that they can't update or replace for one reason or the other.
I assume if special characters were required then it became MonthYYYY!, yes?
You are 100% describing my company... Still relying on SMB1 protocols and a "server" running windows XP in a closet somewhere. But we have 4 different passworded accounts minimum to do our job, and they all rotate at different times and can't reuse varying amounts of previous passwords and have different requirements to be accepted... It is a nightmare to the point everyone just saves their passwords to the browser and/or write them on a pad of paper sitting on their desk. This includes computers that are in an area open to the public that anyone could just walk up and start using.
That is an absolute nightmare.
Yup. And all of this was at the recommendation of the million dollar security consultant we hired to get us out of the ransomware attack because we still have people that open all e-mail attachments.
I'm pretty sure we ended up trying to pay the ransom but it didn't actually work, lol.
It makes me smile a little to know that the spirit of ms08-067 still lives on in some way.
I was pretty sure that was eternal blue but didn't believe it would still be relevant 10 years later.
Capital letter at the start. Numbers at the end. Exclamation point at the very end.
It's scary that this is a pattern so many of us does instinctually.
It's a good thing I began using KeePassXC 2 years ago..
here is the thing about working at a corp. I ask IT if there is a vetted password manager to use. They say they don't have one. If I use one now im storing company passwords on unvetted software. thing is the corp has you do all this training and have you sign off you will keep to its guidelines.
Same. Where I work everyone switched to storing them in Excel.
yeah it kinda drives me bonkers. there is a security team and they have all sorts of things that don't always make the most sense but they don't insist the company get a centralize password manager solution.
Mine're in onenote. First page in the section I have for each app. If they don't have obscene password requirements that force me to generate random ones they're in code at least. Otherwise... plain text.
Came to the comments and you were downvoted?
Downvoter, what's the problem with these tools?
They'll never figure out my secret technique... TWO exclamation points!!
All this is correct. But I’ll also add the following:
Most people probably DGAF if their password for work is compromised. They have no skin in the game for whatever their data entry or email is for BigCorp, they’re treated like “monkey push button, monkey get banana,” forced to jump through password hoops and they’re sick of doing it every few weeks or months. So they use the simplest they can get away with and the easiest to remember so they don’t have to call some corpo IT help desk that will roll their eyes at yet another password reset.
Every competent InfoSec dept knows that NIST recommenda a strong password you never rotate unless compromised and yet every corporate policy I've ever witnessed forces password rotation constantly.
Security is 100% theatre.
Don't let the user choose their password. Use passkey and randomly generate a secure password. Encourage passwordless login.
This leads to endless resets as users fail to manage the unmemorizeable passwords, which as you probably know, exposes these kinds of users to new risks via email etc..
I do the exlamation mark thing!!!
Damn, someone figured out my super secret formula for making super strong passwords! What am I going to do‽
new policy: your password must not have been used by any other user in our system. That’s it.
"Sorry, you can't have that password. Someone else''s already using it" is an amazingly useful piece of information to give someone, even an existing employee.
No shit, Sherlock (c). I know nothing about cyber security and even I read somewhere years ago exactly the same: forcing password rotation with complexity rules does not make anything more secure
Yea it does one thing.
It hides exactly when there was a breach somewhere that forced a password reset.
all 55 comments