# US 2019/0377864 A1 · Multi-factor authentication devices

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

- Number: US 2019/0377864 A1
- Document ID: US20190377864A1
- Status: Published application
- Kind: A1
- Application number: 16/440,075
- Filed: 2019-06-13
- Published: 2019-12-12
- Earliest claimed: 2018-06-07
- Assignees: Capital One Services, LLC
- Applicants: Capital One Services, LLC
- Inventors: Michael MOSSOBA; Abdelkadar M'Hamed BENKREIRA; Joshua EDWARDS
- Web page: https://patentgrep.com/patent/US20190377864A1

## CPC

- H04L 63/08: {for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32)}
- H04L 63/083: {using passwords (cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226)}
- G06F 3/0622: {in relation to access}
- G06F 3/0658: {Controller construction arrangements}
- G06F 3/0673: {Single storage device}
- G06F 21/31: User authentication
- G06F 21/34: involving the use of external additional devices, e.g. dongles or smart cards
- G06F 21/40: by quorum, i.e. whereby two or more security principals are required
- G06F 21/42: using separate channels for security data
- G06F 21/554: {involving event detection and direct action}
- 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
- H04L 63/0853: {using an additional device, e.g. smartcard, SIM or a different communication terminal (cryptographic mechanisms or cryptographic arrangements for entity authentication involving additional secure or trusted devices H04L9/3234)}
- H04W 12/06: Authentication
- G06F 3/16: Sound input; Sound output (speech processing G10L)
- G06F 2221/034: Test or assess a computer or a system
- H04L 63/18: {using different networks or channels, e.g. using out of band channels (cryptographic mechanisms or cryptographic arrangements for key distribution involving distinctive intermediate devices or communication paths H04L9/0827; cryptographic mechanisms or cryptographic arrangements for authentication using a plurality of channels H04L9/3215)}
- H04L 2463/082: applying multi-factor authentication
- 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)
- 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
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

A device may receive a request from a first user device to access a protected device. The device may verify a user identity of a user of the first device based on user credentials and determine that an authentication code is needed to authenticate the request to access the protected device. The device may dynamically generate multiple codes and transmit the multiple codes to a second user device associated with the user identity of the user of the first device. A first code, of the multiple codes, may correspond to a correct authentication code needed to authenticate the request to access the protected device. The device may transmit a message including an instruction for identifying the correct authentication code from among the multiple codes, receive a second code from the first device, compare the second code and the first code, and selectively authenticate the request to access the protected device.

## Claims

### Claim 1

A method, comprising:
receiving, by a processor, a request from a first device to access a second device;
generating, by the processor, a plurality of codes based on receiving the request,
a first code, of the plurality of codes, corresponding to a correct authentication code needed to authenticate the request to access the second device,
the first code being generated using a first pseudo-random code based on user-specific data,
one or more second codes, of the plurality of codes, corresponding to one or more decoy codes, and
the one or more second codes being generated using one or more second pseudo-random codes;
transmitting, by the processor, the plurality of codes to a third device;
transmitting, by the processor, a message including an instruction for identifying the correct authentication code from among the plurality of codes using the user-specific data;
receiving, by the processor and from the first device based on transmitting the message, a third code;
comparing, by the processor, the third code and the plurality of codes; and
selectively:
authenticating, by the processor based on the third code matching the first code, the request; or
determining, by the processor based on the third code matching one of the one or more second codes, that the third device is compromised, and
requesting, by the processor and based on determining that the third device is compromised, an additional factor for authenticating the request.

### Claim 2 (depends on 1)

The method of claim 1, wherein the request is a first request;
wherein the plurality of codes a first plurality of codes;
wherein the correct authentication code is a first authentication code;
wherein the message is a first message; and
wherein the method further comprises:
receiving a second request from a fourth device to access the second device;
generating a second plurality of codes based on receiving the request,
a fourth code, of the second plurality of codes, corresponding to a second correct authentication code needed to authenticate the second request to access the second device,
the fourth code being generated using a third pseudo-random code based on the user-specific data,
one or more fifth codes, of the second plurality of codes, corresponding to one or more decoy codes, and
the one or more fifth codes being generated using one or more fourth pseudo-random codes;
transmitting the second plurality of codes to a fifth device;
transmitting a second message including an instruction for identifying the second correct authentication code from among the second plurality of codes using the user-specific data;
receiving, from the fifth device based on transmitting the second message, a sixth code;
identifying, based on the sixth code not matching the fourth code and the one or more fifth codes, the second request as a potential attempt by a hacker; and
performing, based on identifying the second request as a potential attempt by a hacker, a security action.

### Claim 3 (depends on 2)

