Drag Drop detection is not working from Outlook application to Chrome(Outlook.Office.com)
search cancel

Drag Drop detection is not working from Outlook application to Chrome(Outlook.Office.com)

book

Article ID: 264952

calendar_today

Updated On:

Products

Data Loss Prevention Endpoint Prevent

Issue/Introduction

1. Outlook logged in as On-prem Exchange account and https://outlook.office.com/mail/ (in Chrome browser) is logged in as O365 user.
Tested file drag drop from Outlook to Chrome(outlook.office.com > compose email attachment section) and it got detected.

2. Outlook logged in as O365 account and https://outlook.office.com/mail/ (in Chrome browser) is logged in as same O365 user.
Tested file drag drop from Outlook to Chrome(outlook.office.com > compose email attachment section) and it didn't got detected.

3. Again Outlook logged in as On-prem Exchange account and https://outlook.office.com/mail/ (in Chrome browser) is logged in as O365 user.
Tested file drag drop from Outlook to Chrome(outlook.office.com > compose email attachment section) and it didn't got detected.

4. If we drag drop a file from desktop or any other folder to https://outlook.office.com/mail/ (in Chrome browser) with O365 user logged in, it will detect as expected.



Environment

DLP 15.8 MP3, 16.0 MP1

Cause

Chrome solution is changing to SDK based solution, this issue is reproducible with 16.0RU1 SDK changes as well.

Resolution

1. Upon testing this issue internally, we found below two scenarios:

scenario 1 :-  Drag and Drop file to the chrome browser outlook.com from outlook client  - detection works.

scenario 2 :-  After the scenario 1, attempt to drag and drop the same file to other websites like dlptest.com and gmail.com  - file is going undetected. This is a case of data loss. 

2. In 16.0RU1 chrome solution is changing to SDK based solution and this issue is reproducible with 16.0 RU1 SDK changes as well.

3. Since the chrome monitoring is changing to SDK based, we worked with Google product team for the integration and it is fixed in Chrome build version 117.0.5913.0.

4. From DLP product side, the detection issue is addressed in DLP 16.0 RU1 release.