We already know the principle of hardening for on-premises systems, apps and services. Now, let’s apply it to the Microsoft cloud as well!
Sander Berkouwer shows you the default settings in Microsoft Entra ID and explains why they aren’t appropriate for all organizations. By looking under the covers of Microsoft Entra ID, you’ll know when to dial the buttons that govern guest access, app consent and access to the Azure AD admin portal. Sander sprinkles some Conditional Access, Microsoft Defender for Identity and Azure Log Analytics goodness on top of these settings to keep you on top of all things Azure AD.
Watch this session to find out:
- What happens if you use the default Microsoft Entra ID settings
- How to harden your Active Directory, Microsoft Entra ID and Microsoft 365
- How to easily track and report on security and configuration changes in Microsoft Entra ID
- How to secure the sensitive data you store in Microsoft 365