And the Custom banned password list of #Microsoft #Entra ID #Password Protection just continues the joke.
First, it can only contain 1000 entries. And yes, I really don't want to manage a big custom list.
And it gets even worse. The list is intended to contain company specific banned words like brand or product names, company-specific internal terms as well as abbreviations. Entries must be at least 4 characters.
WTF, half the companies I worked for had 3 letter names. And there are many other BWM, KIA, SAP, IBM, GM, BBC, NBA, NFL, UPS, DHL, ...
And don't get me started on acronyms. #TLA (Three-Letter-Acronym) is a term for a reason.
This means, taking my current company as an example, that SMA12 would be an accepted password (if it would be for the length) because 'SMA' 3 points + '12' 2 points is 5 points).
To reach the necessary length you could simply combine it. E.g. 'SMASolar1' would be an accepted password even if 'Solar' was a banned word.
And I CAN'T do ANYTHING!!!
Or at least not anything sensible. If I start to put combinations of 'SMA*' in the custom banned pw list, I'm back at an inadequate big list I have to manage myself
.
And even then SMASolar1234 stays valid
#Cybersecurity #Fail #SecurityFail
Call for #Help: I would be very happy if someone can show me that I'm wrong. The state of Microsoft Entra ID Password Protection is a MUCH bigger pain than that I would have been wrong
.