Criminals of the world would love to know that they don’t have to deal with MFA if they phish you while you’re in the office. Now we’ve taken that option away
Azure AD
19 posts
Despite criminal masterminds and “security researchers” always coming up with the next greatest tool for causing financial damage to our businesses and economy, there are patterns.
Defense implies a reactionary approach. Prevention set the scene where ransomware can’t get you in the first place.
Microsoft recently published an analysis of the techniques used by one popular phishing-as-a-service provider. We’ll take that analysis and implement a solution based upon it
Finally, there is an easy way to deploy a base set of conditional access policies to users, devices and apps in a tenant. Microsoft calls it Conditional Access Templates and you will find them in Azure AD – Security – Conditional Access – Conditional Access Templates.
There’s mandatory migration underway from SSPR and MFA settings to policy and you have until later this month to get them into place voluntarily or Microsoft will do it for you
I’m going to show you how adding a single word to a user’s profile in Azure Active Directory (Azure AD) can kick off an entire onboarding process and move user add/remove from an IT task into an administrative assistant task.
We have a sustained 100% secure score in Identity Security and you can too. There’s an actual method and implementation process
Azure AD creates its own password policy. It’s a secure by default item
The Risky User report is useful sure, but wouldn’t it be better if you didn’t have to remember to see if any users have been flagged as Risky?