defensivedepth07/05/2022, 11:22 PM
(ie requiring mixed character types) as a security best practice has been deprecated in favor of minimum password length (as well as a few other controls) by NIST (see section 188.8.131.52 Memorized Secret Verifiers) and the wider InfoSec community for a few years now - and I would like to tweak the complexity requirements for my deployments to be more inline with this.
Guillaume07/06/2022, 1:11 AM
defensivedepth07/06/2022, 11:25 AM
The core of the issue is that we should be trying to guide people into using passphrases (with no complexity rules other than minimum length). The other key controls are: • MFA for non-SSO • Rate-limiting (exists already in FleetDM) • Disallow-list check (ie using haveIbeenpwned offline check or something similar) - https://haveibeenpwned.com/Passwords
When users create and change memorized secrets: - Clearly communicate information on how to create and change memorized secrets. - Clearly communicate memorized secret requirements, as specified in Section 5.1.1. - Allow at least 64 characters in length to support the use of passphrases. Encourage users to make memorized secrets as lengthy as they want, using any characters they like (including spaces), thus aiding memorization. - Do not impose other composition rules (e.g. mixtures of different character types) on memorized secrets. - Do not require that memorized secrets be changed arbitrarily (e.g., periodically) unless there is a user request or evidence of authenticator compromise. (See Section 5.1.1 for additional information).
Guillaume07/06/2022, 4:17 PM
Mystery Incorporated07/07/2022, 5:10 AM
defensivedepth07/07/2022, 11:59 AM