Data Management - Ensure the Customer Lockbox Feature is Enabled

By Ashwin Venugopal -

 








Summary

Customer Lockbox feature should be enabled in which your approval is required by Microsoft for any datacenter operation that grants a Microsoft support engineer or other employee direct access to any data. For example, in some cases a Microsoft support engineer might need access to your Microsoft 365 content in order to help troubleshoot and fix an issue for you. Customer lockbox requests also have an expiration time, and content access is removed after the support engineer has fixed the issue. 

Reason

When this feature is enabled, it can protect the data against data spillage and exfiltration. 

What If?

In this setting Microsoft will require access to the tenant environment prior to a Microsoft engineer accessing the environment for support or troubleshooting. 

How to?

To enable the Customer Lockbox feature, use the Microsoft 365 Admin Portal:
  1. Browse to the Microsoft 365 admin center. 
  2. Expand Settings then select Org settings.
  3. Choose Security & privacy in the right pane.
  4. Click Customer Lockbox.
  5. Check the box Require approval for all data access requests.
  6. Click Save.
To set the Customer Lockbox feature to enabled, use the Exchange Online PowerShell Module:
  1. Run Exchange Online PowerShell Module.
  2. Connect using Connect-ExchangeOnline.
  3. Run the following PowerShell command-

Set-OrganizationConfig -CustomerLockboxEnabled $true

Monitor:

To verify the Customer Lockbox feature is enabled, use the Microsoft 365 Admin Portal:
  1. Browse to the Microsoft 365 admin center. 
  2. Expand Settings then select Org settings.
  3. Choose Security & privacy in the right pane.
  4. Click Customer Lockbox.
  5. Ensure the box labeled Require approval for all data access requests is checked.
To verify the Customer Lockbox feature is enabled, use the Microsoft 365 SecureScore Portal:
  1. Log in to the Microsoft 365 SecureScore portal (https://securescore.microsoft.com) using admin permissions (global admin or a custom admin role) for an Office 365 Enterprise, Microsoft 365 Business, or Office 365 Enterprise, Microsoft 365 Business, or Office 365 Business Premium subscription.
  2. Search for Turn on customer lockbox feature under Improvement actions.

To verify the Customer Lockbox feature is enabled, use the Exchange Online PowerShell Module:

  1. Run Exchange Online PowerShell Module.
  2. Connect using Connect-ExchangeOnline.
  3. Run the following PowerShell command-

Get-OrganizationConfig | Select-Object CusomeLockBoxEnabled

      4. Verify the value is set to True.



































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