# US 2015/0106899 A1 · System and method for cross-cloud identity matching

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

- Number: US 2015/0106899 A1
- Document ID: US20150106899A1
- Status: Published application
- Kind: A1
- Application number: 14/508,325
- Filed: 2014-10-07
- Published: 2015-04-16
- Earliest claimed: 2013-10-10
- Assignees: Mainsoft R&D Ltd.
- Applicants: Mainsoft R&D Ltd.
- Inventors: Roy Sheinfeld
- Web page: https://patentgrep.com/patent/US20150106899A1

## CPC

- H04L 63/10: {for controlling access to devices or network resources}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A system and method for cross-cloud identity matching are provided. The method includes receiving at least one user identifier of a user of a client node; determining at least one cloud-based resource accessed by the client node; selecting a cloud-based resource of the at least one accessed cloud-based resource; extracting at least one possible user identity of the user from the selected cloud-based resource; identifying at least one user identifier of the extracted at least one possible user identity; matching between each identified user identifier and the at least one received user identifier; determining whether each possible user identity is associated with the user respective of the matching; and upon determining that at least one possible user identity is associated with the user, storing each associated user identity respective of the client node.

## Claims

### Claim 1

A method for cross-cloud identity matching, comprising:
receiving at least one user identifier of a user of a client node;
determining at least one cloud-based resource accessed by the client node;
selecting a cloud-based resource of the at least one accessed cloud-based resource;
extracting at least one possible user identity of the user from the selected cloud-based resource;
identifying at least one user identifier of the extracted at least one possible user identity;
matching between each identified user identifier and the at least one received user identifier;
determining whether each possible user identity is associated with the user respective of the matching; and
upon determining that at least one possible user identity is associated with the user, storing each associated user identity respective of the client node.

### Claim 2 (depends on 1)

The method of claim 1, wherein the at least one user identifier is received from an agent installed on the client node.

### Claim 3 (depends on 1)

The method of claim 1, wherein each of the at least one received user identifier and the at least one identified user identifier is any one of: a personal parameter, a professional parameter, an email address, and a profile photo.

### Claim 4 (depends on 3)

The method of claim 3, wherein the personal parameter is any one of: a name, an age, a gender, a hobby, and a hometown.

### Claim 5 (depends on 3)

The method of claim 3, wherein the professional parameter is any one of: a profession, a type of work, and a location of the user's work.

### Claim 6 (depends on 1)

The method of claim 1, wherein a possible user identity is determined to be associated with the user upon determining that the matching at least one identified user identifier and the at least one received user identifier exceeds a verification threshold.

### Claim 7 (depends on 6)

The method of claim 6, wherein the verification threshold is any one of: a number of user identifiers that demonstrate matching above a matching threshold, and a degree of matching between user identifiers.

### Claim 8 (depends on 1)

The method of claim 1, wherein determining whether each possible user identity is associated with the user further comprises:
providing each associated user identity to a user; and
upon receiving a confirmation from the user that the associated user identity is associated with the user, determining that the associated user identity is associated with the user.

### Claim 9 (depends on 1)

The method of claim 1, further comprising at least one of: tokenizing the received at least one user identifier and parsing the received at least one user identifier.

### Claim 10 (depends on 1)

A non-transitory computer readable medium having stored thereon instructions for causing one or more processing units to execute the method according to claim 1.

### Claim 11

A system for cross-cloud identity matching, comprising:
a processing system; and
a memory communicatively connected to the processing system, the memory containing instructions that, when executed by the processing system, configure the system to:
receive at least one user identifier of a user of a client node;
determine at least one cloud-based resource accessed by the client node;
select a cloud-based resource of the at least one accessed cloud-based resource;
extract at least one possible user identity of the user from the selected cloud-based resource;
identify at least one user identifier of the extracted at least one possible user identity;
match between each identified user identifier and the at least one received user identifier;
determine whether each possible user identity is associated with the user respective of the matching; and
upon determining that at least one possible user identity is associated with the user, store each associated user identity respective of the client node.

### Claim 12 (depends on 11)

The system of claim 11, wherein the at least one user identifier is received from an agent installed on the client node.

### Claim 13 (depends on 11)

The system of claim 11, wherein each of the at least one received user identifier and the at least one identified user identifier is any one of: a personal parameter, a professional parameter, an email address, and a profile photo.

### Claim 14 (depends on 13)

The system of claim 13, wherein the personal parameter is any one of: a name, an age, a gender, a hobby, and a hometown.

### Claim 15 (depends on 13)

The system of claim 13, wherein the professional parameter is any one of: a profession, a type of work, and a location of the user's work.

### Claim 16 (depends on 11)

The system of claim 11, wherein a possible user identity is determined to be associated with the user upon determining that the matching at least one identified user identifier and the at least one received user identifier exceeds a verification threshold.

### Claim 17 (depends on 16)

The system of claim 16, wherein the verification threshold is any one of: a number of user identifiers that demonstrate matching above a matching threshold, and a degree of matching between user identifiers.

### Claim 18 (depends on 11)

The system of claim 11, wherein the system is further configured to:
provide each associated user identity to a user; and
upon receiving a confirmation from the user that the associated user identity is associated with the user, determine that the associated user identity is associated with the user.

### Claim 19 (depends on 11)

The system of claim 11, wherein the system is further configured to perform at least one of: tokenize the received at least one user identifier, and parse the received at least one user identifier

### Claim 20 (depends on 11)

The system of claim 11, wherein the client node further comprises an agent configured to collect the at least one user identifier of the user of the client node.
