IP Library Granted Patent US 10,616,214
Granted Patent B1
US 10,616,214 · App. 15/346,748 · Granted Apr 7, 2020

Systems and methods for preventing loss of possession factors

Inventors: Kevin Jiang (San Mateo, CA); Ilya Sokolov (Boston, MA)
Assignee: NortonLifeLock Inc.
H04L63/0853H04L63/083H04W12/06H04L2463/082
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 10,616,214
App. No.
15/346,748
Granted
Apr 7, 2020
Kind
B1
Abstract

The disclosed computer-implemented method for preventing loss of possession factors may include (i) identifying an account of a user that is associated with a possession factor that is used by the user to perform a multi-factor authentication procedure that is required when accessing the account of the user, (ii) monitoring one or more attributes of at least one of the user and the possession factor, (iii) determining, based at least in part on the one or more attributes of at least one of the user and the possession factor, that the possession factor has likely been lost, and (iv) performing a security action in response to determining that the possession factor has likely been lost to prevent the user from being unable to perform the multi-factor authentication procedure. Various other methods, systems, and computer-readable media are also disclosed.

Claims (92)

1. A computer-implemented method for preventing loss of possession factors, at least a portion of the method being performed by a computing device comprising at least one processor, the method comprising:

identifying an account of a user that is associated with a username, a password, and a possession factor that generates one-time-use passwords, wherein the username, the password, and a one-time-use password generated by the possession factor are used by the user to perform a multi-factor authentication procedure that is required when accessing the account of the user;

monitoring an additional attribute of at least one of the user or the possession factor, the additional attribute comprising one of:

an initial phone number that enables the possession factor to receive the one-time-use passwords;

a cellular service that enables the possession factor to receive the one-time-use passwords;

a physical location that enables the possession factor to connect to the cellular service and receive the one-time-use passwords;

a physical address that enables the possession factor to connect to the cellular service and receive the one-time-use passwords; or

an installation status of the possession factor that enables the possession factor to generate the one-time-use passwords;

detecting, based at least in part on a change of the additional attribute, that the user is likely unable to use the possession factor to generate the one-time-use passwords; and

performing, in response to detecting that the user is likely unable to use the possession factor to generate the one-time-use passwords, a security action to prevent the user from being unable to perform the multi-factor authentication procedure.

2. The computer-implemented method of claim 1 , wherein:

the account of the user is associated with an additional possession factor;

either one of the possession factor and the additional possession factor can be used by the user to generate the one-time-use passwords; and

the security action prevents the possession factor and the additional possession factor from becoming simultaneously lost.

3. The computer-implemented method of claim 2 , wherein performing the security action comprises:

notifying the user of the user's likely inability to use the possession factor to generate the one-time-use passwords; and

instructing the user to:

access the account of the user using the additional possession factor; and

register a backup possession factor to replace the possession factor.

4. The computer-implemented method of claim 1 , wherein:

the possession factor comprises a mobile phone that was initially associated with the initial phone number;

monitoring the additional attribute comprises monitoring, as part of an application installed on the mobile phone, a current phone number that is currently associated with the mobile phone; and

detecting that the user is likely unable to use the possession factor to generate the one-time-use passwords comprises detecting that the current phone number is not the same as the initial phone number.

5. The computer-implemented method of claim 1 , wherein:

the possession factor comprises a mobile phone that was associated with the initial phone number;

monitoring the additional attribute factor comprises monitoring, as part of an application installed on the mobile phone, the physical location of the mobile phone; and

detecting that the user is likely unable to use the possession factor to generate the one-time-use passwords comprises detecting a change in the physical location of the mobile phone that indicates that the cellular service associated with the initial phone number has likely been lost.

6. The computer-implemented method of claim 1 , wherein:

the possession factor comprises a mobile phone that was initially associated with the initial phone number;

monitoring the additional attribute comprises monitoring the physical address of the user; and

detecting that the user is likely unable to use the possession factor to generate the one-time-use passwords comprises detecting a change in the physical address of the user that indicates that the cellular service associated with the initial phone number has likely been lost.

7. The computer-implemented method of claim 1 , wherein:

the possession factor comprises a mobile phone that was initially associated with the initial phone number;

monitoring the additional attribute comprises monitoring a service status of the initial phone number; and

detecting that the user is likely unable to use the possession factor to generate the one-time-use passwords comprises determining that the service status of the initial phone number indicates that the initial phone number has likely been lost.

8. The computer-implemented method of claim 1 , wherein:

the possession factor comprises a software token that was initially installed on a mobile device;

monitoring the additional attribute comprises monitoring, as part of an application installed on the mobile device, whether the software token is still installed on the mobile device; and

detecting that the user is likely unable to use the possession factor to generate the one-time-use passwords comprises determining that the software token is no longer installed on the mobile device.

9. The computer-implemented method of claim 1 , wherein:

the possession factor comprises a software token that was initially installed on a mobile device;

monitoring the additional attribute comprises monitoring whether the software token is still installed on the mobile device by periodically sending push notifications to the software token; and

detecting that the user is likely unable to use the possession factor to generate the one-time-use passwords comprises determining that the software token is no longer responding to the push notifications.

10. The computer-implemented method of claim 1 , wherein:

monitoring the additional attribute further comprises monitoring a time period since the user last used the possession factor; and

detecting that the user is likely unable to use the possession factor to generate the one-time-use passwords further comprises determining that the time period has exceeded a predetermined threshold.

