Data Management - Ensure DLP Policies are Enabled for Microsoft Teams

By Ashwin Venugopal -

 








Summary

Enabling these policies for Microsoft Teams blocks sensitive content when shared in teams or channels. The content will be scanned for specific types of data such as social security numbers, credit card numbers, or passwords.

Reason

If DLP policies are enabled, then, they can alert the users and administrators about the types of data not to be exposed which in turn helps in protecting the data from accidental exposure. 

What If?

Setting up these policies will allow sensitive data in Teams channels or chat messages to be detected or blocked. 

How to?

To enable DLP policies, use the Microsoft 365 Admin Center:
  1. Under Admin centers pick Compliance to open Microsoft 365 purview compliance portal.
  2. Under Solutions select Data loss prevention and then Policies.
  3. Now, click Create policies.
  4. After that, either start with a template or create a custom policy.
  5. Provide a Name for your policy.
  6. At the Choose locations step, either choose Protect content in Exchange email, Teams chats and channel messages and OneDrive and SharePoint documents or select Let me choose specific locations. If you do select Let me choose specific locations, ensure that Teams chat and channel messages is selected.
  7. Ensure that the proper DLP policies are created for the type of content to be detected and what actions should be taken.

Monitor:

To verify that DLP policies are enabled, use the Microsoft 365 Admin Center:
  1. Under Admin centers pick Compliance to open Microsoft 365 purview compliance portal.
  2. Under Solutions select Data loss prevention and then Policies.
  3. Now, click Create policies.
  4. After that, verify that policies exist and are enabled.
  5. Now, ensure that under Locations to apply the policy the policies include Teams chat and channel messages.
To verify that DLP for Microsoft Teams is enabled for all users, use the Exchange Online/Compliance PowerShell Module:
  1. Run Exchange Online PowerShell Module.
  2. Connect using Connect-ExchangeOnline, then run the following

Import-Module ExchangeOnlineManagement

       3. After that, connect to the Security and Compliance Center via the following Connect-                               IPPSSession.
        4. Run the following PowerShell command to see what DLP policies are created:

Get-DlpCompliancePolicy

        5. Next, you have to run the following to look at the policy details to ensure the required users are              excluded TeamsLocationException

Get-DlpCompliancePolicy -Identity "POLICYNAME FROM ABOVE" | Select-Object TeamsLocation*















































































































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