The invention is a system and method for identifying, assessing, and responding to vulnerabilities on a mobile communication device. information about the mobile communication device, such as its operating system, firmware version, or software configuration, is transmitted to a server for assessment. The server accesses a data storage storing information about vulnerabilities. Based on the received information, the server may identify those vulnerabilities affecting the mobile communication device, and may transmit a notification to remediate those vulnerabilities. The server may also transmit result information about the vulnerabilities affecting the mobile communication device. The server may also store the received information about the device, so that in the event the server learns of new vulnerabilities, it may continue to assess whether the device is affected, and may accordingly notify or remediate the device. The server may provide an interface for an administrator to manage the system and respond to security issues.
|
0. 60. A method comprising:
a) at a server, determining whether a vulnerability of a mobile communications device exceeds a threshold level based on a prioritized list of vulnerability risks;
b) at a server, determining that the mobile communications device requires remediation when the vulnerability is determined to exceed the threshold level;
c) at the server, transmitting instructions to the mobile communications device to remediate the vulnerability of the mobile communications device determined to exceed the threshold level;
d) at the server, determining whether a remediation confirmation has been received from the mobile communications device in response to the transmitted instructions within a preset time period; and
e) when the server determines that the remediation confirmation has not been received within the preset time period, taking, at the server, an action step to facilitate remediating the determined vulnerability.
0. 66. A method:
a) on a mobile communications device, transmitting vulnerability identification information to a server; and
b) on the mobile communications device, receiving a first subset of a first set of vulnerability result information from the server, wherein the first set of vulnerability result information is generated based on a correlation between the transmitted vulnerability identification information and at least one of a plurality of sets of vulnerability information accessed from a data storage device of the server, the vulnerability information including descriptions of known vulnerabilities, and wherein the first subset of vulnerability result information is selected from the first set of vulnerability result information based on a determined vulnerability risk of each item of the vulnerability result information, and wherein the first subset of vulnerability result information includes instructions for remediating at least one vulnerability of the mobile communications device.
0. 56. A method comprising:
a) receiving at a mobile communications device from a server a first set of vulnerability information about the mobile communications device, the first set of vulnerability information being accessed from a data storage device of the server, the vulnerability information including descriptions of known vulnerabilities, an amount of information included in the first set of vulnerability information being determined by a setting provided to the server by an input from an administrator; and
b) correlating by the mobile communications device the received first set of vulnerability information to a set of vulnerability identification information about the mobile communications device to determine whether the received vulnerability information is relevant to the mobile communications device to generate a first set of vulnerability result information, the first set of vulnerability result information including instructions for remediating at least one vulnerability of the mobile communications device.
10. A method comprising:
a) transmitting, from a mobile communication communications device, a set of vulnerability identification information to at least one server that accesses a data storage storing a plurality of sets of vulnerability information, the vulnerability information including descriptions of known vulnerabilities; and,
b) receiving, at the mobile communication communications device from the at least one server, a subset of a first set of result information that correlates to, wherein the first set of result information is generated by correlating the transmitted set of vulnerability identification information to at least one of the plurality of sets of vulnerability information stored on the data storage, and wherein an amount of the first set of result information included in the subset of result information being determined by a setting provided to the server by an input from an administrator, and wherein the subset of result information includes instructions for remediating at least one vulnerability of the mobile communications device.
0. 28. A method comprising:
a) storing a plurality of sets of vulnerability information on a data storage accessible by at least one server, the vulnerability information including descriptions of known vulnerabilities;
b) receiving, at the at least one server, a set of vulnerability identification information about a mobile communications device;
c) correlating, by the at least one server, the received set of vulnerability identification information to at least one of the plurality of sets of vulnerability information accessed from the data storage to generate a first set of result information; and
d) transmitting, by the at least one server to the mobile communications device, a first subset of the first set of result information, an amount of the first set of result information included in the first subset of result information being determined by a setting provided to the server by an input from an administrator, and the first subset of result information including instructions for remediating at least one vulnerability of the mobile communications device.
1. A method comprising:
a) providing at least one server that accesses a data storage storing a plurality of sets of vulnerability information, the vulnerability information including descriptions of known vulnerabilities;
b) receiving, at the at least one server, a set of vulnerability identification information about a mobile communication communications device;
c) correlating, by the at least one server, the received set of vulnerability identification information to at least one of the plurality of sets of vulnerability information accessed from the data storage to generate a first set of result information; and,
d) transmitting, by the at least one server to the mobile communications device, a first subset of the first set of result information, an amount of the first set of result information included in the first subset of result information being determined by a setting provided to the server by an input from an administrator, and the first subset of result information including instructions for remediating at least one vulnerability of the mobile communications device.
23. A method comprising:
a) providing at least one server that accesses a data storage storing a plurality of sets of vulnerability information, the vulnerability information including descriptions of known vulnerabilities;
b) receiving, at the at least one server, a set of vulnerability identification information about a mobile communication communications device;
c) correlating, by the at least one server, the received set of vulnerability identification information to at least one of the plurality of sets of vulnerability information accessed from the data storage to generate a first set of result information; and,
d) transmitting, by the at least one server to the mobile communication communications device, a first subset of the first set of result information and a notification about the first subset of the first set of result information, wherein an amount of the first set of result information included in the first subset of result information is determined by a setting provided to the server by an input from an administrator, and wherein the first subset of result information includes instructions for remediating at least one vulnerability of the mobile communications device.
0. 40. A method comprising:
a) storing a plurality of sets of vulnerability information on a data storage accessible by at least one server, the vulnerability information including descriptions of known vulnerabilities;
b) receiving, at the at least one server, a set of vulnerability identification information about a mobile communications device;
c) correlating, by the at least one server, the received set of vulnerability identification information to at least one of the plurality of sets of vulnerability information accessed from the data storage to generate a first set of result information;
d) transmitting, by the at least one server to the mobile communications device, a notification about the first set of result information; and
e) transmitting, by the at least one server to the mobile communications device, a first subset of the first set of result information, the first subset of result information being selected from the first set of result information based on a determined vulnerability risk of each item of the result information, and the first subset of result information including instructions for remediating at least one vulnerability of the mobile communications device.
0. 63. A method comprising:
storing, in a data store accessible by a server, vulnerability information based on applications available for installation on mobile communications devices, the vulnerability information including descriptions of known vulnerabilities;
receiving, at the server, first information and second information from a mobile communications device, wherein the first information identifies an application downloaded to the mobile communications device, and the second information identifies an operating system of the mobile communications device;
analyzing, at the server, the stored vulnerability information, and the first and second information;
based on the analysis, making a vulnerability assessment;
transmitting a subset of the vulnerability assessment from the server to the mobile communications device, the subset of the vulnerability assessment being selected from the vulnerability assessment based on a determined vulnerability risk of each item of the vulnerability assessment; and
based on the vulnerability assessment, transmitting from the server to the mobile communications device instructions for remediating at least one vulnerability of the mobile communications device.
0. 49. A method comprising:
a) on a server accessing data storage containing a plurality of sets of vulnerability criteria, the vulnerability criteria including descriptions of known vulnerabilities, receiving a set of vulnerability identification information from a mobile communications device;
b) at the server, correlating the received set of vulnerability identification information to the stored plurality of sets of vulnerability criteria to determine if there is a partial match between the received set and at least one of the plurality of stored sets of vulnerability criteria accessed from the data storage, and to generate a set of result information; and
c) when the server determines there is a partial match between the received set and at least one of the plurality of stored sets of vulnerability criteria, transmitting by the server to the mobile communications device a subset of the set of result information related to the vulnerability criteria, the subset of result information being selected from the set of result information based on a determined vulnerability risk of each item of the result information, and the subset of result information including instructions for remediating at least one vulnerability of the mobile communications device.
20. A system comprising:
a data storage storing a plurality of sets of vulnerability information, the vulnerability information including descriptions of known vulnerabilities;
a server for accessing the data storage, for receiving one or more sets of vulnerability identification information about one or more mobile communication communications devices, for correlating the one or more sets of received vulnerability identification information to at least one of the plurality of sets of vulnerability information accessed from the data storage to generate one or more sets of result information, for transmitting one or more subsets of the one or more sets of result information, and for transmitting one or more notifications about the one or more sets of result information, wherein an amount of the one or more sets of result information included in the one or more subsets of result information is determined by a setting provided to the server by an input from an administrator, and wherein at least one of the one or more subsets of result information includes instructions for remediating at least one vulnerability of the mobile communication device; and,
a network connecting the at least one server, data storage, and the plurality of one or more mobile communication communications devices.
0. 45. A method comprising:
a) storing a plurality of sets of vulnerability information on a data storage accessible by a server, the vulnerability information including descriptions of known vulnerabilities;
b) receiving, at the server a plurality of sets of vulnerability identification information about a plurality of mobile communications devices, each vulnerability identification information set associated with a single mobile communications device;
c) correlating, by the server, the received plurality of vulnerability identification information sets to the stored plurality of vulnerability information accessed from the data storage to generate a plurality of sets of assessment result information;
d) transmitting the plurality of sets of assessment result information for display on a management console; and
e) transmitting, by the server to each of the plurality of mobile communications devices, a subset of a corresponding set of assessment result information, the subset being selected from the corresponding set of assessment result information based on a determined vulnerability risk of each item of the corresponding assessment result information, and the subset including instructions for remediating at least one vulnerability of the plurality of mobile communications devices.
0. 69. A method comprising:
at an administrator server in communication with a plurality of mobile communications devices, receiving a plurality of sets of vulnerability result information, each set associated with one of the plurality of mobile communications devices, wherein the plurality of sets of vulnerability result information is generated based on correlating, for each of the plurality of mobile communications devices, a received set of vulnerability identification information to at least one of a plurality of sets of vulnerability information accessed from a data storage of the administrator server, the vulnerability information including descriptions of known vulnerabilities;
at the administrator server, based upon the received plurality of sets of vulnerability result information, performing actions directed to the mobile communications devices identified in the sets of vulnerability result information as having vulnerabilities; and
at the administrator server, based upon the received plurality of sets of vulnerability result information, transmitting to each of the plurality of mobile communications devices identified in the sets of vulnerability result information as having vulnerabilities, a subset of a corresponding set of vulnerability result information, the subset being selected from the corresponding set of vulnerability result information based on a determined vulnerability risk of each item of the corresponding vulnerability result information, and the subset of the corresponding set of vulnerability result information including instructions for remediating at least one vulnerability of the mobile communications device.
0. 52. A method comprising:
a) storing a plurality of sets of vulnerability information on a data storage accessible by a server, the vulnerability information including descriptions of known vulnerabilities;
b) receiving, at the server, a first set of vulnerability identification information about a mobile communications device;
c) correlating, by the server, the received set of vulnerability identification information to the plurality of sets of vulnerability information accessed from the data storage to generate a first set of result information;
d) transmitting to the mobile communications device, by the server, a first subset of the first set of result information and a request for a second set of vulnerability identification information about the mobile communications device, wherein the first subset of result information is selected from the first set of result information based on a determined vulnerability risk of each item of the result information, and wherein the first subset of result information includes instructions for remediating at least one vulnerability of the mobile communications device;
e) receiving at the server the requested second set of vulnerability identification information;
f) correlating, by the server, the received second set of vulnerability identification information to the plurality of sets of vulnerability information to generate a second set of result information; and
d) transmitting to the mobile communications device, by the server, a second subset of the second set of result information, wherein the second subset of result information is selected from the second set of result information based on the determined vulnerability risk of each item of the result information.
0. 37. A method comprising:
a) storing a plurality of sets of vulnerability information on a data storage accessible by at least one server, the vulnerability information including descriptions of known vulnerabilities;
b) receiving, at the at least one server, a first set of vulnerability identification information about a first mobile communications device;
c) correlating, by the at least one server, the first set of vulnerability identification information to at least one of the plurality of sets of vulnerability information accessed from the data storage to generate a first set of result information;
d) transmitting, by the at least one server to the first mobile communications device, a first subset of the first set of result information, an amount of the first set of result information included in the first subset of result information being limited by a setting specified by an administrator, and the first subset of result information including instructions for remediating at least one vulnerability of the mobile communications device;
e) receiving, at the at least one server, a second set of vulnerability identification information about a second mobile communications device, wherein the second set of vulnerability identification information differs from the first set of vulnerability identification information;
f) correlating, by the at least one server, the second set of vulnerability identification information to at least one of the plurality of sets of vulnerability information to generate a second set of result information; and,
g) transmitting, by the at least one server to the second mobile communications device, a second subset of the second set of result information, an amount of the second set of result information included in the second subset of result information being determined by the setting provided to the server by the input from the administrator.
17. A method comprising:
a) providing at least one server that accesses a data storage storing a plurality of sets of vulnerability information, the vulnerability information including descriptions of known vulnerabilities;
b) receiving, at the at least one server, a first set of vulnerability identification information about a first mobile communication communications device;
c) correlating, by the at least one server, the first set of vulnerability identification information to at least one of the plurality of sets of vulnerability information accessed from the data storage to generate a first set of result information; and,
d) transmitting, by the at least one server to the mobile communications device, a first subset of the first set of result information, an amount of the first set of result information included in the first subset of result information being determined by a setting provided to the server by an input from an administrator, and the first subset of result information including instructions for remediating at least one vulnerability of the mobile communications device;
e) receiving, at the at least one server, a second set of vulnerability identification information about a second mobile communication communications device, wherein the second set of vulnerability identification information differs from the first set of vulnerability identification information;
f) correlating, by the at least one server, the second set of vulnerability identification information to at least one of the plurality of sets of vulnerability information to generate a second set of result information; and,
g) transmitting, by the at least one server to the mobile communications device, a second subset of the second set of result information, an amount of the second set of result information included in the second subset of result information being determined by the setting provided to the server by the input from the administrator.
2. The method of
3. The method of
4. The method of
e) transmitting, by the at least one server to the mobile communication communications device, a notification about the first set of result information.
5. The method of
6. The method of
e) updating at least one of the plurality of sets of vulnerability information on the data storage to form a plurality of updated sets of vulnerability information;
f) after the step of transmitting, by the at least one server, the first set subset of result information, correlating, by the at least one server, the received set of vulnerability identification information to the plurality of updated sets of vulnerability information to generate a second set of result information; and,
g) transmitting, by the at least one server to the mobile communications device, a second subset of the second set of result information, an amount of the second set of result information included in the second subset of result information being determined by the setting provided to the server by the input from the administrator.
7. The method of
e) updating at least one of the plurality of sets of vulnerability information on the data storage to form a plurality of updated sets of vulnerability information;
f) after the step of transmitting, by the at least one server, the first set subset of result information, correlating, by the at least one server, the received set of vulnerability identification information to the plurality of updated sets of vulnerability information to generate a second set of result information; and,
g) transmitting, by the at least one server to the mobile communication communications device, a notification about the second set of result information.
8. The method of
e) receiving, at the data storage, a new set of vulnerability information to form an updated plurality of sets of vulnerability information;
f) after the step of transmitting, by the at least one server, the first set subset of result information, correlating, by the at least one server, the received set of vulnerability identification information to the updated plurality of sets of vulnerability information to generate a second set of result information; and,
g) transmitting, by the at least one server, the second set of result information.
9. The method of
e) receiving, at the data storage, a new set of vulnerability information to form an updated plurality of sets of vulnerability information;
f) after the step of transmitting, by the at least one server, the first set subset of result information, correlating, by the at least one server, the received set of vulnerability identification information to the updated plurality of sets of vulnerability information to generate a second set of result information; and,
g) transmitting, by the at least one server to the mobile communication communications device, a notification about the second set of result information.
11. The method of
12. The method of
13. The method of
c) receiving, at the mobile communication communications device from the at least one server, a notification about the first set of result information.
14. The method of
15. The method of
d) displaying, on the mobile communication communications device, at least a portion of the received notification.
16. The method of
c) receiving, at the mobile communication communications device from the at least one server, a notification about a second set of result information.
18. The method of
19. The method of
21. The system of
22. The system of
24. The method of
25. The method of
26. The method of
e) receiving, at the data storage, a new set of vulnerability information to form an updated plurality of sets of vulnerability information;
f) correlating, by the at least one server, the received set of vulnerability identification information to the updated plurality of sets of vulnerability information to generate a second set of result information; and,
g) transmitting, by the at least one server to the mobile communications device, a second subset of the second set of result information, an amount of the second set of result information included in the second subset of result information being determined by the setting provided to the server by the input from the administrator.
27. The method of
e) receiving, at the data storage, a new set of vulnerability information to form an updated plurality of sets of vulnerability information;
f) correlating, by the at least one server, the received set of vulnerability identification information to the updated plurality of sets of vulnerability information to generate a second set of result information; and,
g) transmitting, by the at least one server to the mobile communication communications device, a notification about the second set of result information.
0. 29. The method of claim 28, wherein the vulnerability identification information is information selected from the group consisting of an operating system type, an operating system version, a firmware version, a device model, carrier information, authentication information, user information, configuration information for the mobile communications device, hardware information, a list of files, a list of software components, a list of libraries, and a list of software applications on the mobile communications device.
0. 30. The method of claim 28, wherein vulnerability information is information selected from the group consisting of a name, a description, a remediation instruction, a severity rating, a security impact summary, and a criterion for being vulnerable.
0. 31. The method of claim 28, further comprising the step of:
e) transmitting, by the at least one server to the mobile communications device, a notification about the first set of result information.
0. 32. The method of claim 31, wherein the notification includes an instruction related to the first set of result information.
0. 33. The method of claim 28, further comprising the steps of:
e) updating at least one of the plurality of sets of vulnerability information on the data storage to form a plurality of updated sets of vulnerability information;
f) after the step of transmitting, by the at least one server, the first subset of result information, correlating, by the at least one server, the received set of vulnerability identification information to the plurality of updated sets of vulnerability information to generate a second set of result information; and,
g) transmitting, by the at least one server to the mobile communications device, a second subset of the second set of result information, an amount of the second set of result information included in the second subset of result information being determined by the setting provided to the server by the input from the administrator.
0. 34. The method of claim 28, further comprising the steps of:
e) updating at least one of the plurality of sets of vulnerability information on the data storage to form a plurality of updated sets of vulnerability information;
f) after the step of transmitting, by the at least one server, the first subset of result information, correlating, by the at least one server, the received set of vulnerability identification information to the plurality of updated sets of vulnerability information to generate a second set of result information; and,
g) transmitting, by the at least one server to the mobile communications device, a notification about the second set of result information.
0. 35. The method of claim 28, further comprising the steps of:
e) receiving, at the data storage, a new set of vulnerability information to form an updated plurality of sets of vulnerability information;
f) after the step of transmitting, by the at least one server, the first subset of result information, correlating, by the at least one server, the received set of vulnerability identification information to the updated plurality of sets of vulnerability information to generate a second set of result information; and,
g) transmitting, by the at least one server, the second set of result information.
0. 36. The method of claim 28, further comprising the steps of:
e) receiving, at the data storage, a new set of vulnerability information to form an updated plurality of sets of vulnerability information;
f) after the step of transmitting, by the at least one server, the first subset of result information, correlating, by the at least one server, the received set of vulnerability identification information to the updated plurality of sets of vulnerability information to generate a second set of result information; and,
g) transmitting, by the at least one server to the mobile communications device, a notification about the second set of result information.
0. 38. The method of claim 37, wherein the vulnerability identification information is information selected from the group consisting of an operating system type, an operating system version, a firmware version, a device model, carrier information, authentication information, user information, configuration information for the mobile communications device, hardware information, a list of files, a list of software components, a list of libraries, and a list of software applications on the mobile communications device.
0. 39. The method of claim 37, wherein vulnerability information is information selected from the group consisting of a name, a description, a remediation instruction, a severity rating, a security impact summary, and a criterion for being vulnerable.
0. 41. The method of claim 40, wherein the vulnerability identification information is information selected from the group consisting of an operating system type, an operating system version, a firmware version, a device model, carrier information, authentication information, user information, configuration information for the mobile communications device, hardware information, a list of files, a list of software components, a list of libraries, and a list of software applications on the mobile communications device.
0. 42. The method of claim 40, wherein vulnerability information is information selected from the group consisting of a name, a description, a remediation instruction, a severity rating, a security impact summary, and a criterion for being vulnerable.
0. 43. The method of claim 40, further comprising the steps of:
f) receiving, at the data storage, a new set of vulnerability information to form an updated plurality of sets of vulnerability information;
g) correlating, by the at least one server, the received set of vulnerability identification information to the updated plurality of sets of vulnerability information to generate a second set of result information; and,
h) transmitting, by the at least one server to the mobile communications device, a second subset of the second set of result information, the second subset of result information being selected from the second set of result information based on a determined vulnerability risk of each item of the result information.
0. 44. The method of claim 40, further comprising the steps of:
f) receiving, at the data storage, a new set of vulnerability information to form an updated plurality of sets of vulnerability information;
g) correlating, by the at least one server, the received set of vulnerability identification information to the updated plurality of sets of vulnerability information to generate a second set of result information; and,
h) transmitting, by the at least one server to the mobile communications device, a notification about the second set of result information.
0. 46. The method of claim 45 further comprising the steps of:
at the server, receiving from an administrator for the plurality of mobile communications devices configuration instructions for the correlating and transmitting steps.
0. 47. The method of claim 46 wherein the configuration instructions are selected from the group consisting of custom triggers for transmission of the plurality of sets of assessment result information to the management console, the time period the server waits before transmitting the plurality of sets of assessment result information, the email address where the plurality of sets of assessment result information should be sent, and the type of service that the server should use to transmit the plurality of sets of assessment result information.
0. 48. The method of claim 45 wherein the set of vulnerability information about the mobile communications device is selected from the group of information consisting of weaknesses in the mobile communications device's operating system, other software or hardware flaws in the mobile communications device, protocol implementation or specification flaws in the mobile communications device, misconfiguration of the mobile communications device, software applications installed or stored on the mobile communications device, services provided through, to or by the mobile communications device, the presence of Bluetooth, infrared or Internet capabilities on the mobile communications device, and weaknesses in the mobile communications device's interaction with, flaws in, or misconfiguration of text messaging, voice mail, and telephony.
0. 50. The method of claim 49 wherein the vulnerability identification information is selected from the group consisting of an operating system type, an operating system version, a firmware version, a device model, carrier information, authentication information, user information, configuration information for the mobile communications device, hardware information, and a list of software applications running on the mobile communications device, and combinations thereof.
0. 51. The method of claim 49 wherein the set of vulnerability information about the mobile communications device is selected from the group of information consisting of weaknesses in the mobile communications device's operating system, other software or hardware flaws in the mobile communications device, protocol implementation or specification flaws in the mobile communications device, misconfiguration of the mobile communications device, software applications installed or stored on the mobile communications device, services provided through, to or by the mobile communications device, the presence of Bluetooth, infrared or Internet capabilities on the mobile communications device, and weaknesses in the mobile communications device's interaction with, flaws in, or misconfiguration of text messaging, voice mail, and telephony.
0. 53. The method of claim 52, further comprising the step of:
e) transmitting by the server to the mobile communications device, a notification about the second set of result information.
0. 54. The method of claim 52, wherein the notification includes an instruction related to the second set of result information.
0. 55. The method of claim 52 wherein the set of vulnerability information about the mobile communications device is selected from the group of information consisting of weaknesses in the mobile communications device's operating system, other software or hardware flaws in the mobile communications device, protocol implementation or specification flaws in the mobile communications device, misconfiguration of the mobile communications device, software applications installed or stored on the mobile communications device, services provided through, to or by the mobile communications device, the presence of Bluetooth, infrared or Internet capabilities on the mobile communications device, and weaknesses in the mobile communications device's interaction with, flaws in, or misconfiguration of text messaging, voice mail, and telephony.
0. 57. The method of claim 56 further comprising the steps of:
transmitting, from the mobile communications device to the server, a set of vulnerability identification information about the mobile communications device; and
at the mobile communications device, receiving from the server a second set of vulnerability result information generated by the server, an amount of information included in second set of vulnerability information being determined by the setting provided to the server by the input from the administrator.
0. 58. The method of claim 56 wherein the first set of vulnerability information received from the server is based upon the mobile communications device operating system.
0. 59. The method of claim 56 wherein the set of vulnerability information about the mobile communications device is selected from the group of information consisting of weaknesses in the mobile communications device's operating system, other software or hardware flaws in the mobile communications device, protocol implementation or specification flaws in the mobile communications device, misconfiguration of the mobile communications device, software applications installed or stored on the mobile communications device, services provided through, to or by the mobile communications device, the presence of Bluetooth, infrared or Internet capabilities on the mobile communications device, and weaknesses in the mobile communications device's interaction with, flaws in, or misconfiguration of text messaging, voice mail, and telephony.
0. 61. The method of claim 60 wherein the action step is selected from the group of actions consisting of notifying an administrator of the mobile communications device about the determined vulnerability, disabling the mobile communications device, disabling the mobile communications device such that an administrator of the mobile communications device must verify that the determined vulnerability has been remediated before the mobile communications device can be used again, and notifying the user of the mobile communications device via email or text that the mobile communications device has been determined vulnerable.
0. 62. The method of claim 60 wherein the set of vulnerability information about the mobile communications device is selected from the group of information consisting of weaknesses in the mobile communications device's operating system, other software or hardware flaws in the mobile communications device, protocol implementation or specification flaws in the mobile communications device, misconfiguration of the mobile communications device, software applications installed or stored on the mobile communications device, services provided through, to or by the mobile communications device, the presence of Bluetooth, infrared or Internet capabilities on the mobile communications device, and weaknesses in the mobile communications device's interaction with, flaws in, or misconfiguration of text messaging, voice mail, and telephony.
0. 64. The method of claim 63 wherein the set of vulnerability information about the mobile communications device is selected from the group of information consisting of weaknesses in the mobile communications device's operating system, other software or hardware flaws in the mobile communications device, protocol implementation or specification flaws in the mobile communications device, misconfiguration of the mobile communications device, software applications installed or stored on the mobile communications device, services provided through, to or by the mobile communications device, the presence of Bluetooth, infrared or Internet capabilities on the mobile communications device, and weaknesses in the mobile communications device's interaction with, flaws in, or misconfiguration of text messaging, voice mail, and telephony.
0. 65. The method of claim 63 wherein the mobile communications device displays the first subset of the vulnerability assessment on the mobile communications device using an icon whose image changes depending upon the content of the first set of vulnerability assessment.
0. 67. The method of claim 66 wherein the first subset of vulnerability result information is used by the mobile communications device to generate a display on the mobile communications device.
0. 68. The method of claim 67 wherein the display generated using the first subset of vulnerability result information on the mobile communications device displays an icon whose image changes depending upon the content of the first subset of vulnerability result information.
0. 70. The method of claim 69 wherein the actions are selected from the group of actions consisting of notifying the user of the mobile communications device about the vulnerability via push notification, text message, or email, disabling the mobile communications device, and disabling the ability of the mobile communications device to access a service.
0. 71. The method of claim 69 wherein the administrator server accesses data storage containing a plurality of sets of vulnerability identification information, each set associated with one of the plurality of mobile communications devices, and wherein the actions performed are based upon a priority of vulnerabilities set according to the plurality of sets of vulnerability identification information.
0. 72. The method of claim 69 wherein the set of vulnerability information about the mobile communications device is selected from the group of information consisting of weaknesses in the mobile communications device's operating system, other software or hardware flaws in the mobile communications device, protocol implementation or specification flaws in the mobile communications device, misconfiguration of the mobile communications device, software applications installed or stored on the mobile communications device, services provided through, to or by the mobile communications device, the presence of Bluetooth, infrared or Internet capabilities on the mobile communications device, and weaknesses in the mobile communications device's interaction with, flaws in, or misconfiguration of text messaging, voice mail, and telephony.
|
|||||||||||||||||||||||||
The invention relates generally to mobile security, and specifically, to assessing the vulnerability of a mobile communication device.
Mobile communication devices or mobile devices, such as cellular telephones, smartphones, wireless-enabled personal data assistants, and the like, are becoming more popular as cellular and wireless network providers are able to expand coverage and increase bandwidth. Mobile devices have evolved beyond providing simple telephone functionality and are now highly complex multifunctional devices with capabilities rivaling those of desktop or laptop computers. In addition to voice communications, many mobile devices are capable of text messaging, e-mail communications, internet access, and the ability to run full-featured application software. Mobile devices can use these capabilities to perform online transactions such as banking, stock trading, payments, and other financial activities. Furthermore, a mobile device used by an individual, a business, or a government agency can often store confidential or private information in forms such as electronic documents, text messages, access codes, passwords, account numbers, e-mail addresses, personal communications, phone numbers, and financial information.
In turn, it is more important to protect those devices against malware, malicious attacks and other exploits. Specifically, it would be helpful to be able to identify vulnerabilities for a mobile communication device, so that the user of the mobile communication device can be alerted if his or her device suffers from any exploitable weaknesses. It is also important for an organization that relies on mobile devices to understand the state of their security and be able to respond to vulnerabilities on mobile devices in an efficient and effective manner.
Presently, current solutions for assessing the vulnerabilities of a computer on a network focus on a conventional desktop, laptop, server, or other computing devices that often enjoy more processing power and memory than a mobile communication device and generally have less restricted application environments than a mobile communication device. As such, these computing devices can often include local monitoring services that can run in the background without overly taxing valuable computing resources. In addition, conventional computing devices are often consistently tethered to a particular local network, such that devices can be remotely scanned over the local network for security weaknesses. Mobile communication devices, on the other hand, are often connected to public networks and switch between networks and network types, making remote, network-based security scans undesirable.
What is therefore needed is a way to provide similar protective services for mobile communication devices in a manner that does not overly tax resources on the mobile communication device, and that extends protective services even when the mobile communication device is not connected to a particular network or is not connected to any network.
There are many differences between mobile communication devices (e.g. operating systems, hardware capabilities, software configurations) that make it difficult to have a single system for accurately assessing the vulnerability of multiple types of devices. Additionally, many mobile communication devices are able to accept installation of various third-party software applications or “apps” that have been developed to extend the capabilities of the device. The installation of apps can alter the vulnerability state of a device, since each app may alter how and with which networks the mobile device communicates. What is therefore needed is a way to assess vulnerabilities of a mobile communication device that accounts for differences such as the operating system, the make, model, configuration, or any installed software on the mobile device. Also needed is a way for a user or administrator to view the security status of, remediate, and otherwise assess and manage the security of multiple different mobile communication devices.
The invention is illustrated by way of example and not limitation in the figures of the accompanying drawings, in which like references indicate similar elements, and in which:
The invention is a system and a method for identifying, assessing, and responding to vulnerabilities on or affecting a mobile communication device. As will be discussed further below, a mobile communication device may transmit certain information to a server, and the server may transmit certain result information to the device that contains an assessment or identifies known or potential vulnerabilities affecting the device. Additionally or alternatively, the server may transmit notifications about possible or actual vulnerabilities affecting a mobile communication device, which may include instructions for remediating any vulnerabilities identified as affecting the mobile communication device. Furthermore, the server may host a management console that allows an administrator to view the security status of multiple mobile communication devices and take action to secure them if necessary.
It should be appreciated that the invention can be implemented in numerous ways, including as a process, an apparatus, a system, a device, a method, a computer readable medium such as a computer readable storage medium containing computer readable instructions or computer program code, or as a computer program product comprising a computer usable medium having a computer readable program code embodied therein. One will appreciate that the mobile communication device described herein may include any computer or computing device running an operating system for use on handheld or mobile devices, such as smartphones, PDAs, mobile phones and the like. For example, a mobile communication device may include devices such as the Apple iPhone®, the Palm Pre™, or any device running the Android™ OS, Symbian OS®, Windows Mobile® OS, Palm OS® or Palm Web OS™.
In the context of this document, a computer usable medium or computer readable medium may be any medium that can contain or store the program for use by or in connection with the instruction execution system, apparatus or device. For example, the computer readable storage medium or computer usable medium may be, but is not limited to, a random access memory (RAM), read-only memory (ROM), or a persistent store, such as a mass storage device, hard drives, CDROM, DVDROM, tape, erasable programmable read-only memory (EPROM or flash memory), or any magnetic, electromagnetic, infrared, optical, or electrical system, apparatus or device for storing information. Alternatively or additionally, the computer readable storage medium or computer usable medium may be any combination of these devices or even paper or another suitable medium upon which the program code is printed, as the program code can be electronically captured, via, for instance, optical scanning of the paper or other medium, then compiled, interpreted, or otherwise processed in a suitable manner, if necessary, and then stored in a computer memory.
Applications, software programs or computer readable instructions may be referred to as components or modules. Applications may be hardwired or hard coded in hardware or take the form of software executing on a general purpose computer such that when the software is loaded into and/or executed by the computer, the computer becomes an apparatus for practicing the invention. Applications may also be downloaded in whole or in part through the use of a software development kit or toolkit that enables the creation and implementation of the invention. In this specification, these implementations, or any other form that the invention may take, may be referred to as techniques. In general, the order of the steps of disclosed processes may be altered within the scope of the invention.
One will appreciate that communication between mobile communication device 101 and server 151 may utilize a variety of networking protocols and security measures. In an embodiment, server 151 operates as an HTTP server and the device 101 operates as an HTTP client. To secure the data in transit, mobile communication device 101 and server 151 may use Transaction Layer Security (“TLS”). Additionally, to ensure that mobile communication device 101 has authority to access server 151, and/or to verify the identity of mobile communication device 101, device 101 may send one or more authentication credentials to server 151. For example, authentication credentials may include a username and password or any other data that identifies mobile communication device 101 to server 151. Authentication may allow server 151 to store specific information, such as vulnerability identification information, about mobile communication device 101, and may also provide a persistent view of the security status of mobile communication device 101.
As previously mentioned, data storage 111 may be used to store sets of information about mobile communication device vulnerabilities (“vulnerability information”), which may be transmitted in whole or in part to one or more mobile communication devices in the form of “result information.” As used herein, a vulnerability may include an exploitable weakness on a mobile communication device that may result from the device hardware or software. Vulnerabilities may arise due to weaknesses in the device's operating system, other software or hardware flaws in the device, protocol implementation or specification flaws, misconfiguration of the device, software applications installed or stored on the device, or services provided through, to or by the device. Vulnerabilities may arise form the features of the device, such as from the presence of Bluetooth, infrared or Internet capabilities on the device, or other communication interfaces and protocols available on the device. Vulnerabilities may arise from weaknesses in the device's interaction with, flaws in, or misconfiguration of other services and systems such as text messaging, voice mail, telephony, or other services and systems accessed through a mobile communication device. Information about a vulnerability, i.e., vulnerability information, may be stored in data storage 111 and accessed by server 151 or mobile communication device 101. Data storage 111 may store general information about mobile communication device vulnerabilities, or may store information about vulnerabilities specific to a mobile communication device. As will be discussed further below, sets of vulnerability information corresponding to vulnerabilities that could affect or actually affect the mobile communication device may be transmitted in the form of result information, notifications, or both.
One will appreciate that as used herein, vulnerability information may include the name, description, severity rating, security impact summary and remediation instructions for a vulnerability. Vulnerability information may be included in the result information server 151 transmits to mobile communication device 101 or may be stored in data storage 111. Result information may include a list of vulnerabilities that are known to affect mobile communication device 101, a list of potential vulnerabilities that may affect mobile communication device 101, and a list of vulnerabilities that are known not to affect mobile communication device 101. Each entry in a list of vulnerabilities may include some or all of the set of vulnerability information for a vulnerability. As will be discussed in more detail below, the result information may also include a binary assessment of mobile communication device 101 (e.g., good or bad, “okay” or “not okay”), a threat score, remediation instructions for known or potential vulnerabilities, or may instruct display of a graduated icon that changes depending upon state (a sad face for a vulnerable mobile communication device, to a happy face for a “safe” mobile communication device). Vulnerability information may include criteria for determining if a mobile communication device 101 is affected. In an embodiment, vulnerability information may include information about a vulnerability such as a title, a description, a security impact summary, human or computer readable remediation instructions or a severity rating for the vulnerability.
As used herein, “vulnerability identification information” or “identification information” includes data that server 151 may use to determine if mobile communication device 101 is susceptible to any vulnerabilities. Such vulnerability identification information may include the operating system and version for mobile communication device 101; the firmware version of the mobile communication device 101, the device model for mobile communication device 101; carrier information for mobile communication device 101; authentication information; and/or user information for the user of mobile communication device 101. Vulnerability identification information may also include a list of files, software components, libraries and/or a list of the applications or other software installed on mobile communication device 101, as well as other information related to these applications and software such as version and configuration information, configuration information about the mobile communication device 101, communications interfaces and protocols in use by mobile communication device 101 (e.g., WiFi, Bluetooth, IR, SMS, MMS), cellular network information, cellular carrier information, the make and model of mobile communication device 101, and the like.
In an embodiment, vulnerability information stored in data storage 111 may have associated information that includes a description, a title, an overview of the security impact, remediation instructions, and criteria for affected firmware versions. In an embodiment, mobile communication device 101 sends vulnerability identification information to server 151 that includes the device's firmware version. Server 151 may utilize data storage 111 to examine the vulnerability information stored therein and determine if the firmware version for mobile communication device 101 matches the firmware version criteria for any vulnerabilities. If any vulnerabilities match, server 151 may determine that mobile communication device 101 is vulnerable. Server 151 may then transmit result information to the mobile communication device 101, as described herein and shown in the Figures. In an embodiment, server 151 only transmits result information corresponding to vulnerabilities that affect mobile communication device 101. In an embodiment, server 151 transmits result information for all vulnerabilities that may affect device 101. In an embodiment, server 151 transmits result information which contains all vulnerabilities that may affect device 101 and which of those vulnerabilities actually do affect device 101. In an embodiment, the firmware version criteria for being affected by a vulnerability includes the version of the firmware in which the vulnerability was fixed. One will appreciate that some vulnerabilities may only affect certain firmware versions, and that once firmware has been updated to a new version, some vulnerabilities which affected previous versions may no longer be of issue. In order to account for variations in firmware, server 151 may detect and transmit information for vulnerabilities regardless of the firmware version on mobile communication device 101, thereby adding extra precautions. Alternatively, server 151 may only send result information for those vulnerabilities that affect the version of firmware installed on mobile communication device 101, thereby being more specific.
For example, a certain vulnerability may affect a mobile communication device having firmware version 1.0, but not a mobile communication device with firmware version 2.0. Server 151 may receive information about the firmware version of mobile communication device 101, and if the firmware version is earlier than version 2.0, then mobile communication device 101 is determined to be susceptible to the certain vulnerability. However, if the firmware version for mobile communication device 101 is 2.0 or higher, then mobile communication device 101 may not be susceptible to the certain vulnerability. One will appreciate that other variations are possible, and that the determination of whether to send more or less result information may be a setting specified by an administrator, or may involve the application of logic depending upon the severity of the vulnerability and the risks or benefits of transmitting an overabundance of result information to mobile communication device 101. One will also appreciate that the amount of result information to transmit to mobile communication device 101 may also depend upon the capabilities of mobile communication device 101 or the bandwidth of the network.
In an embodiment, data storage 111 stores vulnerability information for at least two types of mobile devices 101. The two mobile device types may have different operating systems, firmware versions, model numbers, carrier information, authentication information, user information, configuration information, states, software applications, and the like. As a result, the vulnerability identification information for each of the at least two mobile devices will differ in some aspect. As such, in an embodiment, data storage 111 may store vulnerability information for vulnerabilities that may affect both of the two device types, including vulnerabilities that may affect one device type but not the other. One will appreciate that data storage 111 may store vulnerability information for a variety of mobile communication devices, and will be able to provide information that will help identify, assess and remediate vulnerabilities for a variety of mobile communication devices.
When data storage 111 stores information about vulnerabilities that may affect multiple types of mobile communication devices, it is important that the transmitted result information not include information regarding vulnerabilities that a user may perceive as irrelevant to a particular device. As such it is important that the list of vulnerabilities that may affect a device not simply include all vulnerabilities stored by data storage 111. In an embodiment, a vulnerability may affect a device if the device's vulnerability identification information at least partially matches the vulnerability's criteria for affecting a device. Providing partially matching result information provides a conservative, or safer approach to detecting and identifying potential vulnerabilities, as it may provide a opportunity for further assessment and action (e.g. further analysis conducted by software on a device), rather than only providing full criteria matches.
In an embodiment, the partial match includes criteria related to a device that does not change, is unlikely to change, or is irrespective of particular software versions, firmware versions, updates, and configuration. Such criteria may include the device's operating system, model, carrier, software applications installed, hardware capabilities, and the like. For example, data storage 111 may store information about a vulnerability that affects a particular range of firmware versions of the Apple iPhone® OS. This vulnerability information may include criteria that it affects the Apple iPhone® OS and criteria that it affects specific firmware ranges of various device models. In an embodiment, the server 151 determines that the vulnerability does affect all devices running Apple iPhone® OS that match the vulnerability information's firmware version criteria, the vulnerability may affect devices running any firmware version containing Apple iPhone® OS, and the vulnerability may not affect any devices running Android™, Windows Mobile®, Symbian OS®, or other operating systems. One will appreciate that other methods of determining what vulnerabilities stored by data storage 111 may affect a device may be performed without departing from the scope of this disclosure.
In an embodiment, the scope or type of result information transmitted by server 151 may be general information, or may be specific information about vulnerabilities that may specifically affect mobile communication device 101. As such, the result information transmitted to device 101 may include all of the vulnerability information stored in data storage 111, or may include a subset of all of the vulnerability information stored in data storage 111. The option to transmit general or specific result information may be an option set by an administrator, may depend upon the hardware or software constraints of the mobile communication device, or may depend upon the bandwidth of the network connecting server 151 to mobile communication device 101.
In an embodiment, determining which vulnerabilities specifically affect mobile communication device 101 may involve correlating the vulnerability identification information provided by mobile communication device 101 to the vulnerability information available to server 151. As used herein, “correlating” vulnerability identification information to vulnerability information may involve determining whether the vulnerability described by the vulnerability information affects a device, whether it may affect a device, or whether it does not affect a device. Determinations may be made through a variety of methods, including matching vulnerability identification information with vulnerability information and determining whether identification information satisfies one or more criteria for vulnerability. Correlating may be performed by server 151 and/or data storage 111, and may include applying logic, comparing operating systems, comparing version identifiers, checking for the presence of specific software or other data on the mobile communication device, and the like. In an embodiment, correlating may utilize an identification of the hardware or specifications of the mobile communication device. In an embodiment, correlating may also be performed by mobile device 101.
In block 302 of
Server 151 may transmit a notification to mobile communication device 101 via a variety of mechanisms. A notification may be sent via email, text messaging, or through a client-server communication system as described in U.S. patent application Ser. No. 12/372,719, entitled, “SYSTEM AND METHOD FOR REMOTELY SECURING OR RECOVERING A MOBILE DEVICE,” and incorporated in full herein. A notification may provide information about a vulnerability, information about a potential vulnerability, the status of a mobile communication device, information about remediation instructions, or may request that the user of an affected mobile communication device perform some action to update the vulnerability information on the mobile communication device, or perform some action to remediate the mobile communication device.
In an embodiment, a notification may contain information or an instruction indicating that the mobile communication device 101 needs to connect to server 151 in order to receive new vulnerability information. The notification may be directed to software resident on the mobile communication device 101, may include software readable remediation instructions, and may be in the form of an SMS or may be sent via a push notification service, such as that provided by Apple Computer Inc. to its iPhone® devices. For example, mobile communication device 101 may receive a notification with instructions that the device should be updated to protect against a new security risk. A specific application on the device may require an update, in which case the notification may also cause mobile communication device 101 to update the specific application without user intervention. In an embodiment, a notification may be directed to the user of the mobile communication device. This may include a text message, push notification, or e-mail message containing human-readable information, or a voicemail or other verbal communication directed to the user of mobile communication device 101. Notifying a mobile communication device 101 allows for rapid response to new vulnerabilities, thereby greatly increasing the effectiveness of systems that would otherwise rely on a scheduled or manually-initiated check for security vulnerabilities.
In block 401 of
One will appreciate that the process illustrated in
One will appreciate that the process illustrated in
In block 901 of
If the time limit for receiving a remediation confirmation has been exceeded, then in block 904, an action may be taken. For example, server 151 may notify an administrator about the vulnerable mobile communication device and that the user has not taken action in the specified period of time. In this example, an administrator may take manual action such as sending a personal email or otherwise notifying the user to secure the device 101. In an embodiment, server 151 may automatically disable mobile communication device 101 in some fashion to prevent affecting other devices on the network 121 or to prevent further damage. For example, server 151 may prevent mobile communication device 101 from connecting to a specific network, email system, document repository, or other system. Alternatively, server 151 may disable mobile communication device 101 such that an administrator must verify that the device is safe before it is can be used again. Some mechanisms by which the disablement can take place are disclosed in U.S. patent application Ser. No. 12/372,719, entitled, “SYSTEM AND METHOD FOR REMOTELY SECURING OR RECOVERING A MOBILE DEVICE,” and U.S. patent application Ser. No. 12/255,632, entitled, “SECURE MOBILE PLATFORM SYSTEM,” both of which are incorporated in full herein. In an embodiment, the user of mobile communication device 101 may be notified by server 151 via email, text message or other means of communication that the mobile communication device is vulnerable and that corrective action was not taken within the prescribed time. The notification may serve as a reminder to help the user take action and secure the device. In this fashion, the invention goes beyond simply updating a mobile communication device to ensure security, or periodically scanning mobile communication devices on the network for potential vulnerabilities. As described herein, the invention may provide a customized vulnerability assessment based upon the unique state and configuration of each mobile communication device on the network, and may provide notifications and remediation instructions based upon this unique state and configuration.
One will appreciate that other actions may be performed in order to optimally secure a mobile device once it is known to be vulnerable. The embodiments described herein may be combined as part of a security response process. In an example, a user may receive a direct reminder after one day if his or her device is determined to be vulnerable and is not yet remediated. After two additional days, if the device is still vulnerable, an administrator may be notified and the device disallowed access to email and the organization's VPN service. Once the device is remediated, the administrator may be notified and access to email and VPN may be automatically restored. Other examples are also possible without departing from this disclosure or the scope of the invention.
If in block 903 of
In block 201 of
In an embodiment, the data transmitted by server 151 in block 1002 of
In an embodiment, the data transmitted by server 151 in block 1002 of
In an embodiment, server 151 may transmit reports based on security status information available at the server. The reports may show changes in security status over time or show a current summary. Some example reports include the number of vulnerable of devices with respect to time, the current number of vulnerable devices with each severity level, the current number of vulnerable devices broken down by operating system type, and a list of contact information for users with the most severely vulnerable devices.
In an embodiment, server 151 may transmit security related events that are generated both by clients and by server 151 due to automatic or administrative action. The events may be displayed, gathered, processed, or otherwise interacted with as disclosed in U.S. patent application Ser. No. 12/255,635, entitled, “SECURITY STATUS AND INFORMATION DISPLAY SYSTEM,” which is incorporated in full herein.
In an embodiment, server 151 allows an administrator to perform actions related to a device or group of devices. Actions that may be performed include notifying the user of the device via a push notification, text message, email, or another messaging system; disabling the device; disabling the device's access to a service, potentially using a mechanism disclosed in U.S. patent application Ser. No. 12/255,632, entitled, “SECURE MOBILE PLATFORM SYSTEM”; or those disclosed in U.S. patent application Ser. No. 12/372,719, entitled, “SYSTEM AND METHOD FOR REMOTELY SECURING OR RECOVERING A MOBILE DEVICE,” both of which are incorporated in full herein.
In an embodiment, server 151 allows an administrator to configure how the server operates. One such configuration may include custom triggers or alerts on certain events (e.g. devices not remediating in a period of time) that will result in logging and administrator notification via email, text message, or other messaging medium. Other examples of configuration options include: the time period the server waits before notifying an administrator of an un-remediated vulnerable device, the email address or addresses administrators should be notified at, how often to remind users of vulnerable devices that they need to take remediation actions, what method of contact server 151 should use to remind users (e.g. SMS, E-mail, push notification service), how the server interacts with e-mail or VPN services to disable access for a specific vulnerable device, and other ways of controlling the functionality disclosed herein.
In an embodiment, vulnerability identification information is stored by server 151 so that, in the case of a new vulnerability, server 151 can determine whether the device is vulnerable, not vulnerable, or potentially vulnerable based on the information is has. In an embodiment, the server stores vulnerability identification information on data storage 111. This allows an IT admin to get an instant picture of the security risk of their device deployment in the case of a new emerging vulnerability. Such rapid understanding is critical to prioritize response effort in the case of a rapidly spreading worm or severe vulnerability.
In the description above and throughout, numerous specific details are set forth in order to provide a thorough understanding of the invention. It will be evident, however, to one of ordinary skill in the art, that the invention may be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form to facilitate explanation. The description of the preferred embodiments is not intended to limit the scope of the claims appended hereto. Further, in the methods disclosed herein, various steps are disclosed illustrating some of the functions of the invention. One will appreciate that these steps are merely exemplary and are not meant to be limiting in any way. Other steps and functions may be contemplated without departing from this disclosure or the scope of the invention.
Mahaffey, Kevin, Hering, John G., Burgess, James
| Patent | Priority | Assignee | Title |
| 11461471, | May 25 2018 | AT&T Intellectual Property I, L.P. | Virtual reality for security augmentation in home and office environments |
| 11841940, | Jul 16 2021 | Dell Products L.P. | Preemptive protection against malicious array access |
| ER4170, |
| Patent | Priority | Assignee | Title |
| 3416032, | |||
| 4553257, | Apr 28 1982 | Pioneer Electronic Corp. | Automatic sound volume control device |
| 5319776, | Apr 19 1990 | Symantec Corporation | In transit detection of computer virus with safeguard |
| 5574775, | Aug 04 1993 | THE CHASE MANHATTAN BANK, AS COLLATERAL AGENT | Universal wireless radiotelephone system |
| 6185689, | Jun 24 1998 | RICHARD S CARSON & ASSOC , INC | Method for network self security assessment |
| 6269456, | Dec 31 1997 | JPMORGAN CHASE BANK, N A ; MORGAN STANLEY SENIOR FUNDING, INC | Method and system for providing automated updating and upgrading of antivirus applications using a computer network |
| 6272353, | Aug 20 1999 | NOKIA SOLUTIONS AND NETWORKS US LLC | Method and system for mobile communications |
| 6301668, | Dec 29 1998 | Cisco Technology, Inc | Method and system for adaptive network security using network vulnerability assessment |
| 6453345, | Nov 06 1996 | COMERICA BANK AS AGENT | Network security and surveillance system |
| 6529143, | Oct 23 1998 | Nokia Technologies Oy | Information retrieval system |
| 6792543, | Aug 01 2001 | McAfee, Inc | Virus scanning on thin client devices using programmable assembly language |
| 6907530, | Jan 19 2001 | SSL SERVICES LLC | Secure internet applications with mobile code |
| 6959184, | Jun 30 1999 | Lucent Technologies Inc.; Lucent Technologies Inc | Method for determining the security status of transmissions in a telecommunications network |
| 7020895, | Dec 24 1999 | WITHSECURE CORPORATION A K A WITHSECURE OYJ | Remote computer virus scanning |
| 7023383, | Jan 08 1999 | SKYHOOK HOLDING, INC | Multiple pass location processor |
| 7069589, | Jul 14 2000 | Computer Associates Think, Inc | Detection of a class of viral code |
| 7096368, | Aug 01 2001 | JPMORGAN CHASE BANK, N A ; MORGAN STANLEY SENIOR FUNDING, INC | Platform abstraction layer for a wireless malware scanning engine |
| 7123933, | May 31 2001 | Cisco Technology, Inc | System and method for remote application management of a wireless device |
| 7127455, | Nov 12 2002 | HEWLETT-PACKARD DEVELOPMENT COMPANY, L P | Taxonomy for mobile e-services |
| 7143441, | May 08 2001 | Aramira Corporation | Wireless device mobile application security system |
| 7171690, | Aug 01 2001 | JPMORGAN CHASE BANK, N A , AS ADMINISTRATIVE AGENT | Wireless malware scanning back-end system and method |
| 7178166, | Sep 19 2000 | KYNDRYL, INC | Vulnerability assessment and authentication of a computer by a local scanner |
| 7210168, | Oct 15 2001 | JPMORGAN CHASE BANK, N A , AS ADMINISTRATIVE AGENT | Updating malware definition data for mobile data processing devices |
| 7228566, | Jul 10 2001 | FORTRA, LLC | Automated computer system security compromise |
| 7236598, | May 23 2001 | INVICTA Networks, Inc.; Invicta Networks, Inc | Systems and methods for communication protection |
| 7237264, | Jun 04 2001 | KYNDRYL, INC | System and method for preventing network misuse |
| 7266810, | Apr 09 2002 | SNOWFLAKE INC | Runtime profiling of platform-independent software applications |
| 7290276, | Feb 06 2003 | Lenovo PC International | Information processing apparatus for secure information recovery |
| 7305245, | Oct 29 2004 | SKYHOOK WIRELESS, INC | Location-based services that choose location algorithms based on number of detected access points within range of user device |
| 7308256, | Feb 28 2002 | NTT DOCOMO INC | Mobile communication terminal, information processing apparatus, relay server apparatus, information processing system, and information processing method |
| 7308712, | Dec 31 2001 | MCAFEE, INC , A DELAWARE CORPORATION | Automated computer vulnerability resolution system |
| 7325249, | Apr 30 2001 | GOOGLE LLC | Identifying unwanted electronic messages |
| 7356835, | Aug 26 2003 | Mitel Networks Corporation | Security monitor for PDA attached telephone |
| 7376969, | Dec 02 2002 | MICRO FOCUS LLC | Real time monitoring and analysis of events from multiple network security devices |
| 7386297, | Dec 28 2002 | PANTECH CORPORATION | Mobile communication system and mobile terminal having function of inactivating mobile communication viruses, and method thereof |
| 7392043, | Apr 17 2003 | McAfee, Inc | API system, method and computer program product for accessing content/security analysis functionality in a mobile communication framework |
| 7392543, | Jun 30 2003 | CA, INC | Signature extraction system and method |
| 7397424, | Feb 03 2005 | SKYHOOK HOLDING, INC | System and method for enabling continuous geographic location estimation for wireless computing devices |
| 7397434, | Sep 16 2005 | Samsung Electro-Mechanics Co., Ltd. | Built-in antenna module of wireless communication terminal |
| 7401359, | Dec 21 2001 | McAfee, Inc | Generating malware definition data for mobile computing devices |
| 7403762, | Oct 29 2004 | SKYHOOK WIRELESS, INC | Method and system for building a location beacon database |
| 7414988, | Oct 29 2004 | SKYHOOK WIRELESS, INC | Server for updating location beacon database |
| 7415270, | Feb 15 2002 | TELEFONAKTIEBOLAGET L M ERICSSON PUBL | Middleware services layer for platform system for mobile terminals |
| 7433694, | Oct 29 2004 | SKYHOOK WIRELESS, INC | Location beacon database |
| 7467206, | Dec 23 2002 | Microsoft Technology Licensing, LLC | Reputation system for web services |
| 7471954, | Feb 24 2006 | SKYHOOK WIRELESS, INC | Methods and systems for estimating a user position in a WLAN positioning system based on user assigned access point locations |
| 7472422, | Sep 10 2003 | Symantec Corporation | Security management system including feedback and control |
| 7474897, | Feb 22 2005 | SKYHOOK WIRELESS, INC | Continuous data optimization by filtering and positioning systems |
| 7493127, | Feb 22 2005 | SKYHOOK WIRELESS, INC | Continuous data optimization of new access points in positioning systems |
| 7502620, | Mar 04 2005 | SKYHOOK WIRELESS, INC | Encoding and compression of a location beacon database |
| 7515578, | May 08 2006 | SKYHOOK WIRELESS, INC | Estimation of position using WLAN access point radio propagation characteristics in a WLAN positioning system |
| 7525541, | Apr 05 2004 | Gula Consulting Limited Liability Company | Data processing for three-dimensional displays |
| 7551579, | May 08 2006 | SKYHOOK WIRELESS, INC | Calculation of quality of wlan access point characterization for use in a wlan positioning system |
| 7551929, | May 08 2006 | SKYHOOK WIRELESS, INC | Estimation of speed and direction of travel in a WLAN positioning system using multiple position estimations |
| 7634800, | Jun 30 2000 | International Business Machines Corporation | Method and apparatus for network assessment and authentication |
| 7685132, | Mar 15 2006 | Beats Music, LLC | Automatic meta-data sharing of existing media through social networking |
| 7696923, | Feb 03 2005 | SKYHOOK HOLDING, INC | System and method for determining geographic location of wireless computing devices |
| 7768963, | Jul 07 2006 | SKYHOOK WIRELESS, INC | System and method of improving sampling of WLAN packet information to improve estimates of Doppler frequency of a WLAN positioning device |
| 7769396, | Oct 29 2004 | SKYHOOK WIRELESS, INC ; SKHYOOK WIRELESS, INC | Location-based services that choose location algorithms based on number of detected access points within range of user device |
| 7774637, | Sep 05 2007 | Spirent Communications, Inc | Meta-instrumentation for security analysis |
| 7809353, | May 18 2006 | BlackBerry Limited | Automatic security action invocation for mobile communications device |
| 7818017, | Oct 29 2004 | Skyhook Wireless, Inc. | Location-based services that choose location algorithms based on number of detected wireless signal stations within range of user device |
| 7835754, | May 08 2006 | SKYHOOK WIRELESS, INC | Estimation of speed and direction of travel in a WLAN positioning system |
| 7856234, | Nov 07 2006 | SKYHOOK WIRELESS, INC | System and method for estimating positioning error within a WLAN-based positioning system |
| 7856373, | Sep 14 2006 | OMNITRAIL HOLDINGS INC; OMNITRAIL TECHNOLOGIES INC | Targeting content to network-enabled devices based upon stored profiles |
| 7861303, | Aug 01 2001 | JPMORGAN CHASE BANK, N A , AS ADMINISTRATIVE AGENT | Malware scanning wireless service agent system and method |
| 7907966, | Jul 19 2005 | Meta Platforms, Inc | System and method for cross-platform applications on a wireless phone |
| 7916661, | May 08 2006 | Skyhook Wireless, Inc. | Estimation of position using WLAN access point radio propagation characteristics in a WLAN positioning system |
| 7999742, | Jun 06 2008 | SKYHOOK WIRELESS, INC | System and method for using a satellite positioning system to filter WLAN access points in a hybrid positioning system |
| 8014788, | May 08 2006 | SKYHOOK WIRELESS, INC | Estimation of speed of travel using the dynamic signal strength variation of multiple WLAN access points |
| 8019357, | Nov 07 2006 | Skyhook Wireless, Inc. | System and method for estimating positioning error within a WLAN-based positioning system |
| 8031657, | Oct 29 2004 | Skyhook Wireless, Inc. | Server for updating location beacon database |
| 8054219, | Jun 06 2008 | SKYHOOK WIRELESS, INC | Systems and methods for determining position using a WLAN-PS estimated position as an initial position in a hybrid positioning system |
| 8089398, | Jun 06 2008 | SKYHOOK WIRELESS, INC | Methods and systems for stationary user detection in a hybrid positioning system |
| 8089399, | Jun 06 2008 | SKYHOOK WIRELESS, INC | System and method for refining a WLAN-PS estimated location using satellite measurements in a hybrid positioning system |
| 8090386, | May 08 2006 | SKYHOOK WIRELESS, INC | Estimation of speed and direction of travel in a WLAN positioning system |
| 8126456, | Jan 17 2007 | eAgency, Inc. | Mobile communication device monitoring systems and methods |
| 8127358, | May 30 2007 | TREND MICRO INCORPORATED | Thin client for computer security applications |
| 20010044339, | |||
| 20020042886, | |||
| 20020087483, | |||
| 20020108058, | |||
| 20020183060, | |||
| 20020191018, | |||
| 20030028803, | |||
| 20030046134, | |||
| 20030079145, | |||
| 20030115485, | |||
| 20030120951, | |||
| 20030131148, | |||
| 20040022258, | |||
| 20040025042, | |||
| 20040133624, | |||
| 20040158741, | |||
| 20040185900, | |||
| 20040225887, | |||
| 20040259532, | |||
| 20050010821, | |||
| 20050015443, | |||
| 20050074106, | |||
| 20050076246, | |||
| 20050091308, | |||
| 20050125779, | |||
| 20050130627, | |||
| 20050138395, | |||
| 20050138413, | |||
| 20050154796, | |||
| 20050197099, | |||
| 20050227669, | |||
| 20050237970, | |||
| 20050254654, | |||
| 20050278777, | |||
| 20050282533, | |||
| 20060026283, | |||
| 20060073820, | |||
| 20060075388, | |||
| 20060080680, | |||
| 20060095454, | |||
| 20060101518, | |||
| 20060130145, | |||
| 20060150238, | |||
| 20060150256, | |||
| 20060179485, | |||
| 20060218482, | |||
| 20060224742, | |||
| 20060253205, | |||
| 20060253584, | |||
| 20060272011, | |||
| 20060277408, | |||
| 20060294582, | |||
| 20070005327, | |||
| 20070011319, | |||
| 20070015519, | |||
| 20070016953, | |||
| 20070016955, | |||
| 20070028095, | |||
| 20070028303, | |||
| 20070028304, | |||
| 20070050471, | |||
| 20070086476, | |||
| 20070088948, | |||
| 20070154014, | |||
| 20070174472, | |||
| 20070186282, | |||
| 20070214504, | |||
| 20070220608, | |||
| 20070240218, | |||
| 20070240221, | |||
| 20070240222, | |||
| 20070248047, | |||
| 20070250627, | |||
| 20070293263, | |||
| 20070297610, | |||
| 20080028470, | |||
| 20080046557, | |||
| 20080047007, | |||
| 20080065507, | |||
| 20080070495, | |||
| 20080072329, | |||
| 20080086773, | |||
| 20080086776, | |||
| 20080109871, | |||
| 20080127171, | |||
| 20080127179, | |||
| 20080127334, | |||
| 20080127336, | |||
| 20080132218, | |||
| 20080134281, | |||
| 20080140767, | |||
| 20080148381, | |||
| 20080172746, | |||
| 20080178294, | |||
| 20080181116, | |||
| 20080196104, | |||
| 20080200160, | |||
| 20080208950, | |||
| 20080209557, | |||
| 20080235801, | |||
| 20080276111, | |||
| 20080293396, | |||
| 20080318562, | |||
| 20090199298, | |||
| 20090205047, | |||
| 20090248623, | |||
| 20090293125, | |||
| 20100064341, | |||
| 20100100939, | |||
| 20100100963, | |||
| 20100154032, | |||
| 20100313270, | |||
| 20100332593, | |||
| 20120137369, | |||
| GB2430588, | |||
| WO2006110181, | |||
| WO2007081356, | |||
| WO2008007111, | |||
| WO2008057737, | |||
| WO2005101789, |
| Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
| Dec 17 2013 | LOOKOUT, INC. | (assignment on the face of the patent) | / | |||
| Oct 26 2018 | LOOKOUT, INC | Silicon Valley Bank | SECURITY INTEREST SEE DOCUMENT FOR DETAILS | 048208 | /0947 | |
| Jun 06 2019 | LOOKOUT, INC | OBSIDIAN AGENCY SERVICES, INC | SECURITY INTEREST SEE DOCUMENT FOR DETAILS | 049408 | /0861 | |
| Nov 19 2020 | OBSIDIAN AGENCY SERVICES, INC | LOOKOUT INC | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 054716 | /0923 | |
| May 06 2022 | LOOKOUT, INC | ALTER DOMUS US LLC | SECURITY INTEREST SEE DOCUMENT FOR DETAILS | 059909 | /0764 | |
| May 06 2022 | SILICON VALLEY BANK THE BANK | LOOKOUT, INC | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 059909 | /0668 | |
| Jun 02 2023 | ALTER DOMUS US LLC, AS ADMINISTRATIVE AGENT | LOOKOUT, INC | RELEASE OF PATENT SECURITY INTEREST AT REEL 59909 AND FRAME 0764 | 063844 | /0638 | |
| Jun 12 2024 | LOOKOUT, INC | MIDCAP FINANCIAL TRUST | SECURITY INTEREST SEE DOCUMENT FOR DETAILS | 068538 | /0177 |
| Date | Maintenance Fee Events |
| Sep 04 2020 | M2552: Payment of Maintenance Fee, 8th Yr, Small Entity. |
| Sep 04 2020 | M2552: Payment of Maintenance Fee, 8th Yr, Small Entity. |
| Jun 15 2021 | BIG: Entity status set to Undiscounted (note the period is included in the code). |
| Jun 15 2021 | BIG: Entity status set to Undiscounted (note the period is included in the code). |
| Mar 04 2024 | SMAL: Entity status set to Small. |
| Sep 03 2024 | M2553: Payment of Maintenance Fee, 12th Yr, Small Entity. |
| Date | Maintenance Schedule |
| Mar 27 2021 | 4 years fee payment window open |
| Sep 27 2021 | 6 months grace period start (w surcharge) |
| Mar 27 2022 | patent expiry (for year 4) |
| Mar 27 2024 | 2 years to revive unintentionally abandoned end. (for year 4) |
| Mar 27 2025 | 8 years fee payment window open |
| Sep 27 2025 | 6 months grace period start (w surcharge) |
| Mar 27 2026 | patent expiry (for year 8) |
| Mar 27 2028 | 2 years to revive unintentionally abandoned end. (for year 8) |
| Mar 27 2029 | 12 years fee payment window open |
| Sep 27 2029 | 6 months grace period start (w surcharge) |
| Mar 27 2030 | patent expiry (for year 12) |
| Mar 27 2032 | 2 years to revive unintentionally abandoned end. (for year 12) |