# US 2010/0146638 A1 · Detection filter

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

- Number: US 2010/0146638 A1
- Document ID: US20100146638A1
- Status: Published application
- Kind: A1
- Application number: 12/616,660
- Filed: 2009-11-11
- Published: 2010-06-10
- Earliest claimed: 2007-05-11
- Assignees: FMT Worldwide Pty Ltd
- Inventors: Constantine SIOURTHAS; Bjarne Staugaard Matzen
- Web page: https://patentgrep.com/patent/US20100146638A1

## CPC

- G06Q 20/4016: {involving fraud or risk level assessment in transaction processing}
- G06Q 20/04: Payment circuits
- G06Q 20/24: Credit schemes, i.e. "pay after"
- G06Q 20/40: Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q 20/405: {Establishing or using transaction specific rules}
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

A detection filter installed in an application server including a secure application is disclosed. In one embodiment, the filter includes a rules engine for receiving request data representing an access request for the secure application from a user. The engine applies at least one risk condition rule to the request data to generate a risk probability level, and detects at least one fraud condition when the risk probability level exceeds a threshold level, before passing the access request to the secure application.

## Claims

### Claim at position 1

1-35. (canceled)

### Claim 36

A filter installed in an application server including a secure application, the filter comprising a rules engine configured to i) receive request data representing an access request for the application from a user, ii) apply at least one condition rule to the request data for generating a probability level, and iii) detect at least one condition when the probability level exceeds a threshold level, before passing the access request to the application.

### Claim 37 (depends on 36)

A filter as claimed in claim 36, wherein the rules engine is further configured to access at least one of: past session data for the user in applying the at least one condition rule; and application data accessed by the application for the user in applying the at least one condition rule.

### Claim 38

(canceled)

### Claim 39 (depends on 37)

A filter as claimed in claim 37, wherein the application data for the user comprises at least one of: historical data; and account balance data.

### Claim 40

(canceled)

### Claim 41 (depends on 36)

A filter as claimed in claim 36, further comprising an input adaptor configured to receive and process the access request to provide the request data for the rules engine.

### Claim 42 (depends on 36)

A filter as claimed in claim 36, wherein the filter is configured to invoke a two-factor authentication process for confirming the identity of the user when the condition is detected.

### Claim 43 (depends on 36)

A filter as claimed in claim 36, wherein the rules engine is further configured to determine at least one of: i) an Internet Protocol (IP) address associated with the access request, ii) a change between the request data and previous request data representing a previous access request from the user; iii) a location associated with the IP address, iv) a distance between the location and a previous location associated with a previous IP address associated with the previous access request, v) a speed from the distance, a receive time of the access request and a previous receive time of the previous access request, vi) a client parameter of a client application used to generate the access request and vii) a change in the client parameter between the access request and a previous access request.

### Claim at position 10

44-49. (canceled)

### Claim 50 (depends on 43)

A filter as claimed in claim 43, wherein the client parameter is the version of a Web browser used to generate the access request.

### Claim 51 (depends on 36)

A filter as claimed in claim 36, wherein the rules engine is further configured to determine at least one of: i) a connection speed associated with the access request, ii) a speed change between the connection speed and a previous connection speed associated with a previous access request, iii) connection type associated with the access request and iv) a connection type change between the connection type and a previous connection type associated with a previous access request.

### Claim at position 13

52-54. (canceled)

### Claim 55 (depends on 5351)

A filter as claimed in claim 5351, wherein the rules engine is further configured to determine at least one of: i) when the access request is associated with a public hot-spot connection and ii) when the access request is associated with a satellite connection.

### Claim 56

(canceled)

### Claim 57 (depends on 43)

A filter as claimed in claim 43, wherein the rules engine is further configured to determine a blacklist match between the IP address and an IP address blacklist.

### Claim 58 (depends on 36)

A filter as claimed in claim 36, wherein the probability level is generated using data produced by applying the at least one condition rule.

### Claim 59 (depends on 36)

A filter as claimed in claim 36, wherein the rules engine is further configured to deny access to the application for the user when the condition is detected.

### Claim 60

(canceled)

### Claim 61 (depends on 36)

A filter as claimed in claim 36, wherein the filter is configured to invoke an alert generation process for alerting a party when the condition is detected, before passing the access request to the application.

### Claim 62 (depends on 61)

A filter as claimed in claim 61, wherein the alert generation process comprises generating an email alert or an SMS alert.

### Claim 63 (depends on 36)

A filter as claimed in claim 36, wherein the rules engine is further
generate a first probability level by applying a first condition rule to the request data;
select a second condition rule based on the first probability level; and
apply the second condition rule to the request data for generating a second probability level.

### Claim 64

A management server for generating an interface to adjust and set at least one condition rule, wherein the management server comprises:
a filter installed in an application server including a secure application, the filter comprising a rules engine configured to i) receive request data representing an access request for the application from a user, ii) apply at least one condition rule to the request data for generating a probability level, and iii) detect at least one condition when the probability level exceeds a threshold level, before passing the access request to the application.

### Claim 65 (depends on 64)

A management server as claimed in claim 64, wherein the interface comprises tools to adjust the dependence and connections between condition rules used to generate the probability level.

### Claim 66

A filter system comprising:
a filter installed in an application server including a secure application, the filter comprising a rules engine configured to i) receive request data representing an access request for the application from a user, ii) apply at least one condition rule to the request data for generating a probability level, and iii) detect at least one condition when the probability level exceeds a threshold level, before passing the access request to the application; and
a management server configured to generate an interface to adjust and set the at least one condition rule.

### Claim 67

An application server including:
an application for access by a user; and
a filter installed in an application server including a secure application, the filter comprising a rules engine configured to i) receive request data representing an access request for the application from a user, ii) apply at least one condition rule to the request data for generating a probability level, and iii) detect at least one condition when the probability level exceeds a threshold level, before passing the access request to the application.

### Claim 68

A method of detecting a condition, performed by an application server, the method comprising:
receiving request data representing an access request from a user for an application of the application server;
applying at least one condition rule to the request data for generating a probability level; and
detecting the condition when the probability level exceeds a threshold level, before granting access to the application.

### Claim 69 (depends on 68)

A method as claimed in claim 68, further comprising: applying the at least one condition rule to subsequent access requests during a transaction session with the application before passing the access requests to the application.

### Claim 70 (depends on 68)

A method as claimed in claim 68, wherein the applying the at least one condition rule comprises accessing past transaction session data for the user.