The method of claim 2, wherein performing the security action comprises:
locking a user, associated with the user-specific data, out of an account associated with the second device.

### Claim 4 (depends on 3)

The method of claim 3, further comprising:
authenticating the user after the user is locked out of the account; and
permitting the user to access the account based on authenticating the user.

### Claim 5 (depends on 1)

The method of claim 1, where the request is a first request;
wherein the plurality of codes a first plurality of codes;
wherein the correct authentication code is a first authentication code;
wherein the message is a first message; and
wherein the method further comprises:
receiving a second request from a fourth device to access the second device;
generating a second plurality of codes based on receiving the request,
a fourth code, of the second plurality of codes, corresponding to a second correct authentication code needed to authenticate the second request to access the second device,
the fourth code being generated using a third pseudo-random code based on the user-specific data,
one or more fifth codes, of the second plurality of codes, corresponding to one or more decoy codes, and
the one or more fifth codes being generated using one or more fourth pseudo-random codes;
transmitting the second plurality of codes to a fifth device;
transmitting a second message including an instruction for identifying the second correct authentication code from among the second plurality of codes using the user-specific data;
receiving, from the fifth device, a sixth code;
determining, based on comparing the sixth code and the second plurality of codes, that the sixth code does not match the fourth code;
determining, based on comparing the sixth code and the second plurality of codes, that the sixth code comprises a threshold similarity to the fourth code; and
transmitting, to the fifth device, a third request for another code.

### Claim 6 (depends on 1)

The method of claim 1, wherein transmitting the message comprises:
transmitting the message to the first device.

### Claim 7 (depends on 1)

The method of claim 1, wherein transmitting the message comprises:
transmitting the message to the third device.

### Claim 8

An authentication device, comprising:
one or more memories; and
one or more processors communicatively coupled to the one or more memories, configured to:
receive a request from a first device to access a second device;
generate a plurality of codes based on receiving the request,
a first code, of the plurality of codes, corresponding to a correct authentication code needed to authenticate the request to access the second device,
the first code being generated using a first pseudo-random code based on user-specific data,
one or more second codes, of the plurality of codes, corresponding to one or more decoy codes, and
the one or more second codes being generated using one or more second pseudo-random codes;
transmit the plurality of codes to a third device;
transmit a message including an instruction for identifying the correct authentication code from among the plurality of codes using the user-specific data;
receive, from the first device based on transmitting the message, a third code;
compare the third code and the plurality of codes; and
selectively:
authenticate the request; or
determine that the third device is compromised, and
request, based on determining that the third device is compromised, an additional factor for authenticating the request.

### Claim 9 (depends on 8)

The authentication device of claim 8, wherein the request is a first request;
wherein the plurality of codes a first plurality of codes;
wherein the correct authentication code is a first authentication code;
wherein the message is a first message; and
wherein the one or more processors are further configured to:
receive a second request from a fourth device to access the second device;
generate a second plurality of codes based on receiving the request,
a fourth code, of the second plurality of codes, corresponding to a second correct authentication code needed to authenticate the second request to access the second device,
the fourth code being generated using a third pseudo-random code based on the user-specific data,
one or more fifth codes, of the second plurality of codes, corresponding to one or more decoy codes, and
the one or more fifth codes being generated using one or more fourth pseudo-random codes;
transmit the second plurality of codes to a fifth device;
transmit a second message including an instruction for identifying the second correct authentication code from among the second plurality of codes using the user-specific data;
receive, from the fifth device based on transmitting the second message, a sixth code;
identify, based on the sixth code not matching the fourth code and the one or more fifth codes, the second request as a potential attempt by a hacker; and
perform, based on identifying the second request as a potential attempt by a hacker, a security action.

### Claim 10 (depends on 9)

The authentication device of claim 9, wherein the one or more processors, when performing the security action, are configured to:
lock a user, associated with the user-specific data, out of an account associated with the second device.

### Claim 11 (depends on 10)

The authentication device of claim 10, wherein the one or more processors are further configured to:
authenticate the user after the user is locked out of the account; and
permit the user to access the account based on authenticating the user.

### Claim 12 (depends on 8)

The authentication device of claim 8, where the request is a first request;
wherein the plurality of codes a first plurality of codes;
wherein the correct authentication code is a first authentication code;
wherein the message is a first message; and
wherein the one or more processors are further configured to:
receive a second request from a fourth device to access the second device;
generate a second plurality of codes based on receiving the request,
a fourth code, of the second plurality of codes, corresponding to a second correct authentication code needed to authenticate the second request to access the second device,
the fourth code being generated using a third pseudo-random code based on the user-specific data,
one or more fifth codes, of the second plurality of codes, corresponding to one or more decoy codes, and
the one or more fifth codes being generated using one or more fourth pseudo-random codes;
transmit the second plurality of codes to a fifth device;
transmit a second message including an instruction for identifying the second correct authentication code from among the second plurality of codes using the user-specific data;
receive, from the fifth device, a sixth code;
determine, based on comparing the sixth code and the second plurality of codes, that the sixth code does not match the fourth code;
determine, based on comparing the sixth code and the second plurality of codes, that the sixth code comprises a threshold similarity to the fourth code; and
transmit, to the fifth device, a third request for another code.

