Skip to main content

When we first evaluated Netskope, visibility into non-org accounts within the Outlook desktop application was a known gap due to the application being certificate pinned. I recall that other vendors we evaluated were able to enforce DLP controls on other Outlook accounts, but these vendors often excelled in Endpoint DLP and leveraged more “legacy” approaches as opposed to Netskope’s reliance on the forward proxy.

We currently block non-org accounts in the Outlook desktop app, but the allowance of client accounts within Outlook is a frequent request from our team users. With Netskope’s newer ventures into the Endpoint DLP space, are there any new or future-anticipated abilities to enforce DLP controls over these Outlook accounts/other certificate-pinned applications?

 

Netskope has had the capability to send headers to block this type of data to your upstream MTA such as Proofpoint or Mimecast for years now via the SMTP DLP Email Proxy (Product). You can also do a loopback to O365 if you have no upstream MTA.

 

That is how you need to accomplish what your after here.


Reply