Account/Authentication - Azure Active Directory - Ensure Security Defaults is Disabled on Azure AD

By Ashwin Venugopal -

 






Summary

Security Defaults easily secure and protect your organization and consists of preconfigured security settings for common attacks.

In order to ensure that all the organizations have a basic level of security-enabled at no extra cost, Microsoft is making security defaults available to everyone that can be turned on in the Azure portal.

However, their use will prohibit custom settings which are being set with more advanced settings from this benchmark.

Reason

Security Defaults offer secure default settings that can be managed on behalf of the organizations to keep customers safe until they are ready to manage their own identity security settings.

For example doing the following:

  • Requiring all users and admins to register for MFA.
  • Challenging users with MFA - mostly when they show up on a new device or app, but more often for critical roles and tasks.
  • Disabling authentication from legacy authentication clients, which can't do MFA.

What If?

Disabling of security defaults can affect your environment depending upon security controls implemented in the environment. However, most organizations implements equivalent controls to replace Security Defaults.

It may be necessary to check settings in other Microsoft products, like Azure, to ensure settings and functionality are as expected when disabling security defaults for MS365.

How to?

To disable security defaults in your directory:
  1. Sign-in to Azure portal as security administrator, Conditional Access administrator, or global administrator.
  2. Now, browse to Azure Active Directory > properties.
  3. Select Manage security defaults.
  4.  After that, set the Enable security defaults toggle to No.
  5. Finally, Save.

Monitor:

To ensure security defaults is disabled in your directory:
  1. Sign-in to Azure portal as security administrator, Conditional Access administrator, or global administrator.
  2. Now, browse to Azure Active Directory > properties.
  3. Select Manage security defaults.
  4.  After that, verify the Enable security defaults toggle to No.





































Comments

Post a Comment

Popular posts from this blog

Deployment (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Microsoft Monitoring Agent (MMA) MMA is used across multiple Microsoft solutions and has undergone a few name changes as its features and functionality have evolved. If it is being considered to be used, then following areas should be covered during a Microsoft Sentinel deployment project: Consider the timelines and the strategy for a migration to AMA (Azure Monitor Agent) before the MMA end-of-life.  Consider the central deployment and management methodology for MMA. Determine which endpoints are in scope for deployment as these affect the log ingestion volume significantly.  Azure Monitor Agent (AMA) Organizations with MMA as the main Microsoft Sentinel agent should start planning the migration to AMA as soon as possible to avoid a rushed migration. One of the main advantages of AMA is the ability to control the log collection policy centrally and apply different policies against different groups of computers, re
Read more

Project Resourcing (Part 2)

By Ashwin Venugopal -
Image
  To read part 1, please click  here Engineering - SIEM The SIEM engineers configures Microsoft Sentinel, including Log Analytics, Logic Apps, workbooks, and playbooks. They are also responsible for the following high-level tasks: Initial configuration of Azure tenant, including provisioning required resources, assigning access roles, and configuring workspace parameters like log retention, resource tagging, and blueprints.  Deployment and configuration of syslog/CEF log collection agents in appropriate locations to collect logs from on-premises devices. Generally, it will be joint effort of both system engineer and SIEM engineer, involving configuration and potential troubleshooting.  Working with system owners to enable log forwarding and configuring any required parsing of log data in Log Analytics.  Working with security operations to create and deploy KQL analytic rules to offer detections for SOC/Computer Security Incident Response Team (CSRIT) use. Tuning of alert rule parameter
Read more

Design Planning (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Complex Organizational Structures SIEM can be an expensive security control, hence, it is common multiple businesses to contribute to the overall expense. Various organizational units may require a level of access to specific dashboards or sets of data. Microsoft Sentinel offers the ability to assign table-level permissions and limit the level of access to the minimum required to perform requisite job functions.  Role-based Access Control (RBAC) Requirements Microsoft Sentinel offers an extensive list of Azure built-in roles that can be used to provide granular access according to the job requirements and permitted level of access. Some of them are various Microsoft Sentinel dedicated roles: Microsoft Sentinel Contributor- Can perform all engineering-related configuration, such as creating alert rules, configuring data connectors, and additional similar tasks.  Microsoft Sentinel Reader- Can query the log data stor
Read more