IP Library Granted Patent US 9,716,724
Granted Patent B1
US 9,716,724 · App. 14/625,571 · Granted Jul 25, 2017

Cloud data loss prevention system

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,716,724
App. No.
14/625,571
Granted
Jul 25, 2017
Kind
B1
Abstract

A cloud based data loss prevention (DLP) system (“cloud DLP system”) implements offline scanning of content stored in a cloud-based service belonging to an enterprise in accordance with the enterprise's policy and control. The cloud DLP system provides alerts or remediation in response to detection of non-compliance cloud content. In some embodiments, the cloud DLP system is provided with the access credential of the enterprise to access the cloud-based service. In other embodiments, the enterprise's login credential remains within the enterprise data network and an on-premises client obtains an access token for the cloud DLP system.

Claims (42)

1. A system for providing data loss prevention services to an enterprise operating an enterprise data network, the enterprise data network being in communication with a cloud service provider to store cloud content belonging to the enterprise and to access the stored cloud content on the cloud service provider, the system comprising:

a connector client installed on the premises of the enterprise data network and a cloud based computing system configured outside of the enterprise data network;

the connector client being in communication with the cloud service provider and the cloud based computing system, the connector client being configured to receive, from within the enterprise data network, an access credential of the enterprise for the cloud service provider, the connector client being configured to obtain an access token from the cloud service provider using the access credential of the enterprise, the connector client being configured to provide the access token for the cloud service provider to the cloud based computing system, and the connector client being configured to receive an alert or a report from the cloud based computing system; and

the cloud based computing system including at least one hardware processor and being in communication with the connector client and the cloud service provider, the cloud based computing system being configured to receive the access token from the connector client and to distribute the access token to the one or more processors, the cloud based computing system being configured to use the access token to access the cloud service provider on behalf of the enterprise, the cloud based computing system being configured to use the access token to access cloud content at the cloud service provider belonging to the enterprise and to perform multi-thread scanning of the cloud content for compliance with a security policy of the enterprise, the cloud based computing system being configured to identify a non-compliance cloud content in response to detecting certain cloud content stored on the cloud service provider as being in violation of the security policy, the cloud based computing system being configured to generate the alert or the report in response to the detecting and to provide the alert or the report to the connector client, and the cloud based computing system being further configured to initiate a remediation measure in response to detecting certain cloud content as being in violation of the security policy, the remediation measure comprising one or more of deleting the non-compliance cloud content and quarantining the non-compliance cloud content.

2. The system of claim 1 , wherein the connector client is configured to receive a plurality of access credentials of the enterprise for respective plurality of cloud service providers and to obtain a plurality of access tokens from the respective plurality of cloud service providers using the plurality of access credential of the enterprise, the connector client being configured to provide the plurality of access tokens to the cloud based computing system; and the cloud based computing system is configured to obtain the plurality access tokens from the connector client for accessing the respective plurality of cloud service providers on behalf of the enterprise, the cloud based computing system being configured to use the access tokens to access cloud content at the plurality of cloud service providers belonging to the enterprise and to perform multi-thread scanning of the cloud content for compliance with the security policy of the enterprise.

3. The system of claim 1 , wherein the cloud based computing system comprises a distributed real-time computing system comprising a plurality of processors configured to perform multi-thread scanning of the enterprise's cloud content at the cloud service provider.

4. The system of claim 3 , wherein the cloud based computing system is configured to distribute the access token to the plurality of processors of the distributed real-time computing system.

5. The system of claim 1 , wherein the cloud based computing system is further configured to generate the alert or the report in response to detecting certain cloud content as being in violation of the security policy, the alert or the report identifying the non-compliance cloud content.

6. The system of claim 1 , wherein the cloud content comprises data files or documents or content in other data formats.

7. The system of claim 1 , wherein the cloud based computing system is configured to access the cloud service provider using the cloud service provider's application programming interface (API) to access events and contents at the cloud service provider.

