Storage - Ensure Expiration Time For External Sharing Links Is Set

By Ashwin Venugopal -

 








Summary

Users can easily share content with people outside the organization (such as partners, vendors, clients, or customers) with the help of the external sharing features of Microsoft SharePoint, where, it is a part of secure collaboration with Microsoft 365.

Reason

An attacker can compromise a user account for a short period of time, send anonymous sharing links to an external account, then take their time accessing the data. External accounts can also be compromised and the anonymous sharing links can be stolen to send those external entities after the data has been shared. By restricting how long the links are valid can reduce the window of opportunity for attackers.

What If?

If this feature is enabled, then, it will ensure that the link expires within the defined number of days. This will however, have an effect on the links that were previously not set with an expiration.

How to?

To set expiration for anonymous access links, use the Microsoft 365 Admin Center:
  1. Select Admin centers and SharePoint
  2. Expand Policies and then click Sharing
  3. Under Choose expiration and permissions options for Anyone links. Check the These links must expire within this many days
  4. Set to the desired number of days, such as 30
  5. Click Save

To set expiration for anonymous access links, you can also use SharePoint Online PowerShell:
  1. Connect to SharePoint Online using Connect-SPOService
  2. Now, run the following PowerShell command:

Set-SPOTenant -RequireAnonymousLinksExpireInDays 30

Monitor:

To verify anonymous access links are correctly set to expire, use the Microsoft 365 Admin Center:
  1. Select Admin centers and SharePoint
  2. Expand Policies and then click Sharing
  3. Under Choose expiration and permissions options for Anyone links. Verify if These links must expire within this many days is checked.
  4. Confirm the number of days is set to the desired value, such as 30.

To verify anonymous links are correctly set to expire, you can also use SharePoint Online PowerShell:
  1. Connect to SharePoint Online using Connect-SPOService
  2. Now, run the following PowerShell command:

Get-SPOTenant | fl RequireAnonymousLinksExpireInDays

      3. Verify that the returned value is at most 30 days but is not set to -1











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