The guidance is fairly simple - Just Turn It On:Ģ.1.3 Ensure That Microsoft Defender for Databases Is Set To OnĢ.1.6 Ensure That Microsoft Defender for Open-Source Relational Databases Is Set To OnĢ.1.9 Ensure That Microsoft Defender for Cosmos DB Is Set To OnĢ.1.11 Ensure That Microsoft Defender for DNS Is Set To OnĢ.1.12 Ensure That Microsoft Defender for IoT Is Set To OnĢ.1.13 Ensure That Microsoft Defender for Resource Manager Is Set To On There are six new recommendations around Microsoft Defender Enterprise Mobility & Security E3 or E5.Azure Active Directory Premium P1 or P2.You will need to be in one of the following plans to leverage Conditional Access. Conditional Access lets you build policies that triggers when MFA should fire based on risk levels, signals, countries and more. The benchmark now recommends:ġ.2.1 Ensure Trusted Locations Are Definedġ.2.2 Ensure that an exclusionary Geographic Access Policy is consideredġ.2.3 Ensure that A Multi-factor Authentication Policy Exists for Administrative Groupsġ.2.4 Ensure that A Multi-factor Authentication Policy Exists for All Usersġ.2.5 Ensure Multi-factor Authentication is Required for Risky Sign-insġ.2.6 Ensure Multi-factor Authentication is Required for Azure Management MFA is an absolute no-brainer to me - you should have this running in some shape or form. I'm a big believer of the 80/20 principle - 20% of the action delivers 80% of the results. It's exactly the same here - there's some really low-hanging fruit which can take your security posture forward and help you reduce and eliminate a lot of risk. The Center for Internet Security have updated their CIS Azure Foundations Benchmark. The updates include audit and remediation steps as well as updated MITRE mappings. It weighs in at a fairly hefty 555 pages and includes 147 different recommendations.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |