# US 2021/0344746 A1 · Cloud application-agnostic data loss prevention (dlp)

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2021/0344746 A1
- Document ID: US20210344746A1
- Status: Published application
- Kind: A1
- Application number: 17/373,643
- Filed: 2021-07-12
- Published: 2021-11-04
- Earliest claimed: 2018-05-22
- Assignees: Netskope, Inc.
- Applicants: Netskope, Inc.
- Inventors: Lebin CHENG; Krishna NARAYANASWAMY
- Web page: https://patentgrep.com/patent/US20210344746A1

## CPC

- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- G06F 9/547: {Remote procedure calls [RPC]; Web services}
- G06F 16/9566: {URL specific, e.g. using aliases, detecting broken or misspelled links}
- G06F 21/6227: {where protection concerns the structure of data, e.g. records, types, queries}
- G06F 21/6245: {Protecting personal data, e.g. for financial or medical purposes}
- H04L 63/0245: {Filtering by information in the payload}
- H04L 63/0281: {Proxies}
- H04W 12/088: using filters or firewalls
- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- H04W 12/02: Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII]
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

The technology disclosed applies data loss prevention (DLP) to those cloud-applications for which no application-specific parser is available. Known cloud applications can be arranged in categories of services such as “personal pages and blog,” “news websites,” “cloud-based storage services,” and “social media services.” A category includes a list of uniform resource locators (URLs) of providers of cloud applications that allow users to perform similar activities. The various providers in a category use different syntaxes to implement services in the category. The disclosed category-directed parsers synthesize interaction syntax patterns of a sample of providers in the category. A category-directed parser collects metadata from known cloud applications using multiple category-directed match rules synthesized from syntaxes used by the sample providers in the category. The metadata collected by the category-directed parser enables the DLP processor to focus analysis of the content being conveyed via a corresponding API.

## Claims

### Claim 1

A system including one or more processors coupled to memory, the memory loaded with computer instructions to apply data loss prevention, DLP, to cloud-based content services, the instructions, when executed on the processors, implement actions comprising:
determining that a known cloud-based service is being accessed via an application programming interface, API;
determining that no service-specific parser is available for the API being accessed;
determining a category of service for the API being accessed;
selecting a category-directed parser based upon the determined category;
wherein the category-directed parser includes a plurality of category-directed match rules derived from a plurality of syntaxes used by providers of cloud-based content services to implement the category of service;
parsing content being conveyed via the API using the category-directed parser to collect metadata and assigning the collected metadata to variables, using the category-directed match rules; and
transmitting the collected metadata assigned to the variables to a DLP processor for applying data loss prevention to the content being conveyed via the API.

### Claim 2 (depends on 1)

The system of claim 1, further implementing actions comprising:
if no category-directed parser is available to be selected for the API being accessed in the selecting action:
selecting a generic parser, wherein the generic parser includes at least one default match rule derived from the plurality of syntaxes used by providers of cloud-based content services, wherein the default match rule is associated with a plurality of category of services;
parsing content being conveyed via the API using the match rules of the selected generic parser and assigning the collected metadata to variables.

### Claim 3 (depends on 2)

The system of claim 2, wherein determining to use the category-directed parser is based on a domain name in a uniform resource locator (abbreviated URL) used to access the API.

### Claim 4 (depends on 2)

The system of claim 2, wherein the plurality of match rules include at least ten match rules derived from the plurality of syntaxes used by the providers of cloud-based content services to implement the category of service addressed by the category-directed parser.

### Claim 5 (depends on 2)

The system of claim 2, wherein the plurality of match rules are derived from syntaxes used by at least twenty five providers of cloud-based content services that each implement the category of service addressed by the category-directed parser.

### Claim 6 (depends on 1)

The system of claim 1, wherein the cloud-based services are served by at least five category-directed parsers in distinct categories of service.

### Claim 7 (depends on 6)

The system of claim 6, wherein the distinct categories of services served by the at least five category-directed parsers include at least personal pages and blogs, news web sites, cloud-based storage services, webmail, and social media services.

### Claim 8 (depends on 7)

The system of claim 7, wherein collecting metadata from content being conveyed via the API further includes, processing a request message from a client to a server hosting the known cloud-based service.

### Claim 9 (depends on 8)

The system of claim 8, wherein the request message is followed by an upload via the API of the content from the client to the server that is subject to DLP inspection.

### Claim 10

A system including one or more processors coupled to memory, the memory loaded with computer instructions to apply data loss prevention, DLP, to cloud-based content services, the instructions, when executed on the processors, implement actions comprising:
determining that an unknown cloud-based service is being accessed via an application programming interface, API for which no service-specific parser and no category-directed parser is available,
selecting a generic parser based upon the determination that an unknown cloud-based service is being accessed;
wherein the generic parser includes at least one default match rule derived from a plurality of syntaxes used by providers of cloud-based content services, wherein the default match rule is associated with at least two categories of services addressed by category-directed parsers;
parsing content being conveyed via the API using the selected generic parser, collecting metadata and assigning the collected metadata to variables; and
transmitting the collected metadata, assigned to the variables and accompanied by data indicating that the metadata was collected by the generic parser, to a DLP processor for applying data loss prevention to the content being conveyed via the API.

### Claim 11

A method of applying data loss prevention, DLP, to cloud-based content services, including:
determining that a known cloud-based service is being accessed via an application programming interface, API;
determining that no service-specific parser is available for the API being accessed;
determining a category of service for the API being accessed;
selecting a category-directed parser based upon the determined category;
wherein the category-directed parser includes a plurality of category-directed match rules derived from a plurality of syntaxes used by providers of cloud-based content services to implement the category of service;
parsing content being conveyed via the API using the category-directed parser to collect metadata and assigning the collected metadata to variables, using the category-directed match rules; and
transmitting the collected metadata assigned to the variables to a DLP processor for applying data loss prevention to the content being conveyed via the API.

### Claim 12 (depends on 11)

The method of claim 11, wherein determining to use the category-directed parser is based on a domain name in a uniform resource locator (abbreviated URL) used to access the API.

### Claim 13 (depends on 11)

The method of claim 11, wherein the plurality of match rules include at least ten match rules derived from the plurality of syntaxes used by the providers of cloud-based content services to implement the category of service addressed by the category-directed parser.

### Claim 14 (depends on 11)

The method of claim 11, wherein the plurality of match rules are derived from syntaxes used by at least twenty five providers of cloud-based content services that each implement the category of service addressed by the category-directed parser.

### Claim 15 (depends on 11)

The method of claim 11, wherein the cloud-based services are served by at least five cloud-based content services in distinct categories of service.
