IP Library Granted Patent US 11,075,899
Granted Patent B2
US 11,075,899 · App. 16/394,279 · Granted Jul 27, 2021

Cloud authentication

Inventor: Bjorn Markus Jakobsson (Portola Valley, CA)
Assignee: RavenWhite Security, Inc.
H04L63/083G06F21/31G06F21/552G06F21/60H04L9/0891H04L63/1483G06F2221/2131H04K1/00H04L2209/56H04L2209/605H04L2209/805H04W4/02
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,075,899
App. No.
16/394,279
Granted
Jul 27, 2021
Kind
B2
Abstract

A cloud authentication system is disclosed. A request for an authentication setup for a first user of a first service provider is received. Additional information, such as authentication criteria, can further be received, such as from the first service provider. A set of stimuli to associate with a first user profile of the first user of the first service provider is stored.

Claims (58)

1. A cloud authentication system, comprising:

a processor configured to:

receive a request for authentication setup for a first user of a first service provider;

generate a first set of stimuli to associate with a first user profile of the first user of the first service provider, wherein the first set of stimuli is generated based at least in part on at least one of (1) publicly accessible information associated with the first user and (2) information associated with the first user that is provided by the first service provider;

receive a first request to authenticate, on behalf of the first service provider, a first entity purporting to be the first user;

receive an indication of a perceived threat; and

determine, based at least in part on the perceived threat, whether a stimulus in the first set of stimuli should be presented to the entity purporting to be the first user for classification; and

a memory coupled to the processor and configured to the processor to provide the processor with instructions.

2. The cloud authentication system recited in claim 1 wherein the processor is configured to:

determine a type of the perceived threat; and

based at least in part on the type of the perceived threat, determine whether the stimulus should be presented for classification.

3. The cloud authentication system recited in claim 2 wherein the processor is further configured to determine the type of the perceived threat at least in part by reviewing at least one of (1) an IP address of an access, (2) a type of transaction requested, and (3) recent activity associated with the first user.

4. The cloud authentication system recited in claim 1 wherein the processor is configured to:

determine that the perceived threat is that the first user is being impersonated by malware; and

based at least in part on the determination that the perceived threat is that the first user is being impersonated by malware, determine that the stimulus should be presented for classification.

5. The cloud authentication system recited in claim 1 wherein the processor is configured to:

determine that the perceived threat is that the first user is being impersonated by an entity that is likely to know preferences of the first user; and

based at least in part on the determination that the perceived threat is that the first user is being impersonated by an entity that is likely to know preferences of the first user, determine that the stimulus should not be presented for classification.

6. The cloud authentication system recited in claim 1 wherein the processor is further configured to determine whether the stimulus should be presented for classification based at least in part on a first set of policies associated with the first service provider.

7. The cloud authentication system recited in claim 6 wherein the first set of policies is provided to the cloud authentication system by the first service provider.

8. The cloud authentication system recited in claim 1 wherein the processor is further configured to:

receive a second request to authenticate, on behalf of a second service provider different from the first service provider, a second entity purporting to be a second user; and

in response to the second request to authenticate, select at least some stimuli in a second set of stimuli to be presented to the entity purporting to be the second user, wherein the at least some stimuli in the second set of stimuli are selected based at least in part on a second set of policies associated with the second service provider.

9. The cloud authentication system recited in claim 1 wherein the processor is configured to obtain the publicly accessible information associated with the first user at least in part by scraping a website.

10. The cloud authentication system recited in claim 1 wherein the processor is further configured to:

obtain information associated with the first user via an agent on a client associated with the first user; and

use the information obtained via the agent to generate at least a portion of the first set of stimuli.

11. A method, comprising:

receiving a request for authentication setup for a first user of a first service provider;

generating a first set of stimuli to associate with a first user profile of the first user of the first service provider, wherein the first set of stimuli is generated based at least in part on at least one of (1) publicly accessible information associated with the first user and (2) information associated with the first user that is provided by the first service provider;

