3 ms·
Composition policies seem to be one of the hardest things to stamp out, as is evident here where ~45% of top sites still use them. I got to talking about these
by zamadatix 4y ago
Composition policies seem to be one of the hardest things to stamp out, as is evident here where ~45% of top sites still use them.
I got to talking about these types of policies with a friend who was asking about revamping the requirements at their company. I talked through it all, showed the math, showed how few extra minimum characters it takes to blow out all of the common complexity rules, talked about the simplicity, showed the latest research and recommendations from respected bodies, and in the end they still implemented them. Why? It'd be hard to explain the change to management and there was fear the users would be upset upon seeing the couple extra character requirement since they are already used to the complexity rules. Somewhat the "security theater" note in the conclusion but probably also a little bit of not wanting to argue with the Deloitte types of the world also mentioned in the conclusion. On the bright side they did at least add blocklists.
It would have been interesting to see information on MFA in the dataset though. The paper notes MFA may be a reason sites have shifted their attention away from password security but seems to have skipped MFA during the data gathering process making it hard to say much about it. Beyond security strength MFA is also a powerful tool to attack another password policy problem - expirations. It allows you to answer the question of "how long should it be acceptable for an advisory to have access to a compromised account" with "it isn't" instead of "6 months" or whatever the annoying policy is. And sure, improperly implemented/insecure MFA could be a whole paper itself, but it's hard to make claims of how many sites have weak/strong password policy without at least a cursory look at that path.
- xyzzy123 4y agoNIST have updated their password advice but it's still not flowed through to other places like PCI, Australian ISM or tons of other standards. If you're setting an org-wide policy it should (at least in theory) comply with the intersection of all the other crappy standards you're stuck with.... which means password complexity and pointless expiration requirements for at least a few more years :-/ The paperwork/compliance lag issue mainly affects internal systems and directory, but can flow on to public sites as well.