# US 2010/0146612 A1 · Method and apparatus for trust-based, fine-grained rate limiting of network requests

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

- Number: US 2010/0146612 A1
- Document ID: US20100146612A1
- Status: Published application
- Kind: A1
- Application number: 12/705,365
- Filed: 2010-02-12
- Published: 2010-06-10
- Earliest claimed: 2003-11-18
- Assignees: AOL Inc.
- Inventors: Christopher Newell TOOMEY
- Web page: https://patentgrep.com/patent/US20100146612A1

## CPC

- H04L 63/08: {for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32)}
- G06F 21/31: User authentication
- G06F 21/33: using certificates
- H04L 9/002: {Countermeasures against attacks on cryptographic mechanisms (network architectures or network communication protocols for protection against malicious traffic H04L63/1441)}
- H04L 9/3234: {involving additional secure or trusted devices, e.g. TPM, smartcard, USB or software token (network architectures or network communication protocols for supporting authentication of entities using an additional device in a packet data network H04L63/0853)}
- H04L 9/3297: {involving time stamps, e.g. generation of time stamps}
- H04L 63/123: {received data contents, e.g. message integrity}
- H04L 63/126: {the source of the received data}
- H04L 63/1458: {Denial of Service}
- H04L 2209/42: Anonymization, e.g. involving pseudonyms
- H04L 2209/76: Proxy, i.e. using intermediary entity to perform cryptographic operations
- H04L 2209/80: Wireless
- 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

A method and apparatus for fine-grained, trust-based rate limiting of network requests distinguishes trusted network traffic from untrusted network traffic at the granularity of an individual user/machine combination, so that network traffic policing measures are readily implemented against untrusted and potentially hostile traffic without compromising service to trusted users. A server establishes a user/client pair as trusted by issuing a trust token to the client when successfully authenticating to the server for the first time. Subsequently, the client provides the trust token at login. At the server, rate policies apportion bandwidth according to type of traffic: network requests that include a valid trust token are granted highest priority. Rate policies further specify bandwidth restrictions imposed for untrusted network traffic. This scheme enables the server to throttle untrusted password-guessing requests from crackers without penalizing most friendly logins and only slightly penalizing the relatively few untrusted friendly logins.

## Claims

### Claim 1

A method of limiting unauthorized network requests, comprising the steps of:
issuing a trust token to each unique user ID-client machine combination successfully authenticating to a network service to establish said each unique user ID-machine combination as a trusted entity, said trust token comprising at least one client-originated item of data that uniquely identifies said client machine;
responsive to a determination that a network request received from a user ID-client machine combination is unaccompanied by a valid trust token, adding a specified amount of incremental response latency when processing said network request that is unaccompanied by said valid trust token.

### Claim 2 (depends on 1)

The method of claim 1, further comprising the step of:
transmitting said each trust token via a secure channel from said network service to said each unique user ID-client machine pair upon successful authentication to said network service by said each unique user ID-client machine pair.

### Claim 3 (depends on 1)

The method of claim 1, further comprising the step of:
storing said each issued trust token at said each unique user ID-client machine pair.

### Claim 4 (depends on 1)

The method of claim 1, further comprising the step of storing said issued trust token in a server side database, indexed according to a combination of user ID and said at least one item of client-originated data that uniquely identifies said client machine.

### Claim 5 (depends on 4)

The method of claim 4, further comprising the steps of:
transmitting said user ID and at least one item of client-originated data that uniquely identifies said client machine to said server; and
retrieving said stored trust token from said server-side database.

### Claim 6 (depends on 1)

The method of claim 1, wherein said network service comprises a server.

### Claim 7 (depends on 1)

The method of claim 1, wherein said trust token comprises a data object containing said at least one item of client-originated data that uniquely identifies said each client machine.

### Claim 8 (depends on 7)

The method of claim 7, said data object further comprising any of:
said user ID
a derivative of said user ID;
a time stamp of first authentication to said network service by said trusted entity; and
a time stamp of a most recent authentication to said network service by said trusted entity.

### Claim 9 (depends on 8)

The method of claim 8, wherein said derivative comprises a cryptographic hash of the user ID.

### Claim 10 (depends on 1)

