Account/Authentication - Azure Active Directory - Ensure that Office 365 Passwords Are Not Set to Expire

By Ashwin Venugopal -

 





Summary

Generally, Microsoft cloud-only accounts consists of pre-defined password policy that cannot be changed. You can only change the number of days until a password expires and whether or not passwords expire at all.

Reason

Some of the organizations like NIST and Microsoft have updated their password policy recommendations to not arbitrarily require users to change their passwords are a specific amount of time, unless there is evidence that the password is compromised or the user forget it. 

What If?

If the passwords are set not to expire, then, the other controls should be in place to supplement this setting. The following steps are recommended to be taken:

  1. Ban common passwords
  2. Educate users to not reuse organization passwords anywhere else
  3. Enforce MFA registration for all users
  4. Enforce MFA registration

How to?

To set Office 365 Passwords to Expire, use the Microsoft 365 Admin Center:
  1. Expand settings then select the Org Settings subcategory.
  2. Click on Security & privacy.
  3. Select Password expiration policy.
  4. If the Set passwords to never expire (recommended) box is unchecked, check it.
  5. Click Save.

To set Office 365 Passwords Are Not Set to Expire, use the Microsoft Online PowerShell Module:

  1. Connect Microsoft Online service using Connect-MSOLService.
  2. Run the following Microsoft Online PowerShell command:

Set -MsolPasswordPolicy -ValidityPeriod 2147483647 -DomainName <DomainName> - NotficationDays 30

Monitor:

To verify Office 365 Passwords Are Not Set to Expire, use the Microsoft 365 Admin Center:
  1. Expand settings then select the Org Settings subcategory.
  2. Click on Security & privacy.
  3. Select Password expiration policy and ensure that Set passwords to never expire (recommended) has been checked.

To verify Office 365 Passwords Are Not Set to Expire, use the Microsoft Online PowerShell Module:

  1. Connect to Microsoft Online service using Connect-MSOLService.
  2. Run the following Microsoft Online PowerShell command:

Get -MsolPasswordPolicy  -DomainName <DomainName> | ft ValidityPeriod














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