# US 2015/0106870 A1 · Anomaly detection on web client

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

- Number: US 2015/0106870 A1
- Document ID: US20150106870A1
- Status: Published application
- Kind: A1
- Application number: 14/129,514
- Filed: 2013-10-10
- Published: 2015-04-16
- Earliest claimed: 2013-10-10
- Assignees: Intel Corporation
- Inventors: Hong Li; Tobias Kohlenberg; Jim S. Baca
- Web page: https://patentgrep.com/patent/US20150106870A1

## CPC

- H04L 63/1425: {Traffic logging, e.g. anomaly detection}
- G06F 16/9535: Search customisation based on user profiles and personalisation
- G06F 21/54: by adding security routines or objects to programs
- G06F 21/554: {involving event detection and direct action}
- 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)

## Abstract

Embodiments for anomaly detection on a web client are generally described herein. A processor on the web client is monitored, where a web browser is installed on the web client, with the web browser arranged to render a web page, the web page including content originating from a plurality of origins. A request from the web page to store data on the web client is intercepted, with the request originating from a particular origin of the plurality of origins. The request is analyzed and approved or denied based on the particular origin.

## Claims

### Claim at position 1

-25. (canceled)

### Claim 26

An apparatus for anomaly detection on a web client, the apparatus comprising:
a monitoring module arranged to:
monitor a web browser installed on the apparatus, the web browser arranged to render a web page, the web page including content originating from a plurality of origins;
intercept a request from the web page to store data on the apparatus, the request originating from a particular origin of the plurality of origins;
analyze the request; and
approve or deny the request based on the particular origin.

### Claim 27 (depends on 26)

The apparatus of claim 26, wherein the web browser is one of a plurality of web browsers installed on the apparatus, and wherein to analyze the request, the monitoring module is arranged to analyze the request according to a setting specific to the web browser, the setting specifying a policy to a handle storage request from one of a plurality of related origins.

### Claim 28 (depends on 27)

The apparatus of claim 27, wherein each of the plurality of web browsers include a different setting for handling a storage request from one of a plurality of related origins.

### Claim 29 (depends on 26)

The apparatus of claim 26, wherein to analyze and approve the request, the monitoring module is arranged to:
identify the particular origin;
query a database with the particular origin to determine whether the particular origin is on a white list of origins; and
approve the request when the particular origin is on the white list.

### Claim 30 (depends on 29)

The apparatus of claim 29, wherein the database is stored at the apparatus.

### Claim 31 (depends on 29)

The apparatus of claim 29, wherein the database is stored at a server remote from the apparatus.

### Claim 32 (depends on 26)

The apparatus of claim 26, wherein the monitoring module is a plug-in for the web browser.

### Claim 33 (depends on 26)

The apparatus of claim 26, wherein to analyze and approve the request, the monitoring module is arranged to:
analyze a characteristic of web browser behavior; and
approve the request based on the characteristic of web browser behavior.

### Claim 34 (depends on 33)

The apparatus of claim 33, wherein the characteristic of web browser behavior is at least one of: a speed of storing data to the apparatus, a number of subdomains of the origin requesting to store data on the apparatus, a frequency of subdomain changes, or a ratio of reads and writes of stored data.

### Claim 35 (depends on 26)

The apparatus of claim 26, wherein the request from the web page to store data on the apparatus is a HTML5 request to store data in a localStorage object.

### Claim 36 (depends on 26)

The apparatus of claim 26, comprising a notification module arranged to present a notification to a user of the apparatus when the monitoring module denies the request.

### Claim 37 (depends on 26)

The apparatus of claim 26, wherein to deny the request, the monitoring module is arranged to add the particular origin to a blacklist to block future storage requests from the particular origin.

### Claim 38 (depends on 26)

The apparatus of claim 26, wherein to deny the request, the monitoring module is arranged to block storage of data on the apparatus.

### Claim 39

A method for anomaly detection on a web client, the method comprising:
monitoring using a processor on the web client, a web browser installed on the web client, the web browser arranged to render a web page, the web page including content originating from a plurality of origins;
intercepting a request from the web page to store data on the web client, the request originating from a particular origin of the plurality of origins;
analyzing the request; and
approving or denying the request based on the particular origin.

### Claim 40 (depends on 39)

The method of claim 39, wherein the web browser is one of a plurality of web browsers installed on the web client, and wherein analyzing the request comprises analyzing the request according to a setting specific to the web browser, the setting specifying a policy to a handle storage request from one of a plurality of related origins.

### Claim 41 (depends on 40)

The method of claim 40, wherein each of the plurality of web browsers include a different setting for handling a storage request from one of a plurality of related origins.

### Claim 42 (depends on 39)

The method of claim 39, wherein analyzing and approving the request comprises:
identifying the particular origin;
querying a database with the particular origin to determine whether the particular origin is on a white list of origins; and
approving the request when the particular origin is on the white list.

### Claim 43 (depends on 42)

The method of claim 42, wherein the database is stored at the web client.

### Claim 44 (depends on 42)

The method of claim 42, wherein the database is stored at a server remote from the web client.

### Claim 45 (depends on 39)

The method of claim 39, wherein the method is performed using a plug-in for the web browser.

### Claim 46 (depends on 39)

The method of claim 39, wherein analyzing and approving the request comprises:
analyzing a characteristic of web browser behavior; and
approving the request based on the characteristic of web browser behavior.

### Claim 47 (depends on 46)

The method of claim 46, wherein the characteristic of web browser behavior is at least one of: a speed of storing data, a number of subdomains of the origin requesting to store data, a frequency of subdomain changes, or a ratio of reads and writes of stored data.

### Claim 48 (depends on 39)

The method of claim 39, comprising adding the particular origin to a blacklist to block future storage requests from the particular origin.

### Claim 49 (depends on 39)

The method of claim 39, comprising blocking storage of data on the web client.

### Claim 50

A machine-readable medium including instructions for anomaly detection on a web client, which when executed by a machine, cause the machine to:
monitor using a processor on the web client, a web browser installed on the web client, the web browser arranged to render a web page, the web page including content originating from a plurality of origins;
intercept a request from the web page to store data on the web client, the request originating from a particular origin of the plurality of origins;
analyze the request; and
approve or deny the request based on the particular origin.
