# US 2014/0230051 A1 · Fraud detection for identity management systems

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

- Number: US 2014/0230051 A1
- Document ID: US20140230051A1
- Status: Published application
- Kind: A1
- Application number: 13/763,553
- Filed: 2013-02-08
- Published: 2014-08-14
- Earliest claimed: 2013-02-08
- Assignees: Apple Inc.
- Applicants: Apple Inc.
- Inventors: Saravanan Vallinayagam; Gunaranjan Chandraraju; Selvarajan Subramaniam; Lon S. Hardeman; Vinamra Agarwal; Hai-Tao Li; Umesh Batra; Prabhakaran Vaidyanathaswami
- Web page: https://patentgrep.com/patent/US20140230051A1

## CPC

- H04L 63/1416: {Event detection, e.g. attack signature detection}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Systems, methods and computer program products for identifying and remediating in real-time (or near real-time) fraudulent activities associated with identity management systems are disclosed. An event (e.g., client request to logon to an account) is received during a time interval. An abnormal pattern in one or more characteristics of the event is determined. The event is associated with a client identity. One or more reputation scores for the client identity are determined based on event history data associated with the client identity. One or more state objects for one or more client identifier attributes are updated with the reputation scores. One or more remedial actions are implemented against the client request using the one or more updated state objects.

## Claims

### Claim 1

A method comprising:
receiving a request to process an event during a time interval;
determining an abnormal pattern in one or more characteristics of the event;
determining a reputation score of a client identity associated with the event based on event history associated with the client identity;
updating a state object with the reputation score; and
implementing a remedial action using the updated state object, where the method is performed by one or more hardware processors.

### Claim 2 (depends on 1)

The method of claim 1, where determining an abnormal pattern in one or more characteristics of the event, further comprises:
analyzing the attributes using a Markov chain model.

### Claim 3 (depends on 1)

The method of claim 1, where determining an abnormal pattern in one or more characteristics of the event, further comprises:
determining that a threshold number of the attributes are determined to be abnormal relative to other attributes received during the time interval.

### Claim 4 (depends on 1)

The method of claim 1, where the event is a client request to log into an account.

### Claim 5 (depends on 1)

The method of claim 1, where determining a reputation score of the client identity based on event history, further comprises:
generating a score for the client identity that indicates a level of abnormality.

### Claim 6 (depends on 4)

The method of claim 4, wherein implementing a remedial action using the updated state object includes denying the client request.

### Claim 7 (depends on 4)

The method of claim 4, wherein implementing a remedial action using the updated state object includes requiring authentication of a user associated with the client request.

### Claim 8 (depends on 4)

The method of claim 4, wherein implementing a remedial action using the updated state object includes resetting a password associated with the account.

### Claim 9 (depends on 4)

The method of claim 4, wherein implementing a remedial action using the updated state object includes generating an alert or notification.

### Claim 10 (depends on 4)

The method of claim 4, wherein implementing a remedial action using the updated state object includes adding the client identity to a list of client identities associated with fraudulent events.

### Claim 11

A system comprising:
one or more processors;
memory coupled to the one or more processors and configured to store instructions, which, when executed by the one or more processors, causes the one or more processors to perform operations comprising:
receiving a request to process an event during a time interval;
determining an abnormal pattern in one or more characteristics of the event;
determining a reputation score of a client identity associated with the event based on event history associated with the client identity;
updating a state object with the reputation score; and
implementing a remedial action using the updated state object.

### Claim 12 (depends on 11)

The system of claim 11, where determining an abnormal pattern in one or more characteristics of the event, further comprises:
analyzing the attributes using a Markov chain model.

### Claim 13 (depends on 11)

The system of claim 11, where determining an abnormal pattern in one or more characteristics of the event, further comprises:
determining that a threshold number of the attributes are determined to be abnormal relative to other attributes received during the time interval.

### Claim 14 (depends on 11)

The system of claim 11, where the event is a client request to log into an account.

### Claim 15 (depends on 11)

The system of claim 11, where determining a reputation of the client identity based on the client request history, further comprises:
generating a score for the client identity that indicates a level of abnormality.

### Claim 16 (depends on 14)

The system of claim 14, wherein implementing a remedial action using the updated state object includes denying the client request.

### Claim 17 (depends on 14)

The system of claim 14, wherein implementing a remedial action using the updated state object includes requiring authentication of a user associated with the client request.

### Claim 18 (depends on 14)

The system of claim 14, wherein implementing a remedial action using the updated state object includes resetting a password associated with the account.

### Claim 19 (depends on 14)

The system of claim 14, wherein implementing a remedial action using the updated state object includes generating an alert or notification.

### Claim 20 (depends on 14)

The system of claim 14, wherein implementing a remedial action against using the updated state object includes adding the client identity to a list of client identities associated with fraudulent events.
