Securing a device based on atypical user behavior
First Claim
1. A system for securing a device comprising:
- a. a behavior module for authorizing events, updating rule data, and securing the device; and
b. an authentication module responsive to a first event being a secure event, for determining if the first event is authenticated;
c. responsive to the first event being authenticated, for directing the behavior module to authorize the first event and to update the rule data;
d. responsive to the first event not being authenticated, for determining if an authentication is valid;
e. responsive to the authentication being valid, for directing the behavior module to authorize the first event and update the rule data;
f. responsive to the authentication not being valid, for directing the behavior module to secure the device;
g. a processor;
h. a memory storing the behavior module and the authentication module for execution by the processor;
i. wherein the authentication module is responsive to the first event not being a secure event, for directing the behavior module to authorize the first event and update the rule data, wherein secure events require authentication and non-secure events do not require authentication, andj. wherein the authentication module is responsive to the first event authentication being valid, for directing the behavior module to determine if the first event is a static event, and wherein the behavior module is responsive to the first event not being a static event, for authorizing the first event and updating the rule data, the rule data comprising at least one item from the group of;
which events have been authenticated, a number of times an event occurred, if a user is connected to a docking station, and timer information.
23 Assignments
0 Petitions
Accused Products
Abstract
A system and method for securing the mobile device applies the rules to determine if an event associated with an application is a secure event. If the event is a secure event, the system applies the rules to determine if the event is authenticated. If the event is authenticated, the event is authorized and the system updates rule data associated with the event and/or other associated events. Updating the rule data allows other associated events to be authenticated. If the event is not authenticated, the system requests authentication from a user. If the authentication is valid, the event is authorized and the system updates the rule data associated with the event and/or other associated events. If the authentication is not valid, the system secures the mobile device. Authorizing the event enables a user to access the application and/or data associated with the application.
27 Citations
29 Claims
-
1. A system for securing a device comprising:
-
a. a behavior module for authorizing events, updating rule data, and securing the device; and b. an authentication module responsive to a first event being a secure event, for determining if the first event is authenticated; c. responsive to the first event being authenticated, for directing the behavior module to authorize the first event and to update the rule data; d. responsive to the first event not being authenticated, for determining if an authentication is valid; e. responsive to the authentication being valid, for directing the behavior module to authorize the first event and update the rule data; f. responsive to the authentication not being valid, for directing the behavior module to secure the device; g. a processor; h. a memory storing the behavior module and the authentication module for execution by the processor; i. wherein the authentication module is responsive to the first event not being a secure event, for directing the behavior module to authorize the first event and update the rule data, wherein secure events require authentication and non-secure events do not require authentication, and j. wherein the authentication module is responsive to the first event authentication being valid, for directing the behavior module to determine if the first event is a static event, and wherein the behavior module is responsive to the first event not being a static event, for authorizing the first event and updating the rule data, the rule data comprising at least one item from the group of;
which events have been authenticated, a number of times an event occurred, if a user is connected to a docking station, and timer information. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13)
-
-
14. A method for securing a device comprising:
-
a. determining if a first event is a secure event; b. in response to determining that the first event is a secure event, determining if the first event is authenticated; c. in response to determining that the first event is authenticated, proceeding to step (f); d. in response to determining that the first event is not authenticated, determining if an authentication is valid; e. in response to determining that the authentication is valid proceeding to step (f); f. authorizing the first event and updating rule data for the first event; and g. in response to determining that the authentication is not valid, securing the device, wherein securing the device comprises at least one item selected from the group comprising;
locking the device, encrypting application data, and deleting application data;h. in response to determining that the first event is not a secure event, proceeding to step (f), wherein secure events require authentication and non-secure events do not require authentication, and wherein the rule data comprises at least one item from the group of;
which events have been authenticated, a number of times an event occurred, if a user is connected to a docking station, and timer information;i. determining if the first event is a static event, and responsive to the first event not being a static event, authorizing the first event and updating the rule data. - View Dependent Claims (15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28)
-
-
29. A system for securing a device comprising:
-
a. an authentication module responsive to a first event being a secure event, for determining if the first event is authenticated; b. responsive to the first event not being a secure event, for directing a behavior module to authorize the first event and to update rule data, wherein secure events require authentication and non-secure events do not require authentication, and wherein the rule data comprises at least one item from the group of;
which events have been authenticated, a number of times an event occurred, if a user is connected to a docking station, and timer information;c. responsive to the first event being authenticated, for directing the behavior module to authorize the first event and to update the rule data; d. responsive to the first event not being authenticated, for determining if an authentication is valid; e. responsive to the authentication not being valid, for directing the behavior module to secure the device; f. responsive to the authentication being valid, for directing the behavior module to determine if the first event is a static event; g. responsive to the authentication not being valid, for directing the behavior module to secure the device; h. the behavior module, adapted to authorize an event, update rule data, and secure the device, the behavior module further for determining if an event is a static event, and responsive to the event not being a static event, for authorizing the event and updating the rule data; i. a processor; and j. a memory storing the behavior module and the authentication module for execution by the processor.
-
Specification