# US 8,788,427 B2 · Limiting data exposure in authenticated multi-system transactions

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

- Number: US 8,788,427 B2
- Document ID: US8788427B2
- Status: Granted
- Kind: B2
- Application number: 13/475,494
- Filed: 2012-05-18
- Published: 2013-11-21
- Granted: 2014-07-22
- Earliest claimed: 2012-05-18
- Assignees: The Active Network, Inc.
- Applicants: Doug Johnson
- Inventors: Doug Johnson
- Web page: https://patentgrep.com/patent/US8788427B2

## CPC

- G06Q 20/385: {using an alias or single-use codes}
- G06F 21/335: {for accessing specific resources, e.g. using Kerberos tickets}
- 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
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

The limiting of data exposure in authenticated multi-system transactions is disclosed. A client system authenticates and requests secured data and unsecured data with an initial system. The initial system transmits to an external system a token request that corresponds to the request for the secured data. A token is generated and passed to the initial system, which relays the same to the client system. The client system uses the token to access the secured data on the external system, while also retrieving the unsecured data on the initial system. The initial system thus does not have access to the secured data, while the request therefor is known.

## Claims

### Claim 1

A method for limiting exposure of secured data in an authenticated transaction over multiple systems, the method comprising:
receiving a transaction request from an authenticated user of a client system on an initial system;
deriving from the transaction request a first request for the secured data stored on an external system independent of the initial system and a second request for unsecured data stored on the initial system, the first request and the second request being combined in the transaction request;
transmitting to the external system a token request corresponding to the first request for the secured data, the external system being configured to generate a token associated with the token request;
receiving on the initial system the generated token from the external system; and
transmitting from the initial system to the client system the token and the requested unsecured data stored on the initial system;
wherein the token is presentable by the client system to the external system to retrieve the secured data stored on the external system independently of the transmission of the unsecured data upon validation of the token thereby by the external system.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
transmitting a location identifier for the external system to the client system;
wherein the client system initiates a request for the secured data based upon the provided location identifier for the external system.

### Claim 3 (depends on 1)

The method of claim 1, further comprising:
storing in an audit log on the initial system the token and the token request corresponding to the first request for the secured data.

### Claim 4 (depends on 1)

The method of claim 1, further comprising:
establishing a secured trusted data communications link between the initial system and the external system.

### Claim 5 (depends on 1)

The method of claim 1, further comprising:
establishing a secured trusted data communications link between the initial system and the client system.

### Claim 6 (depends on 1)

The method of claim 1, wherein the requested unsecured data includes a placeholder for the requested secured data.

### Claim 7 (depends on 1)

The method of claim 1, further comprising:
receiving a validation request from the external system generated in response to the client system presenting the token to the external system, the validation request including the token as received by the external system from the client system;
confirming the validation request; and
transmitting a transaction validity response to the external system upon confirmation of the validation request.

### Claim 8 (depends on 1)

The method of claim 1, wherein the token is single-use and newly generated for each token request.

### Claim 9 (depends on 1)

The method of claim 1, wherein the user has a first account established on the initial system independently of the external system.

### Claim 10 (depends on 9)

The method of claim 9, wherein the user has a second account established on the external system, the token being presentable by the client system to the external system upon authentication of the user to the second account, and the token request including an identifier of the second account.

### Claim 11

An article of manufacture comprising a non-transitory program storage medium readable by a computer, the medium tangibly embodying one or more programs of instructions executable by the computer to perform a method for limiting exposure of secured data in an authenticated transaction over multiple systems, the method comprising:
receiving a transaction request from an authenticated user of a client system on an initial system;
deriving from the transaction request a first request for the secured data stored on an external system independent of the initial system and a second request for unsecured data stored on the initial system, the first request and the second request being combined in the transaction request;
transmitting to the external system a token request corresponding to the first request for the secured data, the external system being configured to generate a token associated with the token request;
receiving on the initial system the generated token from the external system; and
transmitting from the initial system to the client system the token and the requested unsecured data stored on the initial system;
wherein the token is presentable by the client system to the external system to retrieve the secured data stored on the external system independently of the transmission of the unsecured data upon validation of the token by the external system.