# US 2021/0067543 A1 · Dynamic aggregation of information based on web application layer requests

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

- Number: US 2021/0067543 A1
- Document ID: US20210067543A1
- Status: Published application
- Kind: A1
- Application number: 16/554,228
- Filed: 2019-08-28
- Published: 2021-03-04
- Earliest claimed: 2019-08-28
- Assignees: Imperva, Inc.
- Applicants: Imperva, Inc.
- Inventors: David LEVY NAHUM
- Web page: https://patentgrep.com/patent/US20210067543A1

## CPC

- H04L 63/126: {the source of the received data}
- H04L 63/1441: {Countermeasures against malicious traffic (countermeasures against attacks on cryptographic mechanisms H04L9/002)}
- H04L 63/166: {at the transport layer}
- H04L 67/564: Enhancement of application control based on intercepted application data
- H04L 67/566: Grouping or aggregating service requests, e.g. for unified processing
- H04L 67/5682: Policies or rules for updating, deleting or replacing the stored data
- H04W 24/08: Testing, {supervising or monitoring} using real traffic
- H04L 63/0236: {Filtering by address, protocol, port number or service, e.g. IP-address or URL}
- H04L 63/0263: {Rule management}
- H04L 63/168: {above the transport layer}
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 2463/146: Tracing the source of attacks
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

A method by a web application layer proxy for dynamically creating counters during runtime based on actual web application layer requests received by the web application layer proxy. The method includes installing a counting rule in the web application layer proxy, where the counting rule specifies a set of parameters based upon which to create counters, receiving a web application layer request generated by a web application client that is intended for a web application server, determining a set of parameter values associated with the web application layer request that corresponds to the set of parameters specified by the counting rule, and creating a counter associated with the set of parameter values associated with the web application layer request in response to a determination that a counter associated with the set of parameter values associated with the web application layer request does not exist.

## Claims

### Claim 1

A method by one or more network devices implementing a web application layer proxy for dynamically creating counters during runtime based on actual web application layer requests received by the web application layer proxy, wherein the web application layer proxy is communicatively coupled between one or more web application clients and one or more web application servers, the method comprising:
installing a first counting rule in the web application layer proxy, wherein the first counting rule specifies a set of parameters based upon which to create counters;
receiving a first web application layer request generated by one of the one or more web application clients that is intended for one of the one or more web application servers;
determining a set of parameter values associated with the first web application layer request that corresponds to the set of parameters specified by the first counting rule; and
creating a first counter associated with the set of parameter values associated with the first web application layer request in response to a determination that a counter associated with the set of parameter values associated with the first web application layer request does not exist.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
receiving a second web application layer request generated by one of the one or more web application clients that is intended for one of the one or more web application servers;
determining a set of parameter values associated with the second web application layer request that corresponds to the set of parameters specified by the first counting rule; and
updating the first counter in response to a determination that the set of parameter values associated with the second web application layer request is the same as the set of parameter values associated with the first counter or creating a second counter associated with the set of parameter values associated with the second web application layer request in response to a determination that a counter associated with the set of parameter values associated with the second web application layer request does not exist.

### Claim 3 (depends on 1)

The method of claim 1, further comprising:
providing one or more counters that were created based on the first counting rule, including the first counter, to a security center for analysis.

### Claim 4 (depends on 1)

The method of claim 1, wherein the set of parameters specified by the first counting rule includes one or more of: site ID, origin geolocation, destination geolocation, client type, proxy ID, Secure Sockets Layer (SSL) version, attack type, security rule ID, and point of presence (PoP) name.

### Claim 5 (depends on 1)

The method of claim 1, further comprising:
installing a security rule in the web application layer proxy, wherein the security rule refers to one or more counters that were created based on the first counting rule using a name assigned to the first counting rule.

### Claim 6 (depends on 1)

The method of claim 1, further comprising:
installing a second counting rule in the web application layer proxy, wherein the second counting rule specifies a set of parameters based upon which to create counters, wherein the set of parameters specified by the second counting rule is different from the set of parameters specified by the first counting rule.

### Claim 7 (depends on 6)

The method of claim 6, wherein a parameter value from the set of parameter values associated with the first web application layer request is only determined once for the first web application layer request even when the set of parameters specified by the second counting rule includes a parameter corresponding to the parameter value that is also included in the set of parameters specified by the first counting rule.

### Claim 8 (depends on 1)

The method of claim 1, wherein the first counter is stored in a hash table using a key that is generated based on the set of parameter values associated with the first counter.

### Claim 9 (depends on 1)

The method of claim 1, wherein the determining and creating is performed using a thread running on the web application layer proxy that is different from a thread of the web application layer proxy that applies security rules.

### Claim 10 (depends on 1)