The method of claim 1, further comprising a step of encrypting said trust token.

### Claim 11 (depends on 1)

The method of claim 1, further comprising the step of:
transmitting said issued trust token along with said user ID, authentication credentials, and said at least one item of client-originated data that uniquely identifies said machine to said network service.

### Claim 12 (depends on 1)

The method of claim 1, further comprising the steps of:
validating said each trust token received at said network service with a request from said each unique user ID-client machine pair; and
processing said request without adding incremental response latency.

### Claim 13 (depends on 12)

The method of claim 12, wherein said step of validating said trust token comprises the step of:
verifying that the user ID and said at least one item of client-originated data that uniquely identifies said client machine in the trust token match those presented with said request.

### Claim 13 (depends on 12)

The method of claim 12, wherein said step of validating said trust token further comprises any of the steps of:
verifying that a time stamp of a first authentication by said trusted entity recorded in the trust token is no earlier than a configurable earliest acceptable first-authentication time stamp; and
verifying that a time stamp of a last authentication by said trusted entity recorded in the trust token is no earlier than a configurable earliest acceptable last-authentication time stamp.

### Claim 14 (depends on 1)

The method of claim 1, further comprising the step of:
updating said trust token after a login by a trusted entity.

### Claim 15

A computer program product comprising computer readable code means embodied on a tangible medium, said computer readable code means comprising code for performing a method of limiting unauthorized network requests, said method comprising the steps of:
issuing a trust token to each unique user ID-client machine combination successfully authenticating to a network service to establish said each unique user ID-machine combination as a trusted entity, said trust token comprising at least one client-originated item of data that uniquely identifies said client machine;
responsive to a determination that a network request received from a user ID-client machine combination is unaccompanied by a valid trust token, adding a specified amount of incremental response latency when processing said network request that is unaccompanied by said valid trust token.

### Claim 16

A method of establishing an entity requesting a network service as trusted, comprising the steps of:
for each successful authentication, adding or updating a database record containing at least a user identifier, an originating network address and a date/timestamp of first and/or the current successful authentication;
comparing all subsequent authentication requests to said record; and
where the user identifier of a subsequent request matches that of a successful authentication, extending trust to the subsequent request if its originating network address and timestamp information satisfy predetermined criteria in relation to said record.

### Claim 17 (depends on 16)

The method of claim 16, wherein said step of adding or updating a database record comprises either of the steps of:
creating a new record by said network service if an entity has not previously authenticated to said network service; and
updating a previously created record for subsequent authentication requests from said entity.

### Claim 18 (depends on 16)

The method of claim 16, wherein the step of extending trust to the subsequent request comprises any of the steps of:
extending trust if the user identification and originating network address match those of the record exactly, and wherein the data/timestamps from the record satisfy configurable bounds checks; and
when the user identifier of the subsequent request matches that of a record, determining a trusted address range for the user identifier from stored authentication records; and
if the timestamps pass configurable bounds checks, extending trust to the request.

### Claim 19 (depends on 18)

The method of claim 18, wherein the step of extending trust to the subsequent request further comprises the step of:
if the originating address of the subsequent request falls within the trusted address range, and
determining if the data/timestamps for the trusted address range satisfy configurable bounds checks.

### Claim 21 (depends on 19)

The method of claim 19, wherein the step of determining if the data/timestamps for the trusted address range satisfy configurable bounds checks comprises the steps of:
establishing earliest date/timestamp for the trusted IP range as a minimum for the earliest authentication timestamp; and
establishing earliest date/timestamp for the trusted IP range as a maximum for the earliest authentication timestamp.

### Claim 22 (depends on 16)

The method of claim 16, wherein the entity comprises a user requesting the network service from an anonymous client.

### Claim 23 (depends on 16)

The method of claim 16, further comprising the steps of:
processing requests from trusted entities according to a first policy; and
processing remaining requests according to at least a second policy.

### Claim 24 (depends on 23)

The method of claim 23, wherein processing remaining requests according to at least a second policy comprises any of the steps of:
adding a configurable amount of incremental response latency when processing untrusted logins; and
adding a configurable amount of incremental response latency when processing requests from IP addresses that have exceeded a configurable login rate.
