Granted Patent B2

US 12,598,216 · App. 18/631,478 · Granted Apr 7, 2026

Inventors: Krishna Narayanaswamy (Saratoga, CA); Ajay Agrawal (Bangalore, IN)

Assignee: Netskope, Inc.

H04L63/20G06F16/285G06F16/951G06F21/6209H04L63/0281H04L63/10H04L63/104H04L63/105H04L63/12G06F16/1734

Abstract

Claims (75)

1 . An endpoint data loss prevention system, comprising:

a monitor, executing on an endpoint, configured to detect data egress requests from the endpoint to uncontrolled destinations, wherein each data egress request comprises an associated file;

a local metadata store on the endpoint having stored therein sensitivity metadata, wherein:

the sensitivity metadata classifies a sensitivity of a respective file and is generated by a cloud-based content sensitivity scanner using deep inspection of the respective file and stored in a cloud-based metadata store, and

the local metadata store is synchronized with the cloud-based metadata store periodically;

an endpoint policy enforcer, executing on the endpoint, configured to:

receive an indication of the data egress requests from the monitor,

in response to each data egress request, obtain the sensitivity metadata for the associated file of the data egress request, and

enforce data loss prevention policies on the data egress requests based on the sensitivity metadata; and

an anchor pattern scanner, executing on the endpoint, configured to:

in response to scan requests associated with unscanned files, classifying the unscanned file as sensitive or non-sensitive based on an anchor pattern scan,

in response to the unscanned file being classified as non-sensitive, transmit a non-sensitive indication to the endpoint policy enforcer as the sensitivity metadata, and

in response to the unscanned file being classified as sensitive:

transmit the unscanned file to the cloud-based content sensitivity scanner;

receive the sensitivity metadata for the unscanned file from the cloud-based content sensitivity scanner; and

transmit the sensitivity metadata provided by the cloud-based content sensitivity scanner to the endpoint policy enforcer.

2 . The endpoint data loss prevention system of claim 1 , wherein the endpoint policy enforcer is further configured to:

request the sensitivity metadata from the local metadata store.

3 . The endpoint data loss prevention system of claim 2 , wherein the endpoint policy enforcer is further configured to:

in response to a negative response from the local metadata store, request the sensitivity metadata from the cloud-based metadata store.

4 . The endpoint data loss prevention system of claim 3 , wherein the endpoint policy enforcer is further configured to:

in response to a negative response from the cloud-based metadata store, send a scan request to the anchor pattern scanner indicating the associated file is an unscanned file.

5 . The endpoint data loss prevention system of claim 4 , wherein the endpoint policy enforcer is further configured to:

in response to receiving the non-sensitive indication from the anchor pattern scanner, allow the data egress request.

6 . The endpoint data loss prevention system of claim 4 , wherein the endpoint policy enforcer is further configured to:

in response to receiving the sensitivity metadata from the anchor pattern scanner, store the sensitivity metadata in the local metadata store.

7 . The endpoint data loss prevention system of claim 1 , wherein the monitor is a file system monitor.

8 . The endpoint data loss prevention system of claim 1 , wherein the monitor is an endpoint traffic monitor.

9 . The endpoint data loss prevention system of claim 1 , wherein the endpoint policy enforcer is further configured to:

for each data egress request, put the data egress request on hold until the sensitivity metadata for the associated file is obtained.

10 . The endpoint data loss prevention system of claim 1 , wherein the anchor pattern scan comprises scanning the unscanned file for:

social security numbers;

credit card numbers;

bank account numbers;

dates of birth;

passwords;

source code; or

a combination thereof.

11 . The endpoint data loss prevention system of claim 1 , wherein the sensitivity metadata in the local metadata store comprises data generated by the cloud-based content sensitivity scanner while the respective files were resident in a cloud-based document store.

12 . The endpoint data loss prevention system of claim 1 , wherein the sensitivity metadata in the local metadata store comprises data generated by the cloud-based content sensitivity scanner in response to the respective files being transmitted to or from a cloud-based document store.

13 . A method for enforcing data loss prevention at an endpoint, the method comprising:

maintaining, on the endpoint, a local metadata store comprising sensitivity metadata, wherein:

the sensitivity metadata classifies a sensitivity of a respective file and is generated by a cloud-based content sensitivity scanner using deep inspection of the respective file and stored in a cloud-based metadata store, and

the local metadata store is synchronized with the cloud-based metadata store periodically;

intercepting, with a monitor executing on the endpoint, data egress requests from the endpoint to uncontrolled destinations, wherein each data egress request comprises an associated file;

receiving, by an endpoint policy enforcer, an indication of the data egress requests from the monitor;

in response to each data egress request, obtaining, by the endpoint policy enforcer, the sensitivity metadata for the associated file of the data egress request; and

enforcing, by the endpoint policy enforcer, data loss prevention policies on the data egress requests based on the sensitivity metadata.

14 . The method of claim 13 , wherein the obtaining the sensitivity metadata comprises:

requesting, by the endpoint policy enforcer, the sensitivity metadata from the local metadata store.

15 . The method of claim 14 , wherein the obtaining the sensitivity metadata further comprises:

in response to a negative response from the local metadata store, requesting, by the endpoint policy enforcer, the sensitivity metadata from the cloud-based metadata store.

16 . The method of claim 15 , wherein the obtaining the sensitivity metadata further comprises:

in response to a negative response from the cloud-based metadata store, determining, by the endpoint policy enforcer, that the associated file is an unscanned file;

transmitting, by the endpoint policy enforcer, a request to scan the unscanned file to an anchor pattern scanner;

classifying, by the anchor pattern scanner, the unscanned file as sensitive or non-sensitive based on an anchor pattern scan, wherein the classifying comprises:

in response to the unscanned file being classified as non-sensitive, transmit a non-sensitive indication to the endpoint policy enforcer as the sensitivity metadata, and

in response to the unscanned file being classified as sensitive:

transmit the unscanned file to the cloud-based content sensitivity scanner;

receive the sensitivity metadata for the unscanned file from the cloud-based content sensitivity scanner; and

transmit the sensitivity metadata provided by the cloud-based content sensitivity scanner to the endpoint policy enforcer.

17 . The method of claim 16 , further comprising:

in response to receiving the non-sensitive indication from the anchor pattern scanner, allowing, by the endpoint policy enforcer, the data egress request.

18 . The method of claim 16 , further comprising:

in response to receiving the sensitivity metadata from the anchor pattern scanner, storing, by the endpoint policy enforcer, the sensitivity metadata in the local metadata store.

19 . The method of claim 16 , wherein the anchor pattern scanner scans the unscanned file for:

social security numbers;

credit card numbers;

bank account numbers;

dates of birth;

passwords;

source code; or

a combination thereof.

20 . The method of claim 13 , further comprising:

for each data egress request, putting, by the endpoint policy enforcer, the data egress request on hold until the sensitivity metadata for the associated file is obtained.

Assignments (1)

Continuity (8)

References Cited (144)