The method of claim 1, wherein the first counting rule is installed in response to receiving a request to install the first counting rule.

### Claim 11 (depends on 10)

The method of claim 10, wherein the first counting rule is installed while the web application layer proxy is in operation.

### Claim 12

A set of one or more non-transitory machine-readable storage media storing instructions which, when executed by one or more processors of one or more network devices implementing a web application layer proxy that is communicatively coupled between one or more web application clients and one or more web application servers, causes the one or more network devices to perform operations for dynamically creating counters during runtime based on actual web application layer requests received by the web application layer proxy, the operations comprising:
installing a first counting rule in the web application layer proxy, wherein the first counting rule specifies a set of parameters based upon which to create counters;
receiving a first web application layer request generated by one of the one or more web application clients that is intended for one of the one or more web application servers;
determining a set of parameter values associated with the first web application layer request that corresponds to the set of parameters specified by the first counting rule; and
creating a first counter associated with the set of parameter values associated with the first web application layer request in response to a determination that a counter associated with the set of parameter values associated with the first web application layer request does not exist.

### Claim 13 (depends on 12)

The set of one or more non-transitory machine-readable storage media of claim 12, wherein the operations further comprise:
receiving a second web application layer request generated by one of the one or more web application clients that is intended for one of the one or more web application servers;
determining a set of parameter values associated with the second web application layer request that corresponds to the set of parameters specified by the first counting rule; and
updating the first counter in response to a determination that the set of parameter values associated with the second web application layer request is the same as the set of parameter values associated with the first counter or creating a second counter associated with the set of parameter values associated with the second web application layer request in response to a determination that a counter associated with the set of parameter values associated with the second web application layer request does not exist.

### Claim 14 (depends on 12)

The set of one or more non-transitory machine-readable storage media of claim 12, wherein the operations further comprise:
providing one or more counters that were created based on the first counting rule, including the first counter, to a security center for analysis.

### Claim 15 (depends on 12)

The set of one or more non-transitory machine-readable storage media of claim 12, wherein the set of parameters specified by the first counting rule includes one or more of: site ID, origin geolocation, destination geolocation, client type, proxy ID, Secure Sockets Layer (SSL) version, attack type, security rule ID, and point of presence (PoP) name.

### Claim 16 (depends on 12)

The set of one or more non-transitory machine-readable storage media of claim 12, wherein the operations further comprise:
installing a security rule in the web application layer proxy, wherein the security rule refers to one or more counters that were created based on the first counting rule using a name assigned to the first counting rule.

### Claim 17

A network device configured to implement a web application layer proxy that is to be communicatively coupled between one or more web application clients and one or more web application servers, wherein the web application layer proxy is configured to dynamically create counters during runtime based on actual web application layer requests received by the web application layer proxy, the network device comprising:
one or more processors; and
a non-transitory machine-readable storage medium having instructions stored therein, which when executed by the one or more processors, causes the network device implementing the web application layer proxy to:
install a first counting rule in the web application layer proxy, wherein the first counting rule specifies a set of parameters based upon which to create counters,
receive a first web application layer request generated by one of the one or more web application clients that is intended for one of the one or more web application servers,
determine a set of parameter values associated with the first web application layer request that corresponds to the set of parameters specified by the first counting rule, and
create a first counter associated with the set of parameter values associated with the first web application layer request in response to a determination that a counter associated with the set of parameter values associated with the first web application layer request does not exist.

### Claim 18 (depends on 17)

The network device of claim 17, wherein the instructions, when executed by the one or more processors, further causes the network device implementing the web application layer proxy to:
receive a second web application layer request generated by one of the one or more web application clients that is intended for one of the one or more web application servers,
determine a set of parameter values associated with the second web application layer request that corresponds to the set of parameters specified by the first counting rule, and
update the first counter in response to a determination that the set of parameter values associated with the second web application layer request is the same as the set of parameter values associated with the first counter or create a second counter associated with the set of parameter values associated with the second web application layer request in response to a determination that a counter associated with the set of parameter values associated with the second web application layer request does not exist.

### Claim 19 (depends on 17)

The network device of claim 17, wherein the instructions, when executed by the one or more processors, further causes the network device implementing the web application layer proxy to:
install a security rule in the web application layer proxy, wherein the security rule refers to one or more counters that were created based on the first counting rule using a name assigned to the first counting rule.

### Claim 20 (depends on 17)

The network device of claim 17, wherein the instructions, when executed by the one or more processors, further causes the network device implementing the web application layer proxy to:
install a second counting rule in the web application layer proxy, wherein the second counting rule specifies a set of parameters based upon which to create counters, wherein the set of parameters specified by the second counting rule is different from the set of parameters specified by the first counting rule.