8. The system of claim 7 , wherein the cloud based computing system is configured to access the cloud service provider using the cloud service provider's event API to poll for cloud content recently uploaded to the cloud service provider and belonging to the enterprise and to retrieve the recently uploaded cloud content to scan for compliance with the security policy of the enterprise.

9. A method for providing data loss prevention services to an enterprise operating an enterprise data network, the enterprise data network being in communication with a cloud service provider to store cloud content belonging to the enterprise and to access the stored cloud content on the cloud service provider, the method comprising:

receiving from within the enterprise data network and at a connector client installed on the premises of the enterprise data network, an access credential of the enterprise for the cloud service provider;

obtaining, at the connector client installed on the premises of the enterprise data network, an access token from the cloud service provider using the access credential of the enterprise;

providing, from the connector client, the access token to a cloud based computing system configured outside of the enterprise data network, the cloud based computing system comprising one or more processors;

receiving, at the cloud based computing system, the access token from the connector client, the access token being used to access the cloud service provider on behalf of the enterprise;

distributing the access token to the one or more processors;

assessing, at the cloud based computing system and using the access token, the cloud content at the cloud service provider belonging to the enterprise;

performing multi-thread scanning, at the cloud based computing system, the cloud content for compliance with a security policy of the enterprise;

identifying, at the cloud based computing system, a non-compliance cloud content in response to detecting certain cloud content stored on the cloud service provider as being in violation of the security policy;

generating, at the cloud based computing system, an alert or a report in response to the detecting;

providing, from the cloud based computing system, the alert or the report to the connector client; and

initiating, at the cloud based computing system, a remediation measure in response to detecting certain cloud content as being in violation of the security policy, wherein initiating the remediation measure comprising deleting the non-compliance cloud content or quarantining the non-compliance cloud content.

10. The method of claim 9 , further comprising:

receiving, from within the enterprise data network and at the connector client, a plurality of access credentials of the enterprise for respective plurality of cloud service providers;

obtaining a plurality of access tokens from the respective plurality of cloud service providers using the plurality of access credential of the enterprise;

providing the plurality of access tokens to the cloud based computing system;

receiving, at the cloud based computing system, the plurality access tokens from the connector client for accessing respective plurality of cloud service providers on behalf of the enterprise; and

assessing, at the cloud based computing system and using the plurality of access tokens, the cloud contents at the plurality of cloud service providers belonging to the enterprise.

11. The method of claim 9 , further comprising:

providing a distributed real-time computing system comprising a plurality of processors configured as the cloud based computing system; and

performing multi-thread scanning of the enterprise's cloud content at the cloud service using the distributed real-time computing system.

12. The method of claim 11 , further comprising:

distributing the access token to the plurality of processors of the distributed real-time computing system.

13. The method of claim 9 , further comprising:

generating, at the cloud based computing system, the alert or the report in response to detecting certain cloud content as being in violation of the security policy, the alert or the report identifying the non-compliance cloud content.

14. The method of claim 9 , wherein the cloud content comprises data files or documents or content in other data formats.

15. The method of claim 9 , wherein assessing, at the cloud based computing system and using the access token, the cloud content at the cloud service provider belonging to the enterprise comprises:

accessing the cloud service provider using the cloud service provider's application programming interface (API) to access events and contents at the cloud service provider.

16. The method of claim 15 , wherein accessing the cloud service provider using the cloud service provider's application programming interface (API) to access events and contents at the cloud service provider comprises:

accessing the cloud service provider using the cloud service provider's event API to poll for cloud content recently uploaded to the cloud service provider and belonging to the enterprise; and

retrieving the recently uploaded cloud content to scan for compliance with the security policy of the enterprise.

