Account/Authentication - Azure Active Directory - Ensure that Password Protection is Enabled for Active Directory

By Ashwin Venugopal -

 







Summary

If Azure Active Directory Password Protection to Active Directory is enabled, then, it will help in protecting against the use of common passwords. However, this recommendation applies to Hybrid deployments only, and will be of no use unless working with on-premises Active Directory.

Reason

As Azure Directory protects an organization against the use of weak or leaked passwords and also helps them in creating a list of custom banned passwords to prevent their users from using easily guessed passwords that are specific to their industry; deploying this feature to Active Directory will strengthen the passwords that are used in the environment.

What If?

The end result of this setting highly depends upon existing password policies in place in the environment, hence, those with stronger password policies in place, will be affected minimally, while, those without them will have to implement Azure Active Directory Password Protection for users to change and adhere to more stringent requirements than they have been accustomed to.

How to?

To setup Azure Active Directory Password Protection, use the following steps:
  1. Download and install the Azure AD Password Proxies and DC Agents from https://www.microsoft.com/download/details.aspx?id=57071
  2. After completing the installation, login to https://admin.microsoft.com as a Global Administrator.
  3. Go to Admin centers and click on Azure Active Directory.
  4. On the left side navigation select Azure Active Directory and then Security followed by Authentication methods.
  5. Now, choose Password protection and toggle enable password protection on Windows Server Active Directory to Yes and Mode to Enforced.
  6. Now, click Save at the top of the right pane.

      
Monitor:

To verify that Azure Active Directory Password Protection is enabled, use the Microsoft 365 Admin Center:
  1. Login to https://admin.microsoft.com as a Global Administrator.
  2. Go to Admin centers and click on Azure Active Directory.
  3. On the left side navigation select Azure Active Directory and then Security followed by Authentication methods.
  4. Now, choose Password protection and make sure enable password protection on Windows Server Active Directory is set to Yes and Mode is set to Enforced.
  5. Now, verify that the Domain Controller Agent and Proxy's are deployed to the Domain Controllers in the environment.














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