This has been in their guidance since at least 2017.
"Verifiers SHOULD NOT impose other composition rules (e.g., requiring mixtures of different character types or prohibiting consecutively repeated characters) for memorized secrets. Verifiers SHOULD NOT require memorized secrets to be changed arbitrarily (e.g., periodically). However, verifiers SHALL force a change if there is evidence of compromise of the authenticator"
Also worth pointing out that NIST doesn't set policy, so unfortunately this doesn't directly "forbid" anything, though many other policies reference 800-63.
Are you referring to the first amendment? If so, this allows you to speak against the government. It doesn't prevent you from entering optional contracts.
I'm not making any statement about the morality, just that this is not a 1a issue.
Apparently I phrased my response poorly. I was responding to the narrow context of the idea that devs aren't using Azure VMs instead of Macs. I was not disputing the popularity of Azure.
Of the organizations that have Exchange Server on premises, I'd bet the lions share are hybrid, with regular user mailboxes in the cloud, using the server(s) for application relays, etc.
Not sure if I'm missing your intentional irony, but NIST was one of the best places to send folks who think user password rotations are a good idea.
I said "was" because pretty much everyone has now caught up, but NIST updated guidance shortly after big breaches were able to be studied.
> Verifiers SHOULD NOT impose other composition rules (e.g., requiring mixtures of different character types or prohibiting consecutively repeated characters) for memorized secrets. Verifiers SHOULD NOT require memorized secrets to be changed arbitrarily (e.g., periodically). However, verifiers SHALL force a change if there is evidence of compromise of the authenticator
The factors are:
- Something you know
- Something you have
- Something you are (biometrics)