Account/Authentication - Azure Active Directory - Ensure Modern Authentication for SharePoint Applications is Required

By Ashwin Venugopal -

 






Summary

The option of modern authentication in Microsoft 365 enables authentication features like Multifactor Authentication (MFA) using smart cards, Certificate-based Authentication (CBA), and third-party SAML identity providers.

Reason

Authentication controls like MFAs can be circumvented if basic authentication is used by SharePoint Applications. Additionally, requiring modern authentication for SharePoint applications ensures that strong authentication mechanisms are used when establishing sessions between these applications, SharePoint, and connecting users.

What If?

If modern authentication for SharePoint is implemented, then, users will have to authenticate to SharePoint using modern authentication. This may cause a minor impact to typical user behavior.

How to?

To set SharePoint settings, use the Microsoft 365 Admin Center:
  1. Under Admin centers select SharePoint.
  2. Expand the Policies section, and then choose Access control.
  3. Select Apps that don't use modern authentication.
  4. Select the radio button for Block access.
  5. Click Save.

To set Apps that don't use modern authentication is set to Block, use the SharePoint online PowerShell mode:

  1. Connect to SharePoint Online using Connect -SPOService -Url https://tenant-admin.sharepoint.com replacing tenant with your value.
  2. Run the following SharePoint Online PowerShell command-

Set -SPOTenant -LegacyAuthProtocolsEnabled $false

Monitor:

To verify SharePoint settings, use the Microsoft 365 Admin Center:
  1. Under Admin centers select SharePoint.
  2. Expand the Policies section, and then choose Access control.
  3. Select Apps that don't use modern authentication and make sure that it is set to Block access.

To verify Apps that don't use modern authentication is set to Block, use the SharePoint online PowerShell mode:

  1. Connect to SharePoint Online using Connect -SPOService -Url https://tenant-admin.sharepoint.com replacing tenant with your value.
  2. Run the following SharePoint Online PowerShell command-

Set -SPOTenant | ft LegacyAuthProtocolsEnabled

      3. Verify LegacyAuthProtocolsEnabled is set false.

















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...
Read more

Deployment (Part 1)

By Ashwin Venugopal -
Image
  To read part 2, please click  here To read part 3, please click  here Azure Resources Microsoft Sentinel needs following resources to be created: Subscription (if a dedicated subscription(s) will be used) Resource group(s) Log Analytics workspace(s) Automation rules/playbook Alert rules Workbooks Microsoft Sentinel offers hundreds of alert rules, workbooks, and automation playbook templates along with hunting scripts. The templates can be used to activate/deploy schedule alerts, create customized dashboards, create automation playbooks and perform threat-hunting activities. Generally, once deployed, the resources created have to be adjusted to match the existing environment, configure local credentials, etc. Methods of deployment: Manual- Administrator can manually configures the Microsoft Sentinel resources with the help of Azure portal. Any manual process has the inherent risks of human operator error, lack of compliance with potential change control procedures, and u...
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...
Read more