receiving a first request to authenticate, on behalf of the first service provider, a first entity purporting to be the first user;

receiving an indication of a perceived threat; and

determining, based at least in part on the perceived threat, whether a stimulus in the first set of stimuli should be presented to the entity purporting to be the first user for classification.

12. The method of claim 11 , comprising:

determining a type of the perceived threat; and

based at least in part on the type of the perceived threat, determining whether the stimulus should be presented for classification.

13. The method of claim 12 , comprising determining the type of the perceived threat at least in part by reviewing at least one of (1) an IP address of an access, (2) a type of transaction requested, and (3) recent activity associated with the first user.

14. The method of claim 11 , comprising:

determining that the perceived threat is that the first user is being impersonated by malware; and

based at least in part on the determination that the perceived threat is that the first user is being impersonated by malware, determining that the stimulus should be presented for classification.

15. The method of claim 11 , comprising:

determining that the perceived threat is that the first user is being impersonated by an entity that is likely to know preferences of the first user; and

based at least in part on the determination that the perceived threat is that the first user is being impersonated by an entity that is likely to know preferences of the first user, determining that the stimulus should not be presented for classification.

16. The method of claim 11 , further comprising determining whether the stimulus should be presented for classification based at least in part on a first set of policies associated with the first service provider.

17. The method of claim 16 wherein the first set of policies is provided to a cloud authentication system by the first service provider.

18. The method of claim 11 , further comprising:

receiving a second request to authenticate, on behalf of a second service provider different from the first service provider, a second entity purporting to be a second user; and

in response to the second request to authenticate, selecting at least some stimuli in a second set of stimuli to be presented to the entity purporting to be the second user, wherein the at least some stimuli in the second set of stimuli are selected based at least in part on a second set of policies associated with the second service provider.

19. The method of claim 11 , comprising obtaining the publicly accessible information associated with the first user at least in part by scraping a website.

20. The method of claim 11 , further comprising:

obtaining information associated with the first user via an agent on a client associated with the first user; and

using the information obtained via the agent to generate at least a portion of the first set of stimuli.

21. A computer program product embodied in a tangible, non-transitory computer readable storage medium and comprising computer instructions for:

receiving a request for authentication setup for a first user of a first service provider;

generating a first set of stimuli to associate with a first user profile of the first user of the first service provider, wherein the first set of stimuli is generated based at least in part on at least one of (1) publicly accessible information associated with the first user and (2) information associated with the first user that is provided by the first service provider;

receiving a first request to authenticate, on behalf of the first service provider, a first entity purporting to be the first user;

receiving an indication of a perceived threat; and

determining, based at least in part on the perceived threat, whether a stimulus in the first set of stimuli should be presented to the entity purporting to be the first user for classification.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 21, 2026
From: JAKOBSSON, BJORN MARKUS
To: RAVENWHITE SECURITY, INC.
Reel/Frame 075334/0716 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 21, 2026
From: RAVENWHITE SECURITY, INC.
To: NUECES BLOCKCHAIN LLC
Reel/Frame 075334/0752 →
CHANGE OF NAME Recorded May 24, 2019
From: RAVENWHITE INC.
To: RAVENWHITE SECURITY, INC.
Reel/Frame 049287/0025 →
Continuity (11)
Continuation 14736156 · Jun 10, 2015
Continuation 13370078 · Feb 9, 2012
Continuation In Part 12215048 · Jun 23, 2008
Continuation In Part 11890408 · Aug 6, 2007
Continuation In Part 13161184 · Jun 15, 2011
Provisional Application 61441562 · Feb 10, 2011
Provisional Application 60967675 · Sep 6, 2007
Provisional Application 60918781 · Mar 19, 2007
Provisional Application 60836641 · Aug 9, 2006
Provisional Application 61355149 · Jun 16, 2010
Related Publication 20190281042A1 · Sep 12, 2019