Assignments (16)
ASSIGNMENT OF INTERCOMPANY FIRST LIEN PATENT SECURITY AGREEMENT Recorded Apr 14, 2025
From: UBS AG, STAMFORD BRANCH
To: ACQUIOM AGENCY SERVICES LLC
Reel/Frame 070840/0598 →
INTERCOMPANY FIRST LIEN PATENT SECURITY AGREEMENT Recorded Jan 24, 2025
From: SKYHIGH SECURITY LLC
To: UBS AG, STAMFORD BRANCH, AS COLLATERAL AGENT
Reel/Frame 070618/0001 →
RELEASE OF SECURITY INTEREST Recorded Oct 28, 2024
From: UBS AG, STAMFORD BRANCH, AS COLLATERAL AGENT
To: SKYHIGH SECURITY LLC
Reel/Frame 069272/0570 →
RELEASE OF SECURITY INTEREST Recorded Aug 16, 2024
From: STG PARTNERS, LLC
To: MUSARUBRA US LLC; SKYHIGH SECURITY LLC
Reel/Frame 068671/0435 →
FIRST LIEN PATENT SECURITY AGREEMENT Recorded Aug 15, 2024
From: MAGENTA SECURITY HOLDINGS LLC; SKYHIGH SECURITY LLC
To: UBS AG, STAMFORD BRANCH, AS COLLATERAL AGENT
Reel/Frame 068657/0666 →
SECURITY INTEREST Recorded Aug 1, 2024
From: MUSARUBRA US LLC; SKYHIGH SECURITY LLC
To: STG PARTNERS, LLC
Reel/Frame 068324/0731 →
CHANGE OF NAME Recorded May 9, 2022
From: SKYHIGH NETWORKS, LLC
To: SKYHIGH SECURITY LLC
Reel/Frame 059912/0601 →
FIRST LIEN PATENT SECURITY AGREEMENT Recorded Jul 27, 2021
From: MUSARUBRA US LLC; SKYHIGH NETWORKS, LLC
To: UBS AG, STAMFORD BRANCH, AS COLLATERAL AGENT
Reel/Frame 057453/0053 →
SECOND LIEN PATENT SECURITY AGREEMENT Recorded Jul 27, 2021
From: MUSARUBRA US LLC; SKYHIGH NETWORKS, LLC
To: UBS AG, STAMFORD BRANCH, AS COLLATERAL AGENT
Reel/Frame 056990/0960 →
RELEASE OF SECURITY INTEREST Recorded Jul 26, 2021
From: MORGAN STANLEY SENIOR FUNDING, INC.
To: MCAFEE, LLC; SKYHIGH NETWORKS, LLC
Reel/Frame 057620/0102 →
RELEASE OF INTELLECTUAL PROPERTY COLLATERAL - REEL/FRAME 046416/0286 Recorded Oct 26, 2020
From: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
To: SKYHIGH NETWORKS, LLC
Reel/Frame 054211/0739 →
CORRECTIVE ASSIGNMENT TO CORRECT THE RECEIVING PARTY DATA PREVIOUSLY RECORDED AT REEL: 046416 FRAME: 0286. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Oct 19, 2020
From: SKYHIGH NETWORKS, LLC
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 054560/0325 →
CHANGE OF NAME Recorded Dec 27, 2018
From: SKYHIGH NETWORKS, INC.
To: SKYHIGH NETWORKS, LLC
Reel/Frame 047985/0819 →
SECURITY INTEREST Recorded Jul 20, 2018
From: SKYHIGH NETWORKS, LLC
To: MORGAN STANLEY SENIOR FUNDING, INC.
Reel/Frame 046416/0225 →
SECURITY INTEREST Recorded Jul 20, 2018
From: SKYHIGH NETWORKS, LLC
To: MORGAN STANLEY SENIOR FUNDING, INC.
Reel/Frame 046416/0286 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 15, 2015
From: CHENNURU, SNEHAL; SARUKKAI, SEKHAR
To: SKYHIGH NETWORKS, INC.
Reel/Frame 035419/0183 →