![]() Office 2010 does not support modern authentication. If you have Office 2013, you can enforce modern authentication, but you have to update the registry. There's a number of reasons why you might need to add those exceptions and have that support there. They're probably using SMTP authentication. What about printers or multifunction devices where you scan it and have the PDF emailed. If you have older PowerShell scripts, they're going to be using some of those legacy authentications, especially if you're going against Exchange. Microsoft recommends that if you have complex security requirements, using conditional access, or you have Azure active directory premium, that you not use security defaults and use conditional access instead. It's tenant wide - so it is imperative to make sure you know if users aren't using it. But why wouldn't you just enable security defaults? ![]() It also protects privileged activities like access to the Azure portal. It blocks legacy protocols, requiring users to perform multifactor authentication when necessary. It requires administrators to use multifactor authentication. 80% of accounts and organizations that have disabled legacy authentication experience 67% fewer compromises, then those where it is enabled.99% of password spray attacks use legacy authentication protocols.Legacy authentication - what is it? It's essentially any mechanism that does not support multifactor authentication (MFA) or modern authentication.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |