News for hackers. Stuff that matters.
Re:Slack Security Incident by bmurphy1976 on Friday July 19, 2019 @12:04PM (#20479755)
The correct answer is routine password rotation, but of course that's stupidly hard to do.
Re:Slack Security Incident by eeeeeeeeeeeee on Friday July 19, 2019 @12:59PM (#20480402)
I don’t agree with that. Regular password rotation increases the opportunity for phishing attacks because people become used to sleep walking through it. And users are generally just adding one or two characters to the password anyway.

Instead, that energy is better spent on requiring strong passwords and people using password managers and two-factor.

Re:Slack Security Incident by pmh on Friday July 19, 2019 @01:42PM (#20480817)
Password rotation in this context is for the infrastructure, not normal user accounts.

There are other options for securing/managing infrastructure access (e.g. PKI, Hashicorp Vault), but if you're using passwords, it's a good idea to rotate them if only to encourage good practices around automation.

Re:Slack Security Incident by bmurphy1976 on Saturday July 20, 2019 @09:52AM (#20485740)
I'm not referring to user accounts, I'm referring to password management for things such as database and/or internal APIs.