11. The computer-implemented method of claim 1 , wherein detecting that the user is likely unable to use the possession factor to generate the one-time-use passwords comprises:

using one or more of the additional attributes to predict a loss score for the possession factor; and

determining that the loss score for the possession factor has exceeded a predetermined threshold.

12. The computer-implemented method of claim 1 , wherein performing the security action comprises immediately notifying the user of the user's likely inability to use the possession factor to generate the one-time-use passwords.

13. The computer-implemented method of claim 1 , wherein monitoring the additional attribute comprises monitoring the additional attribute of the possession factor that enables the possession factor to generate the one-time-use passwords.

14. The computer-implemented method of claim 1 , wherein

the additional attribute comprises one of:

a physical address of the user; or

a physical location of the user.

15. A system for preventing loss of possession factors, the system comprising:

an identifying module, stored in memory, that identifies an account of a user that is associated with a username, a password, and a possession factor that generates one-time-use passwords, wherein the username, the password, and a one-time-use password generated by the possession factor are used by the user to perform a multi-factor authentication procedure that is required when accessing the account of the user;

a monitoring module, stored in memory, that monitors an additional attribute of at least one of the user or the possession factor, the additional attribute comprising one of:

an initial phone number that enables the possession factor to receive the one-time-use passwords;

a cellular service that enables the possession factor to receive the one-time-use passwords;

a physical location that enables the possession factor to connect to the cellular service and receive the one-time-use passwords;

a physical address that enables the possession factor to connect to the cellular service and receive the one-time-use passwords; or

an installation status of the possession factor that enables the possession factor to generate the one-time-use passwords;

a determining module, stored in memory, that detects, based at least in part on a change of the additional attribute, that the user is likely unable to use the possession factor to generate the one-time-use passwords;

a security module, stored in memory, that performs, in response to detecting that the user is likely unable to use the possession factor to generate the one-time-use passwords, a security action to prevent the user from being unable to perform the multi-factor authentication procedure; and

at least one physical processor that executes the identifying module, the monitoring module, the determining module, and the security module.

16. The system of claim 15 , wherein:

the account of the user is associated with an additional possession factor;

either one of the possession factor and the additional possession factor can be used by the user to generate the one-time-use passwords; and

the security action prevents the possession factor and the additional possession factor from becoming simultaneously lost.

17. The system of claim 16 , wherein the security module performs the security action by:

notifying the user of the user's likely inability to use the possession factor to generate the one-time-use passwords; and

instructing the user to:

access the account of the user using the additional possession factor; and

register a backup possession factor to replace the possession factor.

18. The system of claim 16 , wherein the possession factor and the additional possession factor comprise at least two of:

a mobile phone;

a hardware token; and

a software token.

19. The system of claim 15 , wherein the determining module detects that the user is likely unable to use the possession factor to generate the one-time-use passwords by:

using the additional attribute to predict a loss score for the possession factor; and

determining that the loss score for the possession factor has exceeded a predetermined threshold.

20. A non-transitory computer-readable medium comprising one or more computer-executable instructions that, when executed by at least one processor of a computing device, cause the computing device to:

identify an account of a user that is associated with a username, a password, and a possession factor that generates one-time-use passwords, wherein the username, the password, and a one-time-use password generated by the possession factor are used by the user to perform a multi-factor authentication procedure that is required when accessing the account of the user;

monitor an additional attribute of at least one of the user or the possession factor, the additional attribute comprising one of

an initial phone number that enables the possession factor to receive the one-time-use passwords;

a cellular service that enables the possession factor to receive the one-time-use passwords;

a physical location that enables the possession factor to connect to the cellular service and receive the one-time-use passwords;

a physical address that enables the possession factor to connect to the cellular service and receive the one-time-use passwords; or

an installation status of the possession factor that enables the possession factor to generate the one-time-use passwords;

determine, based at least in part on a change of the additional attribute, that the user is likely unable to use the possession factor to generate the one-time-use passwords; and

perform, in response to detecting that the user is likely unable to use the possession factor to generate the one-time-use passwords, a security action to prevent the user from being unable to perform the multi-factor authentication procedure.

Assignments (6)
CHANGE OF NAME Recorded Feb 6, 2023
From: NORTONLIFELOCK INC.
To: GEN DIGITAL INC.
Reel/Frame 062714/0605 →
NOTICE OF SUCCESSION OF AGENCY (REEL 050926 / FRAME 0560) Recorded Sep 13, 2022
From: JPMORGAN CHASE BANK, N.A.
To: BANK OF AMERICA, N.A., AS COLLATERAL AGENT
Reel/Frame 061422/0371 →
SECURITY AGREEMENT Recorded Sep 13, 2022
From: NORTONLIFELOCK INC.
To: BANK OF AMERICA, N.A., AS COLLATERAL AGENT
Reel/Frame 062220/0001 →
CHANGE OF NAME Recorded Feb 14, 2020
From: SYMANTEC CORPORATION
To: NORTONLIFELOCK INC.
Reel/Frame 051935/0228 →
SECURITY AGREEMENT Recorded Nov 4, 2019
From: SYMANTEC CORPORATION; BLUE COAT LLC; LIFELOCK, INC,; SYMANTEC OPERATING CORPORATION
To: JPMORGAN, N.A.
Reel/Frame 050926/0560 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 9, 2016
From: JIANG, KEVIN; SOKOLOV, ILYA
To: SYMANTEC CORPORATION
Reel/Frame 040259/0734 →
Cited By (1)
US 12,229,301