### Claim 13 (depends on 8)

The authentication device of claim 8, wherein the one or more processors, when transmitting the message, are configured to:
transmit the message to the first device.

### Claim 14 (depends on 8)

The authentication device of claim 8, wherein the one or more processors, when transmitting the message, are configured to:
transmit the message to the third device.

### Claim 15

A non-transitory computer-readable medium storing instructions, the instructions comprising:
one or more instructions that, when executed by one or more processors, cause the one or more processors to:
receive a request from a first device to access a second device;
generate a plurality of codes based on receiving the request,
a first code, of the plurality of codes, corresponding to a correct authentication code needed to authenticate the request to access the second device,
the first code being generated using a first pseudo-random code based on user-specific data,
one or more second codes, of the plurality of codes, corresponding to one or more decoy codes, and
the one or more second codes being generated using one or more second pseudo-random codes;
transmit the plurality of codes to a third device;
transmit a message including an instruction for identifying the correct authentication code from among the plurality of codes using the user-specific data;
receive, from the first device based on transmitting the message, a third code;
compare the third code and the plurality of codes; and
selectively:
authenticate the request; or
determine that the third device is compromised, and
request, based on determining that the third device is compromised, an additional factor for authenticating the request.

### Claim 16 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein the request is a first request;
wherein the plurality of codes a first plurality of codes;
wherein the correct authentication code is a first authentication code;
wherein the message is a first message; and
wherein the one or more instructions, when executed by the one or more processors, further cause the one or more processors to:
receive a second request from a fourth device to access the second device;
generate a second plurality of codes based on receiving the request,
a fourth code, of the second plurality of codes, corresponding to a second correct authentication code needed to authenticate the second request to access the second device,
the fourth code being generated using a third pseudo-random code based on the user-specific data,
one or more fifth codes, of the second plurality of codes, corresponding to one or more decoy codes, and
the one or more fifth codes being generated using one or more fourth pseudo-random codes;
transmit the second plurality of codes to a fifth device;
transmit a second message including an instruction for identifying the second correct authentication code from among the second plurality of codes using the user-specific data;
receive, from the fifth device based on transmitting the second message, a sixth code;
identify, based on the sixth code not matching the fourth code and the one or more fifth codes, the second request as a potential attempt by a hacker; and
perform, based on identifying the second request as a potential attempt by a hacker, a security action.

### Claim 17 (depends on 16)

The non-transitory computer-readable medium of claim 16, wherein the one or more instructions, that cause the one or more processors to perform the security action, cause the one or more processors to:
lock a user, associated with the user-specific data, out of an account associated with the second device.

### Claim 18 (depends on 17)

The non-transitory computer-readable medium of claim 17, wherein the one or more instructions, when executed by the one or more processors, further cause the one or more processors to:
authenticate the user after the user is locked out of the account; and
permit the user to access the account based on authenticating the user.

### Claim 19 (depends on 15)

The non-transitory computer-readable medium of claim 15, where the request is a first request;
wherein the plurality of codes a first plurality of codes;
wherein the correct authentication code is a first authentication code;
wherein the message is a first message; and
wherein the one or more instructions, when executed by the one or more processors, further cause the one or more processors to:
receive a second request from a fourth device to access the second device;
generate a second plurality of codes based on receiving the request,
a fourth code, of the second plurality of codes, corresponding to a second correct authentication code needed to authenticate the second request to access the second device,
the fourth code being generated using a third pseudo-random code based on the user-specific data,
one or more fifth codes, of the second plurality of codes, corresponding to one or more decoy codes, and
the one or more fifth codes being generated using one or more fourth pseudo-random codes;
transmit the second plurality of codes to a fifth device;
transmit a second message including an instruction for identifying the second correct authentication code from among the second plurality of codes using the user-specific data;
receive, from the fifth device, a sixth code;
determine, based on comparing the sixth code and the second plurality of codes, that the sixth code does not match the fourth code;
determine, based on comparing the sixth code and the second plurality of codes, that the sixth code comprises a threshold similarity to the fourth code; and
transmit, to the fifth device, a third request for another code.

### Claim 20 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein the one or more instructions, that cause the one or more processors to transmit the message, cause the one or more processors to:
transmit the message to the first device.
