US 9,642,008 B2Grant

System and method for creating and assigning a policy for a mobile communications device based on personal data

Issue Date:2017-05-02

•20 Claims

•11 Drawing Sheets

Abstract

A system and method to create and assign a policy for a mobile communications device are disclosed. The policy may be created based on personal data associated with the mobile communications device. For example, known sources of personal data on the mobile communications device may be identified and a policy may be created based on the known personal data. The policy may then be used to identify additional personal data associated with the mobile communications device. Thus, the personal data associated with the mobile communications device may be monitored. If an application attempts to access the monitored personal data, the access will be detected.

Metadata

Assignee

LOOKOUT, INC.

Inventors

Timothy Micheal Wyatt
Kevin Patrick Mahaffey
David Luke Richardson
Brian James Buck
Marc William Rogers

Application Information

Application Number:US 14/063,342

Filing Date:2013-10-25

Priority Date:2013-10-25

Art Unit:2646

Classifications

IPC:

H04W12/08H04L29/06H04W88/02

Field of Search:

H04W 12/00H04W 12/02H04W 12/08

Patent Drawings (11 sheets)

Description

Field

[0001] The present disclosure relates to policies. In some embodiments, the disclosure relates to creating and assigning a policy for a mobile communications device based on personal data.

Background

[0002] Conventional data security systems and methods may be designed to prevent the leakage (e.g., unauthorized access or transmission) of data. Such conventional systems and methods typically generate and implement security measures for a business or enterprise environment. A corporation may wish to restrict access to sensitive material stored on a corporate computer or server. For example, the corporation may wish to restrict access to private corporate information, intellectual property, financial documents, and customer information. A security measure may be created and implemented in order to restrict access to this type of sensitive information.

[0003] Examples of such security measures include implementing a firewall, intrusion detection systems, antivirus software, or other such systems to prevent unauthorized access to sensitive data. Other types of conventional security measures include the utilization of machine learning algorithms to identify abnormal access of sensitive data, monitoring of computer system behavior, and mechanisms to detect unauthorized attempts to copy sensitive information.

[0004] However, such conventional data security systems and methods are not suitable for use with a mobile communications device. For example, the type of data associated with the mobile communications device tends to be personal data of a user of the device as opposed to corporate or enterprise level information. As such, what is needed are systems and methods for creating and assigning a policy to a device. For example, a policy may be created based on personal data and/or personal use of a mobile communications device and the policy may be used to prevent the unauthorized access or leakage of personal data on the mobile communications device.

Summary

[0005] In some embodiments, a method may identify one or more locations for storing data on a mobile communications device and identify personal data stored at the one or more locations on the mobile communications device. The method may further generate a policy for the mobile communications device based on the personal data and identify a set of personal data associated with the mobile communications device based on the policy. A set of personal data on the mobile communications device may be monitored and an access of the monitored set of personal data by an application executed on the mobile communications device may be detected. The method may be performed by the mobile communications device, a server, or a combination of both. For example, some of the steps of the method may be performed by the mobile communications device and other steps of the method may be performed by the server.

[0006] In some embodiments, the identifying of the set of personal data on the mobile communications device is based on using the policy to identify additional personal data stored on the mobile communications device. In the same or alternative embodiments, the set of personal data includes the identified personal data stored at the one or more locations on the mobile communications device and the identified additional personal data. Furthermore, the personal data may include data from at least one of a contacts database, email database, a database containing communications received or transmitted by the mobile communications device, or location information of the mobile communications device. In some embodiments, the step of detecting the access of the monitored data involves determining if the access resulted in a transmission of at least part of the monitored set of personal data from the mobile communications device. In the same or alternative embodiments, the application is associated with a container wrapper and the step of detecting the access of the monitored set of personal data is based on an interface of the container wrapper. For example, the application may be contained within the container wrapper and instances of the application interacting with an interface of the container wrapper (e.g., through a function call to access personal data external to the container wrapper) may be identified. In alternative embodiments, the monitored set of personal data is associated with a container wrapper and the step of detecting the access of the monitored set of personal data is based on an interface of the container wrapper. For example, the monitored personal data may be contained within the container wrapper and instances of the application interacting with the interface of the container wrapper (e.g., through a function call to the container wrapper to access the personal data) may be identified.

[0007] In some embodiments, a method may identify personal data associated with a mobile communications device and receive an analysis associated with the mobile communications device from a server. A policy for the mobile communications device may be generated based on the personal data associated with the mobile communications device and the analysis from the server. The policy may be assigned to the mobile communications device and data on the mobile communications device may be monitored based on the policy. Furthermore, an access of the monitored data by an application that is executed on the mobile communications device may be detected. In some embodiments, the mobile communications device identifies the personal data associated with the mobile communications device and transmits the identification of the personal data to a server that generates the policy. In an alternative embodiment, the mobile communications device generates the policy after identifying the personal data and receiving the analysis from the server.

[0008] In some embodiments, the analysis from the server is at least partly based on one or more applications installed on the mobile communications device. Furthermore, the analysis may be at least partly based on known access to data performed by at least one application installed on the mobile communications device.

[0009] In some embodiments, a method may identify a first set of personal data associated with a mobile communications device and create a policy based on the first set of personal data associated with the mobile communications device. A second set of personal data associated with the mobile communications device may be identified based on the policy. The second set of personal data may comprise the first set of personal data and additional personal data. The second set of personal data associated with the mobile communications device may be monitored and access of the second set of personal data by at least one application executed on the mobile communications device may be detected.

[0010] In some embodiments, a notification of the detecting of access of the second set of personal data may be displayed. The notification may identify the application accessing the second set of personal data and an option to allow for the access or not allow the access.

Brief Description of the Drawings

[0011] FIG. 1 illustrates a diagram of an example system for creating and assigning a policy for an electronic device in accordance with some embodiments.

[0012] FIG. 2 illustrates a block diagram of an electronic device in accordance with some embodiments of the disclosure.

[0013] FIG. 3 illustrates a block diagram of a policy management system or module to create and assign a policy to an electronic device in accordance with some embodiments.

[0014] FIG. 4 illustrates a flow diagram of an example method of using personal data and a policy in accordance with some embodiments.

[0015] FIG. 5 illustrates a flow diagram of an example method to create and assign a policy to an electronic device in accordance with some embodiments of the disclosure.

[0016] FIG. 6 illustrates a flow diagram of an example method to create a policy based on personal data stored on a device in accordance with some embodiments.

[0017] FIG. 7 illustrates a flow diagram of an example method to create a policy based on personal data associated with a device and server data.

[0018] FIG. 8 illustrates an example method to monitor data and record access of the monitored data based on a policy in accordance with some embodiments.

[0019] FIG. 9 illustrates an example of a personal data access report displaying access to personal data that is monitored based on a policy in accordance with some embodiments of the disclosure.

[0020] FIG. 10 illustrates an example graphical user interface notifying a user of an attempt to access monitored personal data in accordance with some embodiments.

Detailed Description

[0021] The present disclosure may be implemented in numerous ways including, but not limited to, as a process, an apparatus, a system, a device, a method, or a computer readable medium such as a non-transitory computer readable storage medium containing computer readable instructions or computer program code, or a computer network wherein computer readable instructions or computer program code are sent over optical or electronic communication links. Applications, software programs or computer readable instructions may be referred to as components or modules. Applications may take the form of software executing on a general purpose computer or be hardwired or hard coded in hardware. Applications may also be downloaded in whole or in part through the use of a software development kit, framework, or toolkit that enables the creation and implementation of the present disclosure. Applications may also include web applications, which include components that run on the device in a web browser. In this specification, these implementations, or any other form that the disclosure may take, may be referred to as techniques. In general, the order of the steps of disclosed methods may be altered within the scope of the disclosure, except in those instances where it is specified that the order of steps must be in a particular sequence.

[0022] As used herein, the term “mobile communications device” may refer to mobile phones, PDAs and smartphones. The term “mobile communications device” may also refer to a class of laptop computers which run an operating system that is also used on mobile phones, PDAs, or smartphones. Such laptop computers are often designed to operate with a continuous connection to a cellular network or to the internet via a wireless link. The term “mobile communications device” excludes other laptop computers, notebook computers, or sub-notebook computers that do not run an operating system that is also used on mobile phones, PDAs, and smartphones. Specifically, mobile communications devices include devices for which wireless communications services such as voice, messaging, data, or other wireless Internet capabilities are a primary function.

[0023] As used herein, a “mobile communications device” may also be referred to as a “device,” “mobile device,” “mobile client,” “electronic device,” or “handset.”However, a person having skill in the art will appreciate that while the present disclosure refers to systems and methods being used on mobile communications devices, the present disclosure may also be used on other computing platforms including, but not limited to, desktop, laptop, notebook, netbook, or server computers.

[0024] As used herein, the term “client computer” may refer to any computer, embedded device, mobile device, or other system that can be used to perform the functionality described as being performed by the client computer. Specifically, client computers include devices which can be used to display a user interface by which the functionality provided by the server can be utilized by a user. Client computers may be able to display a web page, load an application, load a widget, or perform other display functionality that allows the client computer to report information from the server to the user and to receive input from the user in order to send requests to the server.

[0025] Prior to describing in detail systems and methods for creating and assigning a policy for an electronic device based on personal data, a system in which the disclosure may be implemented shall first be described. Those of ordinary skill in the art will appreciate that the elements illustrated in FIG. 1 may vary depending on the system implementation.

[0026] As shown in FIG. 1, the system may include mobile communications devices 101, 101a and a server 111. An example mobile communications device 101 may include an operating system 113, an input device 115, a radio frequency transceiver(s) 116, a visual display 125, and a battery or power supply 119. Each of these components may be coupled to a central processing unit (CPU) 103. The mobile communications device operating system 113 runs on the CPU 103 and enables interaction between application programs and the mobile communications device hardware components. In some embodiments, the mobile communications device 101 receives data through an RF transceiver(s) 116 which may be able to communicate via various networks including, but not limited to, Bluetooth, local area networks such as Wi-Fi, and cellular networks such as GSM or CDMA.

[0027] In some embodiments, a local software component 175 is an application program that is downloaded to a mobile communications device and installed so that it integrates with the operating system 113. Much of the source code for the local software component 175 can be re-used between various mobile device platforms by using a cross-platform software architecture. In such a system, the majority of software functionality can be implemented in a cross-platform core module. The cross-platform core can be universal allowing it to interface with various mobile device operating systems by using a platform-specific module and a platform abstraction module that both interact with the mobile device operating system 113, which is described in U.S. Pat. No. 8,099,472, entitled “SYSTEM AND METHOD FOR A MOBILE CROSS-PLATFORM SOFTWARE SYSTEM,” incorporated herein by reference. In another embodiment, the local software component 175 can be device, platform or operating system specific.

[0028] The mobile communications device 101 may access a communications network 121 that permits access to a server 111. The server 111 may also be accessed by another mobile communications device 101a via network 121. The network 121 will normally be the Internet but can also be any other communications network. Alternatively, the mobile communications device 101 may access the server 111 by a different network than the network the other mobile communications device 101a accesses the server 111. In some embodiments, the server 111 is provided with server software 117. The server software 117 on the server 111 provides functionality to allow two-way communication between the server 111 and the mobile communications devices 101, 101a through the network 121. The server software 117 allows data, such as location-related information, pictures, contacts, videos, SMS messages, call history, event logs, and settings to be transferred from the mobile communications device 101 to the other mobile communications device 101a and vice versa.

[0029] It is understood by those of ordinary skill in the art that the functionality performed by server 111 does not necessarily have to be accomplished on a single hardware device. In this context, the use of the term server is intended to refer to one or more computers operating in cooperation or collaboration to provide the functionality described herein. The computers may be co-located or in different locations. The computers may inter-operate in such a way that portions of functionality are provided by separate services that may or may not be operated by the same entity as other computers which provide other functionality. For example, one set of servers may provide data storage functionality while another provides all other functionality. The data storage servers may be operated by a separate company than the servers that provide the other functionality. S3 (simple storage system), from Amazon, Inc. is such a data storage service which may be utilized by separate set of computers to enable the present invention.

[0030] It should be understood that the arrangement of electronic mobile communications device 101 illustrated in FIG. 1 is but one possible implementation and that other arrangements are possible. It should also be understood that the various system components defined by the claims, described below, and illustrated in the various block diagrams represent logical components that are configured to perform the functionality described herein. For example, one or more of these system components (and means) can be realized, in whole or in part, by at least some of the components illustrated in the arrangement of mobile communications device 101. In addition, while at least one of these components are implemented at least partially as an electronic hardware component, and therefore constitutes a machine, the other components may be implemented in software, hardware, or a combination of software and hardware. More particularly, at least one component defined by the claims is implemented at least partially as an electronic hardware component, such as an instruction execution machine (e.g., a processor-based or processor-containing machine) and/or as specialized circuits or circuitry (e.g., discrete logic gates interconnected to perform a specialized function), such as those illustrated in FIG. 1. Other components may be implemented in software, hardware, or a combination of software and hardware. Moreover, some or all of these other components may be combined, some may be omitted altogether, and additional components can be added while still achieving the functionality described herein. Thus, the disclosure described herein can be embodied in many different variations, and all such variations known to those of ordinary skill are contemplated to be within the scope of what is claimed.

[0031] In the description that follows, the disclosure will be described with reference to acts and symbolic representations of operations that are performed by one or more devices, unless indicated otherwise. As such, it will be understood that such acts and operations, which are at times referred to as being computer-executed, include the manipulation by the processing unit of data in a structured form. This manipulation transforms the data or maintains it at locations in the memory system of the device, which reconfigures or otherwise alters the operation of the device in a manner well understood by those skilled in the art. The data structures where data is maintained are physical locations of the memory that have particular properties defined by the format of the data. However, while the disclosure is being described in the foregoing context, it is not meant to be limiting as those of skill in the art will appreciate that various of the acts and operation described hereinafter may also be implemented in hardware.

[0032] FIG. 2 illustrates a block diagram of an electronic device 200 in accordance with some embodiments of the disclosure. In general, the electronic device 200 may comprise a plurality of modules and components including a policy management module to create and assign a policy.

[0033] As shown in FIG. 2, the electronic device 200 may be configured to provide an execution environment to host at least one operating system 201, a plurality of applications 202 and 203, and a file system 204. In some embodiments, each of the plurality of applications 202 and 203 may include executable code, which when executed by a processor (e.g., CPU 103), may provide a service or function of the electronic device 200. Each of the plurality of applications 202 or 203 may be associated with at least a part of the application data 216. In the same or alternative embodiments, one or more of the plurality of applications 202 or 203 may access any of the file system 204 comprising file sources 206, 208, and 210, application data 216, device data 218, camera 230, speaker 232, network interface 234, and sensor(s) 232. For example, the electronic device 200 may host or run a plurality of applications 202 and 203. A first application may access or retrieve data from application data 216 and file source 206 from the file system 204. A second application may access or retrieve data from the device data 218 and file sources 208 and 210 from the file system 204. Furthermore, a third application may retrieve data generated from the camera 230 and sensor(s) 232 and access the network interface 234. As such, each of the applications of the plurality of applications 202 and 203 may access various types of data or files stored on the electronic device 200 as well as a functionality (e.g., camera 230, speaker 232, network interface 234, sensor(s) 232) of the electronic device 200.

[0034] In some embodiments, the electronic device 200 may also support the operation of a policy management module 220 that may be responsible for creating and assigning policies for the electronic device 200. In some embodiments, the policy management module 220 may operate in the electronic device 200 as a client application hosted by the electronic device 200, as is shown in FIG. 2. In an alternative embodiment, the policy management module 220 may be provided by and integrated within the operating system 201 of the electronic device 200. In either of the embodiments, the policy management module 220 may be configured to manage the creating and applying of policies described herein. In another embodiment, the policy management module 220 may operate on a server in communication with the electronic device 200. For example, the policy management module 220 may be executed on a server and may create the policy to be assigned to the electronic device 200. In some embodiments, the server may receive data (e.g., an identification of personal data) from the electronic device 200, create a policy based on the received data, and then transmit the policy to the electronic device 200. In an alternative embodiment, functions of the policy management module 220 may be distributed between the electronic device 200 and the server. For example, certain components or modules of the policy management module 220 may be executed by the electronic device 200 while other components or modules may be executed by the server. As such, both the electronic device 200 and a server may perform actions associated with the creating and using of a policy as disclosed herein. Further details with regard to the policy management module 220 are discussed in further detail below with relation to FIG. 3. In some embodiments, the application data 216, device data 218, and file system 204 with file sources 206, 208, and 210 may store a plurality of types of information, files, or data. Such information, files, or data may include sensitive personal data. As such, it may be desirable for the user of the electronic device 200 to restrict access to such personal data and/or to be notified when one or more applications from the plurality of applications 202 and 203 executing on the electronic device 200 access the personal data. In some embodiments, the policy management module 220 executing on the electronic device 200 may identify the personal data stored on the electronic device 200, create a policy based on the identified personal data, monitor the identified personal data based on the policy, and report any access to the identified personal data based on the policy.

[0035] Examples of the previously mentioned data include, but are not limited to, personal data associated with the user of the electronic device 200. For example, the personal data may include personally identifiable information (PII) that may be used to identify the user of the electronic device 200. In some embodiments, the PII may include any information about the user of the electronic device 200 that can be used to distinguish or trace the user's identity as well as information that is linked to the user of the electronic device 200. Examples of such PII include, but are not limited to, the user's name, social security number, date and place of birth, mother's maiden name, driver's license number, passport number, firearm owner's identification card, username, email address, security questions and answers, digital certificates associated with the user, gender, marital status, race, religion, salary, biometric information (e.g., height, weight, eye color, hair color, fingerprint scans, retinal scans, medical information), financial information (e.g., credit card numbers, verification codes, expiration dates, debit card numbers, bank account numbers), family information (e.g., dependents, children, spouse, parents), emergency contact information, etc. These are just some examples of PII.

[0036] Additional examples of personal data associated with the user of the electronic device 200 may include, but are not limited to, contacts of the user of the electronic device 200 (e.g., an address book or phone number contact list), short message service (SMS) contacts, SMS messages transmitted or received by the user of the electronic device 200, email contacts, email database (e.g., the electronic device 200 may store emails from an email account of the user), email messages transmitted or received by the electronic device 200, phone logs, web logs or browser history (e.g., which websites has the user of the electronic device 200 visited), cookies, and phone numbers.

[0037] Further examples of personal data may include information that may be used to identify the electronic device 200. For example, the personal data may include, but is not limited to, International Mobile Station Equipment Identity (IMEI), International Mobile Subscriber Identity (IMSI), Integrated Circuit Card Identifier (ICCID), Mobile Equipment Identifier (MEID), Electronic Serial Numbers (ESN), Unique Device Identifier (UDID), Media Access Control (MAC) Address, the applications that are installed on the electronic device 200 (e.g., plurality of applications 202 and 203), and a phone number associated with the electronic device 200.

[0038] Still further examples of personal data may include data from one or more components of the electronic device 200 (e.g., camera 230, speaker 232, network interface 234, sensor(s) 232). For example, the personal data may include images or photos taken by the camera 230, location information from the sensor 232 of the electronic device 200 (e.g., a current physical location of the electronic device 200), a location history of the electronic device 200, or a log or history of domains, IP addresses, other devices that the electronic device 200 has communicated with. Additionally, location information or other PII may be embedded as metadata, e.g., Exchangeable image file format (Exit) metadata. Such information is usually placed automatically by applications or cameras into image files without the actions of a user.

[0039] Additional examples of personal data may include data which can be used to make inferences about other user personal data. For example, an application that obtains repeated process memory size of a browser application's process can use that information to fingerprint which websites the user is visiting. Thus, although the occasional access to process memory size information does not expose personal data, the repeated access to this information can expose personal data. Detection of repeated access and reporting of repeated access to such system level information that can be used for inferences about other personal data may also be included as personal data. Another example of system related information which can be used to infer personal data is the set of plugins or extensions installed in a browser application. Research has shown that the combination of the browser's user-agent string and the list of installed plugins or extensions can fingerprint a user that may be used to uniquely identify a particular device or user. Thus, an application that attempts to retrieve the complete list of installed plugins or extensions for a browser application can be considered to be accessing another type of personal data. Similarly, devices frequently broadcast the names (SSIDs) of their favorite or recently connected to networks to facilitate discovery and subsequent connection to known or preferred networks. These network names (SSIDs) constitute another example of personal data which can be used to make inferences about other user personal data. For example, the names may reveal recent user locations, user buying preferences, user medical conditions (user's device is trying to connect to “Oncology-Clinic-Free-Wifi”) or other items of a personal nature that can be inferred. In such a case it may be advisable to adjust settings or use application wrappers or operating system functions or hooks to prevent the device from broadcasting some or all of such network names according to a privacy policy. Devices can still connect to such networks by passive discovery (listening for network names broadcast from network access points). Such inferred information could be used by a listener for targeting advertisements or tailoring search results presented to a user of the device. Similarly, an application running on the device may attempt to obtain this list of recently used network names (SSIDs).

[0040] As such, the personal data may include PII data, application related information (e.g., which applications are installed on the electronic device 200), device related information (e.g., identifiers associated with the device), communication related information (e.g., phone logs, emails, SMS messages, etc.), information obtained by the device (e.g., location information), or any personal files or data stored by the user (e.g., files in the file system 204). Such data may be personal to the user and use of the electronic device 200.

[0041] FIG. 3 illustrates a block diagram of a policy management module 220 to create and to assign a policy for a mobile communications device (e.g., electronic device 200). In general, the policy management module 220 may create and assign a policy for a mobile communications device. In some embodiments, the policy management module 220 may be executed on the mobile communications device. In alternative embodiments, the policy management module 200 may be executed from a server. In another embodiment, components or modules of the policy management module 200 may be distributed between the mobile communications device and the server.

[0042] As shown in FIG. 3, the policy management module 220 may comprise a data identifier module 310. In some embodiments, the data identifier module 310 may identify data associated with the electronic device 200. For example, the data identifier module 310 may identify personal data of a user of the electronic device as previously disclosed. In some embodiments, the data identifier module 310 may identify locations on the electronic device 200 (e.g., areas in the file system 204) that are storing the personal data and may further identify types of personal data that is stored on the electronic device 200 or may identify a use of the electronic device 200. The policy management module 220 may further comprise a policy creator module 320. In some embodiments, the policy creator module 320 may create a policy based on the personal data identified by the data identifier module 310. The policy may be created for the electronic device 200 based on the personal data that is stored on the electronic device 200 and the personal use by the user of the electronic device 200. Further detail with regards to identifying data (e.g., by the data identifier module 310) and creating a policy (e.g., by the policy creator module 320) are disclosed in further detail below with relation to FIGS. 5 and 6.

[0043] As shown in FIG. 3, the policy management module 220 may further comprise a policy assigner module 330. In some embodiments, the policy assigner module 330 may assign a policy to the electronic device 200. In some embodiments, a plurality of policies may be available to the policy assigner 330. For example, the policies storage 370 may comprise a plurality of policies that have been created for the electronic device 200 and the policy assigner 330 may select one of the plurality of policies that are located in the policies storage 370. As shown, the policy management module 220 may further include a data monitor module 340. In some embodiments, the data monitor module 340 may monitor personal data that has been identified by the data identifier module 310 and/or personal data that is subject to the policy assigned by the policy assigner module 330. Further details with regard to monitoring data (e.g., by the data identifier module 330) are disclosed with relation to FIG. 8. As shown in FIG. 3, the policy management module 220 may further include an alert notifier module 350. In some embodiments, the alert notifier module 350 may receive an indication from the data monitor module 340 that an access of personal data subject to the policy assigned by the policy assigner module 330 has been detected. In response to such detection, the alert notifier module 350 may notify the user of the electronic device 200 of the detection of an instance of an application accessing the personal data. Further details with regard to such notifications (e.g., by the alert notifier module 350) are disclosed with relation to FIG. 10. The policy management module 220 may further include a policy reporter module 360. In some embodiments, the policy reporter module 360 may receive notifications from the alert notifier 350 of access to personal data by one or more applications. The policy reporter module 360 may aggregate the notifications that are received from the alert notifier 350 and generate a report comprising information detailing which applications (e.g., applications from the plurality of application 202 and 203) have accessed personal data. The generated report may be stored in the reports storage 380 and may further be presented to a user of the electronic device 200. Further details with regard to the generation and presentation of reports (e.g., by the policy reporter module 360) are disclosed with relation to FIG. 9.

[0044] FIG. 4 illustrates a flow diagram of a method 400 for using personal data and a policy. As shown, at step 410, personal data may be received. For example, the data identifier module 310 of the policy management module 220 may receive or identify personal data stored in memory on the mobile communications device. In some embodiments, the personal data may be stored on the electronic device 200. At step 420, a policy may be generated based on the personal data. For example, the policy creator module 320 of the policy management module 220 may create or generate the policy based on the personal data that was received at step 410. In some embodiments, the policy may comprise a set of instructions used to identify data and/or actions to be performed for the identified data. For example, the policy may be a data leakage policy that is used to identify different types of data stored on the electronic device 200, monitor the different types of data, and/or control access to the different types of data. In some embodiments, the policy may be generated based on some amount of personal data in order to identify additional personal data. For example, a plurality of personal data may be stored on the electronic device 200. A subset of the plurality of personal data may be identified or received by the policy management module 220 and a policy may be generated based on the subset of the personal data stored on the electronic device 200. The policy may then be used to identify additional personal data stored on the electronic device 200. As such, the policy may be created based on a smaller set of personal data and then used to detect or identify a larger set of personal data. Thus, at step 430, additional data may be identified based on the created policy.

[0045] As such, the policy may be created based on an initial set of personal data. In some embodiments, the initial set of personal data may be identified based on one or more methods. For example, the initial set of personal data may be identified based on known sources of personal data. Such locations on an electronic device 200 may include, but are not limited to, databases of user information, email databases associated with the electronic device 200 (e.g., locations of stored emails), contact information (e.g., a contact list or phone book on the electronic device 200), SMS information (e.g., SMS messages sent or received on the electronic device 200), etc. As such, there may be one or more defined or known storage locations on the electronic device 200 that contain personal data. The personal data in the defined or known storage locations may then be used to generate a policy to identify additional personal data stored on the electronic device 200. Thus, the policy may be generated based on exact data matching from the defined or known storage locations of personal data.

[0046] In some embodiments, the policy may be generated based on indexed document matching. For example, the policy may be generated based on text in one or more known personal data files. Additional data that matches at least some of the text in the one or more known personal data files may then be identified by the policy as personal data that is to be monitored. Thus, the profile may be generated based on text in a document or corpus of documents. In the same or alternative embodiments, personal data may be identified based on data identifiers. For example, a social security number may be identified in a personal data file based on its nine digits and optional dashes. Files that include such a data identifier may be used in the creation of the policy. The policy may further be generated based on a classifier. For example, a classifier (e.g., a Support Vector Machine that analyzes data and recognizes patterns) may analyze a set of personal data files (e.g., from defined or previously known locations on the electronic device 200) sorted by classification and the resulting model may be used to identify additional personal data that matches the classifications of the model.

[0047] Thus, the policy may be generated based on known sets of data (e.g., personal data) stored at known locations (e.g., an email account, file system locations, contacts list, etc.) or known uses of the electronic device 200. The policy may then be used to identify additional sets of data (e.g., additional personal data) stored at other locations on the electronic device 200.

[0048] FIG. 5 illustrates a flow diagram of a method 500 to create and assign a policy to an electronic device (e.g., electronic device 200). In general, the method 500 may be performed by the policy management module 220 to report access of monitored personal data by the operating system and/or at least one application executing on the device.

[0049] As shown in FIG. 5, the method 500 may identify, at step 510, one or more locations of stored data on the electronic device. For example, the data identifier module 310 of the policy management module 220 may identify one or more known or predefined locations where personal data is stored on the electronic device. In some embodiments, the one or more known or predefined locations may include, but is not limited to, a location in the file storage system of the electronic device, storage for emails received or downloaded by the electronic device from an email account of the user associated with the electronic device, a storage location for a contacts list (e.g., phone numbers and addresses) associated with the electronic device, and a subscriber identification module (SIM) that may store the IMSI, ICCID, SMS messages, phone book contacts, and other data of the electronic device. At step 520, personal data may be identified from the one or more known or predefined locations. In some embodiments, the data stored in the one or more known or predefined locations may be identified as personal data. For example, the method 500 may identify any data stored on the SIM card, contacts list, email account, etc. as being personal data. Next, at step 530, a policy (e.g., a data leakage policy) may be created based on the personal data identified at step 520. For example, the policy creator 320 of the policy management module 220 may create or generate the policy based on the personal data that has been identified at one or more known or predefined locations on the electronic device 200. In some embodiments, the created policy may also be stored in the policies storage 370. At step 540, the policy may be assigned to the electronic device. For example, the policy assigner module 330 of the policy management module 220 may assign the policy to the electronic device 200. The method 500 may further monitor data based on the assigned policy. For example, the data monitor module 340 of the policy management module 220 may monitor data based on the policy. In some embodiments, the monitored data may be additional personal data (e.g., personal data from a plurality of locations associated with the electronic device) that has matched or been identified by the policy. In the same or alternative embodiments, the monitoring of the data may be performed in response to the assigning of the policy. For example, different personal data may be monitored based on the policy that has been assigned to the electronic device.

[0050] At step 560, an access of the monitored data may be detected. For example, the data monitor 340 of the policy management module 220 may detect an application (e.g., from the plurality of applications 202 and 203) that is executed on the electronic device 200 has accessed personal data that has been identified by the policy. In some embodiments, the detected access of the personal data by the application may involve the application accessing the personal data from the file system of the electronic device and/or transferring the personal data from the electronic device to another destination (e.g., a server, another electronic device, etc.) over a network (e.g., the Internet or cellular network). At step 570, the access of the monitored data may be reported. For example, the alert notifier 350 of the policy management module 220 may generate an alert notification for the user of the electronic device and/or the policy reporter 360 of the policy management module 220 may generate a report based on the detection of an application accessing personal data that has been identified by the policy. Further details with regard to reporting the access of the monitored personal data are disclosed with relation to FIGS. 9 and 10.

[0051] As such, one or more known or predefined locations or known or predefined sources of personal data stored on an electronic device may be identified. The data from the predefined locations or predefined sources may be identified as personal data. A policy may be created based on the personal data from the predefined locations or predefined sources. The policy may be assigned to the electronic device and the policy may be used to identify additional personal data (e.g., the personal data from the known or predefined locations or sources as well as additional personal data elsewhere on the electronic device). The additional personal data may be monitored. If an application that is executed on the electronic device accesses the monitored personal data, then a user of the electronic device may be notified of the access of the monitored personal data. Furthermore, a report may be created to detail and provide additional information with regard to the access of the personal data on the electronic device.

[0052] FIG. 6 illustrates a flow diagram of a method 600 to create a policy based on personal data stored on a device. In general, a policy management module 220 may receive or identify a plurality of types of personal data associated with an electronic device 200 and/or a user of the electronic device 200 and may generate a policy based on the personal data.

[0053] As shown in FIG. 6, the method 600 may receive, at step 610, a personal contacts database stored on an electronic device 200. The personal contacts database may include contact information from a contact list or phone book stored on the electronic device. In some embodiments, the contact list may comprise information to identify a plurality of phone contacts and a phone history log (e.g., phone numbers and/or identities of users associated with the phone numbers that the electronic device 200 has placed calls to or received calls from). In the same or alternative embodiments, the personal contacts database may also include an SMS log or history and any other identifier used in inbound or outbound communication from the electronic device 200. As such, the method 600 may receive communication-related information associated with the electronic device 200. The communication-related information may be based on the use of the electronic device 200 (e.g., of prior phone calls, prior SMS messages, etc. that were placed or received by the electronic device). Furthermore, at step 620, the method 600 may receive a personal email database stored on the device. The personal email database may include emails from a personal email account that is associated with a user of the electronic device 200. For example, the electronic device 200 may be configured to access one or more personal email accounts of a user and downloads and/or to transmit email messages to and from the electronic device 200. At step 630, the method 600 may receive personal files stored on the file system of the device. For example, any type of personal data stored on the file system of the electronic device 200 may be received. Examples of such personal data may include, but is not limited to, web-related information such as web browser history, browser cookies, browser's installed extensions or plug-ins, HTML5 local storage, and application data and personal-related information of a user of the electronic device. The method 600 may further receive, at step 640, device specific data. For example, device-related information of the electronic device 200 may be received. In some embodiments, the device-related information may include any type of unique identifier associated with the electronic device including, but not limited to, the IMEI, IMSI, ICCID, MEID, ESN, UDID, MAC address, and a phone number. At step 650, data created by the device may be received. For example, photos created from a camera of the electronic device 200, sensor data created by various sensors of the electronic device (e.g., location data from a GPS component), or any type of log or history information created by the electronic device may be received. At step 660, a personal use of the device may be identified. For example, information indicating that a user of the electronic device 200 uses the electronic device to check one or more email accounts, has certain applications installed (e.g., application-related information), uses the electronic device to connect to various websites, uses a telephone functionality of the electronic device 200, uses an SMS functionality of the electronic device 200, uses a camera component of the electronic device 200 to take photos, and has activated a location determination component (e.g., GPS), etc. may be identified. As such, use-related information of the electronic device 200 may be identified.

[0054] At step 670, a policy may be generated based on the received or identified data or information. As previously disclosed with relation to FIG. 4, the policy may be generated based on personal data. For example, the policy may be generated based on personal data stored on a mobile communications device. Thus, the policy may be considered a custom policy created specifically for the mobile communications device based on the personal data that is currently stored on the mobile communications device. In some embodiment, the policy may be generated based on the personal data stored on the mobile communications device as well as features of the mobile communications device. Examples of the features of the mobile communications device include, but are not limited to, functionality of the mobile communications device (e.g., a camera, location determination components, etc.) and an operating system executed on the mobile communications device. As such, the generated policy may be at least partly platform specific (e.g., specific to an operating system of the mobile communications device) and/or at least partly based on the personal data stored on the mobile communications device.

[0055] Although the steps described above disclose certain types of data or information, any type of personal data or device specific data or information may be used received and/or identified to generate the policy. For example, data on a storage device (e.g., a non-volatile memory card such as a Secure Digital card) coupled to the electronic device 200 may be used to generate the policy.

[0056] FIG. 7 illustrates a flow diagram of a method 700 to create a policy based on personal data associated with a device and data from a server. As shown in FIG. 7, at step 710, an identification of personal data stored on a device may be performed. Such personal data may include any of the types of data associated with the electronic device disclosed herein. At step 720, server data may be received. For example, server analysis data may be received by the policy management module 220 of the electronic device 200. In some embodiments, the server may be a remote server (e.g., a server in communication with the electronic device 200 over a network) and may receive data from the electronic device 200. The server may then analyze the data and transmit data based on the analysis to the electronic device. In some embodiments, the server may receive an identification of specific applications that have been installed and/or are executed on the electronic device 200 and may transmit data based on such identification to the electronic device 200. For example, the server may provide an analysis based on known behavior of the applications that have been installed on the electronic device. Such known behavior may include types of personal data that the installed applications are known to access.

[0057] In some embodiments, the server may also create a set of per application data. For example, the server may create fake or false personal data and transmit the fake or false personal data to the electronic device 200. As such, the fake or false personal data may be unique and access of the fake or false personal data may be monitored (e.g., by the policy management module 220). The fake or false personal data generated may be unique to the particular application, or may be unique to the particular device, or may be unique to the particular user who is using the device, or may be unique to any combination of the above. If any application accesses the fake or false personal data, then the access may be tracked (e.g., determine if the fake or false data was transmitted off of the electronic device 200 over a network) and the server and/or electronic device may identify the application that has accessed the fake or false personal data. Furthermore, a report may be generated to alert the user that the application is accessing the fake or false personal data. Additionally, any subsequent detection of the attempted use of the unique fake or false personal data (e.g., a fake phone number or fake email address) by receiving a communication at the unique fake or false address may result in reporting the usage to the user, identifying that the application for which the fake or false data was generated is an abuser of personal data (e.g., the application is attempting unauthorized access of personal data), and tracking the origin of the communication involving the fake or false address. A policy to disallow access by such an application to personal data may be created and distributed to multiple devices. In a specific embodiment, a known data leaking app or website may be provided with fake information in response to any attempts by the app or website to obtain personal data. In another embodiment apps or web applications can in a laboratory setting be run in a dynamic analysis or emulator farm which is capable of in depth instrumentation on all operations of the app or web application, e.g., crashes, locations accessed on the device or on the network, any personal data access or leakage, type and contents of network traffic, memory usage growth, processor usage over time, number of calls or SMS or other messages sent. Such apps or web applications in the laboratory can be provided with fake data, e.g., email addresses or phone numbers. Subsequent detection of messages or calls to these identifiers can characterize the app or website application as leaking personal data. Such characterization can be used to formulate specific policy for said app or website application, or for other apps or website applications developed by the same developer (as indicated by app signature) or organization (as indicated by domain of the web application). Additionally, app developers can be notified if the developer's app or website application is exhibiting insecure behavior or is capturing or transmitting or otherwise using personal data.

[0058] Returning to FIG. 7, at step 730, the policy may be created based on the data associated with the device and the data associated with the server. Furthermore, at step 740, the policy may be assigned to the electronic device.

[0059] In some embodiments, the policy may be created based on personal data associated with a plurality of devices. For example, different types of personal data may be stored on different devices. A policy may then be generated based on the different types of personal data on the plurality of devices and the policy may be applied to each of the plurality of devices. For example, devices may exchange the identification of the personal data with each other or may transmit to a server the identification of the personal data. The server may optionally provide server analysis data as previously disclosed and may receive the identification of the personal data from the plurality of devices and generate a policy based on the personal data from the plurality of devices. The policy may then be transmitted back to each device and assigned to each of the devices. Thus, a portable policy (e.g., a policy applied to any mobile device) may be created at the server and applied to a plurality of devices.

[0060] FIG. 8 illustrates a method 800 to monitor data and record access of the monitored data based on the application of a policy. In general, the data monitor module 340 of the policy management module 220 may monitor personal data identified by the policy as data for which access should be monitored and the alert notifier module 350 and policy reporter 360 of the policy management module 220 may alert a user of the electronic device 200 of access of personal data and generate a report aggregating a plurality of detected accesses of personal data by one or more applications.

[0061] As shown in FIG. 8, at step 810, a policy may be assigned to the electronic device. For example, the policy may be assigned by the policy management module 220. At step 820, personal data associated with the electronic device may be monitored based on the assigned policy. For example, the assigned policy may be used to identify personal data that is accessible by the electronic device. Such identified personal data may then be monitored for access by one or more applications executed on the electronic device. At step 830, a determination may be made as to whether access of the personal data that has been monitored at step 820 has been detected. If no such access has been detected, then the method 800 may return to monitoring the personal data at step 820. However, if a detection of the personal data occurs, then at step 840, a user of the electronic device may be notified of the application that has accessed or is attempting to access the monitored personal data. For example, an alert notification may be displayed on a screen of the electronic device and comprise information indicating that a specific piece of personal data is being accessed by a particular application. In some embodiments, the alert notification may also include options to allow or disallow the attempted access of the personal data by the application. Further details with regard to such an alert notification are disclosed with relation to FIG. 10. Furthermore, at step 850, the access or attempted access of the monitored personal data by the application may be recorded and/or aggregated (e.g., with other reported access of personal data by applications) to be included in a generated report. Further details with regard to such a report are disclosed with relation to FIG. 9. In some embodiments, the method may return to the monitoring of access to the personal data at step 820 after such notifications and/or generation of such reports.

[0062] In some embodiments, access of the personal data by one or more applications (e.g., at step 830) may be detected by various methods. Examples of such methods include, but are not limited to, configuring the operating system of the electronic device to detect such access (e.g., the policy management module 220 is a part of the operating system), monitoring system logs and/or file system logs (e.g., identifying access of personal data from scanning the file system logs), and inserting the policy management module 220 as a browser plug-in and detecting if a browser is accessing personal data on the electronic device.

[0063] In some embodiments, the access of the personal data may be detected based on application containerization or electronic device containerization (e.g., mobile device containerization). The containerization may involve an approach to create separate environments for applications and/or personal data. For example, an encrypted space or folder on the electronic device 200 may be used to store personal data and/or applications. In some embodiments, the containerization may involve application wrapping. For example, application wrapping container may involve using the operating system of the electronic device 200 and application program interfaces (APIs) to provide a sandboxed environment for personal data and/or applications. This may be performed for each set of personal data or for each application. In some embodiments, such a process may result in each application being enclosed in its own unique container. As such, a container may be placed around individual applications or sets of applications. Furthermore, the attempted access to the personal data may be detected based on API accesses of the containers. For example, the policy management module 220 may detect the API attempt or actual access to the personal data from one or more applications. The application wrapping container may rewire sensitive API calls to the personal data sources and filter access to the personal data sources. Such an application wrapping container may enable the monitoring of encrypted network traffic (e.g., SSL library hooking) and not allow access to the personal data sources by hooking and disabling the APIs of the applications with the application wrapping container or even disabling the functionality of the applications to transmit the personal data over a network or writing the personal data to an unsecure portion of the file system. As such, the detection of the access of personal data by one or more applications may be based on detecting API access (e.g., corresponding to an application wrapping container) and/or based on detecting a transmission of the personal data over a network. Further embodiments may detect access of personal data based on a server side characterization, as discussed in further detail below. Thus, the applications may be run in a container.

[0064] In some embodiments, the containerization process as disclosed above may be performed with respect to the storage of personal data. For example, a container wrapper may be configured on the electronic device 200 to be applied to personal data that is identified on the electronic device. Any access to the personal data must then use the interface (e.g., API) of the container wrapper applied to the personal data in order to access the personal data. As such, personal data may be identified on the electronic device 200 and places the container wrapper around the personal data. In some embodiments, the personal data may then be encrypted and/or placed elsewhere on the electronic device 200 (e.g., in an encrypted folder on the file system). In the same or alternative embodiments, a bloom filter may be used to detect access to personal data. For example, a bloom filter associated with the personal data may be stored on the device and when a ‘hit’ of the bloom filter is detected (e.g., an application accessing personal data associated with the bloom filter), a remote server may be notified of the ‘hit’ of the bloom filter and provide a confirmation or identification of the specific personal data subject to the ‘hit’ of the bloom filter. In some embodiments, the containerization of the personal data may involve the use of a hook mechanism, as previously disclosed with relation to the application wrapping container. For example, a hook may be performed at the file system level, at an operating system level, on a virtual machine (VM), or on hardware (e.g., a special processor or Field Programmable Gate Array configured to detect access to personal data). In some embodiments, an interrupt may be raised or called in response to a detection of access to the personal data in memory, to and from a storage device, to and from a network interface, and as a parameter call (e.g., intra-application or inter-application calls or an application to system call).

[0065] In some embodiments, the access to the personal data from one or more applications may be based on a transmission of the personal data. For example, the policy management module 220 may detect that an application has transmitted personal data from the electronic device 200 to another destination (e.g., a server or another device) over a network. As such, the detection of the access of personal data may be based on identifying one or more applications transmitting the personal data off of the electronic device 200. Thus, the detection of the access to the personal data may be based on network traffic and observing that personal data has been transmitted from the electronic device 200 over a network.

[0066] In some embodiments, the access to the personal data may also be detected based on a dynamic analysis. For example, a server may provide a characterization of an application that identifies what the application may leak (e.g., what kind of personal data is accessed and/or transmitted by the application). In some embodiments, a virtual private network (VPN) may be configured on the electronic device 200. The VPN may then be used to monitor access to personal data. For example, network access by applications may be monitored within the VPN environment and personal data that is transmitted over the network may be detected. Further details with regard to monitoring network access by application within the VPN environment are disclosed in U.S. patent application Ser. No. 14/071,366, entitled “METHODS AND SYSTEMS FOR SECURE NETWORK CONNECTIONS,” filed on Nov. 4, 2013, which is incorporated herein by reference. Thus, network traffic associated with the electronic device 200 may be monitored for personal data leaving or being transmitted from the electronic device.

[0067] In some embodiments, the application container wrapper may be used to monitor a copy and paste function associated with the application. For example, the application container wrapper may hook the copy and paste function and apply the policy to the data contents of the copy and paste function being performed. Thus, the policy may monitor the copy and paste function for the presence of personal data. For example, if monitored personal data may be observed to be copied and pasted and such an act may be recorded or the copying and pasting of the monitored personal data may not be allowed.

[0068] In some embodiments, the policy may have been transmitted to a server 111 or to a piece of the infrastructure of the network 121 (such as a network access point or a switch or a router), which can observe the content of the communications from the device. The policy may be enforced on that location by inspecting the contents of the communications from the device for the presence of personal data. Notification messages can be sent to the owner or administrator of the device upon such detections. A communication whose content includes personal data may be blocked, depending on the specifics allowed in the policy. A command may be sent to the device to terminate the application which sent the personal data. The server or piece of network infrastructure may use special certificates in place of original site certificates to allow the inspection of SSL/TLS traffic; that is, the server or piece of network infrastructure is performing a sanctioned Man in the Middle (MiTM) operation in which there are two separate secured sessions from the server or piece of network infrastructure, one from the server or piece of network infrastructure to the original network destination using that location's valid certificate, and one from the server or piece of network infrastructure to the device using the specially provided certificate.

[0069] FIG. 9 illustrates an example of a personal data access report 900 displaying instances of access to monitored data based on a policy. In general, the personal data access report 900 may be generated by the policy reporter 360 of the policy management module 220 to display detected access of monitored personal data based on a policy by at least one application executed on the electronic device 200. The personal data access report 900 may be based upon a plurality of detected accesses of the monitored personal data. For example, the personal data access 900 may include information to identify and further describe an aggregation of a plurality of instances of access to personal data stored on the electronic device 200 by one or more applications.

[0070] As shown in FIG. 9, the personal data access report 900 may include multiple entries where each entry corresponds to at least one application that is executed on the electronic device 200 and has been detected to access monitored personal data within a particular time frame. For example, the monitored personal data access report 900 may be generated based on a particular time frame. Each detected access of personal data by an application during the time frame may be recorded and a plurality of the instances of detected access may be aggregated to form the personal data access report 900 for the time frame. As such, each of the entries 921, 922, and 923 of the personal data access report 900 may represent an application that has been detected to access at least one monitored personal data. In some embodiments, the personal data access report 900 may further include multiple fields for each of the entries. For example, an application identifier field 920, personal data identifier field 930, time field 940, transmission field 950, and an encrypted field 960 may be displayed as part of the personal data access report 900 for each of the entries 921, 922, and 923.

[0071] In some embodiments, the application identifier field 920 may identify an application that has been detected to access monitored personal data. For example, the application identifier field 920 may identify an application that is executed on the electronic device 200 that has been detected to access monitored personal data associated with the electronic device 200. In the example shown in FIG. 9, the entry 921 may be associated with the application identifier field 920 identifying a first application, the entry 922 may be associated with the application identifier field 920 identifying a second application, and the entry 923 may be associated with the application identifier field 920 identifying a third application. As such, a plurality of applications may be identified as having accessed monitored personal data. The personal data access report 900 may further include a personal data identifier field 930. In some embodiments, the personal data identifier field 930 may display information to identify a type of personal data that has been accessed by a corresponding application. For example, the personal data identifier field 930 may indicate that the first application corresponding to entry 921 has accessed personal data including contacts (e.g., contacts or phone numbers stored on the electronic device 200) and emails (e.g., emails accessed from an email account by the electronic device 200). The personal data identifier field 930 may also indicate that the second application corresponding to the entry 922 has accessed monitored personal data for a location (e.g., a location of the electronic device 200 obtained from a functionality of the electronic device such as a sensor) and that the third application corresponding to entry 923 has accessed personal data for a camera (e.g., camera photos created and stored on the electronic device 200) and one or more files on the file system of the electronic device 200. As such, the personal data identifier field 930 may identify a plurality of types of personal data that one or more applications have accessed. The time field 940 may indicate a time that each of the applications has accessed the corresponding personal data. For example, the time field 940 as shown identifies that the first application has accessed the contacts personal data at a first time and the emails personal data at a second time. The time field 940 further indicates that the second application has accessed the location personal data at a third time and that the third application has accessed both the camera personal data and the file system personal data at a fourth time. In some embodiments, the personal data access report 900 may further display a transmission field 950. In the same or alternative embodiments, the transmission field 950 may indicate whether an application from the entries 921, 922, and/or 923 has transmitted the personal data from the personal data identifier field 930 from the electronic device 200 to another destination (e.g., another device or server) over a network associated with the electronic device 200. For example, the transmission field 950 may indicate that the first application corresponding to entry 921 has transmitted both the contacts personal data and the email personal data from the electronic device 200 over a network. The transmission field 950 may further indicate that the second application corresponding to entry 922 has transmitted the location personal data from the electronic device 200 over a network and that the third application corresponding to entry 923 has not transmitted the camera personal data and file system personal data from the electronic device 200 over the network.

[0072] As shown in FIG. 9, the personal data access report 900 may further include an encrypted field 960. In some embodiments, the encrypted field 960 may indicate whether an application that has transmitted personal data off of the electronic device 200 did so while encrypting the personal data or transmitted the personal data without encrypting the personal data. For example, the encrypted field 960 may identify that the first application that transmitted the contacts personal data and email personal data did not encrypt either of the types of personal data that it accessed and subsequently transmitted. The encrypted field 960 may further identify that the second application encrypted the location personal data before transmitting the location personal data over the network. In some embodiments the personal data access report may also indicate where personal data was transmitted (e.g., a network destination).

[0073] The personal data access report 900 for a specific device may further include a count of all the items of a particular type of personal data that were accessed or a portion of or all of the actual personal data that was accessed. Furthermore, the personal data access report 900 may contain information regarding the context on the device at the time of access to the personal data. For example, the report may also record what applications were open at the time of access of the personal data, whether the electronic device was locked or unlocked, whether the accessing application was in the foreground (e.g., displayed) or not in the foreground (e.g., not displayed). In some embodiments, a personal data policy may have thresholds for each type of personal data access that is considered normal or allowable, for any application or for specific named applications, and the personal data access report may only report instances where the personal data policy is being violated.

[0074] As such, the personal data access report 900 may aggregate multiple instances of access of personal data by one or more applications. The personal data access report 900 may identify a particular type of personal data accessed by each of the applications, a time when the personal data was accessed by each of the applications, whether each application transmitted each accessed personal data off of the electronic device 200, and whether the personal data that was transmitted was encrypted or not. Thus, the personal data access report 900 may display the type of personal data or personal data related functionality of the electronic device that an application has accessed as well as additional details with regard to the type of personal data. Aggregated personal data access report information (with any personal data removed) may be made available separately to provide information to users about the personal data behavior or particular applications. For example, such information may be provided as part of a privacy report about applications, as additional information in application stores, or in databases of information about application characteristics or behavior. In some embodiments, an application installer on the electronic device 200 may use such a database of information about application characteristics or behavior in conjunction with a personal data policy to determine whether an application is allowed to be installed on the electronic device. For example, the user's or device's personal data policy may disallow applications which have a behavior of large scale access to contacts and the database of information about applications may indicate that application X has such a behavior. Thus, the application installer would not allow the installation of application X on the electronic device.

[0075] Although the personal data access report 900 shows certain types of fields and personal data, any type of personal data or fields identifying any type of information may be aggregated and/or displayed in the personal data access report 900. For example, the personal data access report 900 may further display a destination (e.g., IP address) that personal data was transmitted to, whether the electronic device was in a lock mode (e.g., an operation of the electronic device where user functionality of buttons or keys is disabled) or not in the lock mode, etc. In some embodiments, the personal data access report 900 may also display more detailed information. For example, specific contacts, emails, locations, camera photos, and files of the personal data that were accessed by the applications may be identified.

[0076] It may be normal for an application to access some personal data in the course of its operation. For example, an application that is designed to send emails or text messages may access a small number of contacts (e.g., a phone book, email list, etc.) on the electronic device and an application designed to backup data from the electronic device would in normal operation access all of the contacts on the electronic device. But it would not be normal for most applications to access a large number of contacts on the electronic device or all of the contacts on the electronic device. Recording the frequency of access to categories of personal data is used to prepare personal data access reports and may be used to develop policies on a per application basis regarding how much personal data may be accessed per application. For example, the application X that is designed for backing up contacts from the electronic device could have a policy that allows application X unlimited access to the contacts on the electronic device. However, the contacts policy for the electronic device may disallow any other application from accessing more than a configurable number or percentage of the contacts on the electronic device. For example, the policy could prevent other applications from accessing more than 20 contacts or more than 10% of the contacts on the device. The policy enforcement may have actions of reporting the attempted access, asking the user for permission for the application to perform the large scale access, or denying the large scale access. As such, a policy may be configured to allow for different amounts of personal data that may be accessed for different applications executed on the electronic device. The policy may define which types of personal data may be accessed by certain applications and which applications may not access a particular type of personal data.

[0077] In some embodiments, the policy may further define which destinations to which personal data may be transmitted. For example, the policy may allow a first set of personal data to be transmitted from the electronic device to a first network location (e.g., a website or server), but may not allow the first set of personal data to be transmitted from the electronic device to a second network location. Furthermore, in some embodiments, the policy may allow certain applications to be able to transmit personal data from the electronic device to a network location, but may not allow other applications to transmit personal data to a network location. In the same or alternative embodiments, the policy may allow specific applications to transmit specific personal data to a specific network location, but may not allow the applications to transmit other personal data to another network location or the specific personal data to another network location. As such, the policy may be used to allow or not allow access to personal data or transmission of personal data from the electronic device based on any combination of applications, personal data, and network locations (e.g., on a per application basis, per personal data basis, and/or per network location basis).

[0078] In some embodiments, the monitored personal data may be detected to be off of the electronic device. For example, a search engine may be used (e.g., by a server) to detect the monitored personal data at other servers or websites on the Internet. For example, the false or fake personal data as previously disclosed may be searched for on the Internet. In some embodiments, social network accounts for a user may be scanned to find or detect monitored personal data. Such a presence of personal data being off of the electronic device and found on another server or website may indicate that one or more applications executed on the electronic device is accessing personal data and transmitting the personal data off of the electronic device to another location. In some embodiments, a user may securely register his or her personal data with a search engine and the search engine may notify the user when the user's personal data is detected during a web crawl performed by the search engine.

[0079] In some embodiments, the personal data access report 900 may be sent to a server to be used to characterize personal data access patterns of one or more applications that are included in the personal data access report 900. For example, personal data access patterns may be identified by application or network location (e.g., website or network address). Thus, the server may be able to characterize which applications are accessing personal data as well as which network locations are receiving personal data that is transmitted from the electronic device.

[0080] FIG. 10 illustrates a graphical user interface 1000 notifying a user of an attempt to access monitored personal data. In general, the graphical user interface 1000 may provide a user of an electronic device 200 with an option to either allow or not allow access to monitored personal data by an application executed on the electronic device 200.

[0081] As shown in FIG. 10, the graphical user interface 1000 may display a notification 1010. For example, the notification 1010 may correspond to an attempt by an application executed on the electronic device 200 to access monitored personal data on the electronic device 200. In some embodiments, the notification 1010 may identify the application that is requesting or attempting to access personal data and/or the type of personal data that the application is requesting to access or is attempting to access. The graphical user interface 1000 may further include buttons to allow a user of the electronic device 200 to either allow or not allow the application to access the personal data. For example, the graphical user interface 1000 may include a ‘no’ button 1030 to not allow the application to access the personal data or a ‘yes’ button 1020 to allow the application to access the personal data. As such, a user of the electronic device 200 may be notified of each access by an application to personal data that is monitored based on the policy. Thus, the graphical user interface 1000 may provide a user of the electronic device 200 with a gated decision associated with applications attempting to access monitored personal data.

[0082] In some embodiments, a personal data access policy may be pushed to an electronic device from a server when a user logs in to the electronic device.

[0083] In the description above and throughout, numerous specific details are set forth in order to provide a thorough understanding of an embodiment of this disclosure. It will be evident, however, to one of ordinary skill in the art, that an embodiment 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 method disclosed herein, various steps are disclosed illustrating some of the functions of an embodiment. These steps are merely examples, 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 an embodiment.

Claims

What is claimed is:

1. A method comprising:

identifying, by a policy management module on a mobile communications device, one or more locations for storing personal data on the mobile communications device;

identifying, by the policy management module, a first set of personal data stored at the one or more locations on the mobile communications device;

generating, by the policy management module, a policy for the mobile communications device based on an analysis by the policy management module of the first set of personal data, the generated policy for identifying a second set of personal data stored on the mobile communications device and for controlling access to the second set of personal data;

identifying, by the policy management module, the second set of personal data stored on the mobile communications device based on the generated policy, the second set of personal data being different from the first set of personal data;

monitoring, by the policy management module, the second set of personal data stored on the mobile communications device based on the generated policy; and

detecting, by the policy management module, a request for access to the monitored second set of personal data by an application executed on the mobile communications device.

2. The method of claim 1, wherein the step of identifying the second set of personal data stored on the mobile communications device is achieved by using the generated policy to identify additional personal data stored on the mobile communications device.

3. The method of claim 2, further comprising monitoring, by the policy management module, the first set of personal data stored on the mobile communications device based on the generated policy.

4. The method of claim 1, wherein the first set of personal data comprises data from at least one of a contacts database, email database, a database containing communications received or transmitted by the mobile communications device, location information of the mobile communications device, or recently used network names.

5. The method of claim 1, wherein the step of detecting the request for access to the monitored second set of personal data includes determining if the requested access would result in a transmission of at least part of the second set of personal data from the mobile communications device.

6. The method of claim 1, wherein, when the executed application is associated with a container wrapper, the step of detecting the request for access to the monitored second set of personal data is based on the executed application interacting with an interface of the container wrapper.

7. The method of claim 1, wherein, when the monitored second set of personal data is associated with a container wrapper, the step of detecting the request for access to the monitored second set of personal data is based on the executed application interacting with an interface of the container wrapper.

8. A method comprising:

identifying, by a policy management module on a mobile communications device, a first set of personal data associated with the mobile communications device;

receiving, by the policy management module, from a server, an analysis associated with the mobile communications device;

generating, by the policy management module, a policy for the mobile communications device based on the first set of personal data associated with the mobile communications device and based on the analysis received from the server, the generated policy for identifying a second set of personal data stored on the mobile communications device and for controlling access to the second set of personal data;

assigning, by the policy management module, the policy to the mobile communications device;

monitoring, by the policy management module, the second set of personal data stored on the mobile communications device based on the generated policy; and

detecting, by the policy management module, a request for access to the monitored data by an application that is executed on the mobile communications device.

9. The method of claim 8, wherein the analysis received from the server is at least partly based on a presence of at least one application installed on the mobile communications device.

10. The method of claim 9, wherein the analysis received from the server is further at least partly based on known access to the monitored data performed by the at least one application installed on the mobile communications device.

11. The method of claim 8, wherein the identified first set of personal data includes at least one of a contacts database, email database, a database containing communications received or transmitted by the mobile communications device, location information of the mobile communications device, or recently used network names.

12. The method of claim 8, wherein the step of detecting the request for access to the monitored data includes determining if the requested access would result in a transmission of at least part of the monitored data from the mobile communications device.

13. The method of claim 8,

further comprising monitoring, by the policy management module, the first set of personal data associated with the mobile communications device based on the policy.

14. The method of claim 8, wherein, when the application is associated with a container wrapper, the step of detecting the request for access to the monitored data is based on the application interacting with an interface of the container wrapper.

15. A method comprising:

identifying, by a policy management module on a mobile communications device, a first set of personal data stored on the mobile communications device;

generating, by the policy management module, a policy based on the identified first set of personal data stored on the mobile communications device, the generated policy for identifying a second set of personal data stored on the mobile communications device and for controlling access to the second set of personal data;

identifying, by the policy management module, the second set of personal data stored on the mobile communications device based on the generated policy, wherein the second set of personal data includes the identified first set of personal data and additional personal data;

monitoring the second set of personal data stored on the mobile communications device based on the generated policy; and

detecting a request for access to the monitored second set of personal data by at least one application executed on the mobile communications device.

16. The method of claim 15, wherein the identified first set of personal data is associated with at least one of a contacts database, email database, a database containing communications received or transmitted by the mobile communications device, location information of the mobile communications device, or recently used network names.

17. The method of claim 15, wherein the step of detecting the request for access to the monitored second set of personal data includes determining if the access resulted in a transmission of at least a part of the second set of personal data from the mobile communications device.

18. The method of claim 15, wherein, when the at least one application is associated with a container wrapper, the step of detecting the request for access to the monitored second set of personal data is based on the at least one application interacting with an interface of the container wrapper.

19. The method of claim 18, wherein, when the monitored second set of personal data is associated with a container wrapper, the step of detecting the request for access to the monitored second set of personal data is based on the at least one application interacting with an interface of the container wrapper.

20. The method of claim 15, further comprising:

displaying a notification of the detecting of the request for access to the second set of personal data, the notification identifying the application requesting access to the second set of personal data and presenting an option to allow the access or not allow the access.

Patent Citations (356)

Patent	Date	Inventor	Cited By
US3416032(A)	1968-12-01	Jahns et al.	Applicant
US4553257(A)	1985-11-01	Mori et al.	Applicant
US5319776(A)	1994-06-01	Hile et al.	Applicant
US5574775(A)	1996-11-01	Miller, II et al.	Applicant
US5715518(A)	1998-02-01	Barrere et al.	Applicant
US6185689(B1)	2001-02-01	Todd et al.	Applicant
US6269456(B1)	2001-07-01	Hodges et al.	Applicant
US6272353(B1)	2001-08-01	Dicker et al.	Applicant
US6301668(B1)	2001-10-01	Gleichauf et al.	Applicant
US6453345(B2)	2002-09-01	Trcka et al.	Applicant
US6529143(B2)	2003-03-01	Mikkola et al.	Applicant
US6696941(B2)	2004-02-01	Baker	Applicant
US6792543(B2)	2004-09-01	Pak et al.	Applicant
US6892225(B1)	2005-05-01	Tu et al.	Applicant
US6907530(B2)	2005-06-01	Wang	Applicant
US6959184(B1)	2005-10-01	Byers et al.	Applicant
US7020895(B2)	2006-03-01	Albrecht	Applicant
US7023383(B2)	2006-04-01	Stilp et al.	Applicant
US7069589(B2)	2006-06-01	Schmall et al.	Applicant
US7096368(B2)	2006-08-01	Kouznetsov et al.	Applicant
US7123933(B2)	2006-10-01	Poor et al.	Applicant
US7127455(B2)	2006-10-01	Carson et al.	Applicant
US7159036(B2)	2007-01-01	Hinchliffe et al.	Applicant
US7159237(B2)	2007-01-01	Schneier et al.	Applicant
US7171690(B2)	2007-01-01	Kouznetsov et al.	Applicant
US7178166(B1)	2007-02-01	Taylor et al.	Applicant
US7181252(B2)	2007-02-01	Komsi	Applicant
US7210168(B2)	2007-04-01	Hursey et al.	Applicant
US7228566(B2)	2007-06-01	Caceres et al.	Applicant
US7236598(B2)	2007-06-01	Sheymov et al.	Applicant
US7237264(B1)	2007-06-01	Graham et al.	Applicant
US7266810(B2)	2007-09-01	Karkare et al.	Applicant
US7290276(B2)	2007-10-01	Ogata	Applicant
US7304570(B2)	2007-12-01	Thomas et al.	Applicant
US7305245(B2)	2007-12-01	Alizadeh-Shabdiz	Applicant
US7308256(B2)	2007-12-01	Morota et al.	Applicant
US7308712(B2)	2007-12-01	Banzhof	Applicant
US7325249(B2)	2008-01-01	Sutton et al.	Applicant
US7346605(B1)	2008-03-01	Hepworth	Applicant
US7356835(B2)	2008-04-01	Gancarcik et al.	Applicant
US7376969(B1)	2008-05-01	Njemanze et al.	Applicant
US7386297(B2)	2008-06-01	An	Applicant
US7392043(B2)	2008-06-01	Kouznetsov et al.	Applicant
US7392543(B2)	2008-06-01	Szor	Applicant
US7397424(B2)	2008-07-01	Houri	Applicant
US7397434(B2)	2008-07-01	Mun et al.	Applicant
US7401359(B2)	2008-07-01	Gartside et al.	Applicant
US7403762(B2)	2008-07-01	Morgan et al.	Applicant
US7414988(B2)	2008-08-01	Jones et al.	Applicant
US7415270(B2)	2008-08-01	Wilhelmsson et al.	Applicant
US7415536(B2)	2008-08-01	Nakazawa	Applicant
US7433694(B2)	2008-10-01	Morgan et al.	Applicant
US7437158(B2)	2008-10-01	Russell	Applicant
US7467206(B2)	2008-12-01	Moore et al.	Applicant
US7471954(B2)	2008-12-01	Brachet et al.	Applicant
US7472422(B1)	2008-12-01	Agbabian	Applicant
US7474897(B2)	2009-01-01	Morgan et al.	Applicant
US7493127(B2)	2009-02-01	Morgan et al.	Applicant
US7493403(B2)	2009-02-01	Shull	Applicant
US7502620(B2)	2009-03-01	Morgan et al.	Applicant
US7515578(B2)	2009-04-01	Alizadeh-Shabdiz	Applicant
US7525541(B2)	2009-04-01	Chun et al.	Applicant
US7526297(B1)	2009-04-01	Holur et al.	Applicant
US7539882(B2)	2009-05-01	Jessup et al.	Applicant
US7551579(B2)	2009-06-01	Alizadeh-Shabdiz	Applicant
US7551929(B2)	2009-06-01	Alizadeh-Shabdiz	Applicant
US7568220(B2)	2009-07-01	Burshan	Applicant
US7634800(B2)	2009-12-01	Ide et al.	Applicant
US7685132(B2)	2010-03-01	Hyman	Applicant
US7696923(B2)	2010-04-01	Houri	Applicant
US7761583(B2)	2010-07-01	Shull	Applicant
US7768963(B2)	2010-08-01	Alizadeh-Shabdiz	Applicant
US7769396(B2)	2010-08-01	Alizadeh-Shabdiz et al.	Applicant
US7774637(B1)	2010-08-01	Beddoe et al.	Applicant
US7783281(B1)	2010-08-01	Cook et al.	Applicant
US7809353(B2)	2010-10-01	Brown et al.	Applicant
US7809366(B2)	2010-10-01	Rao et al.	Applicant
US7809936(B2)	2010-10-01	Einloth et al.	Applicant
US7813745(B2)	2010-10-01	Li	Applicant
US7818017(B2)	2010-10-01	Alizadeh-Shabdiz et al.	Applicant
US7835754(B2)	2010-11-01	Alizadeh-Shabdiz et al.	Applicant
US7856234(B2)	2010-12-01	Alizadeh-Shabdiz et al.	Applicant
US7856373(B2)	2010-12-01	Ullah	Applicant
US7861303(B2)	2010-12-01	Kouznetsov et al.	Applicant
US7877784(B2)	2011-01-01	Chow	Applicant
US7882247(B2)	2011-02-01	Sturniolo et al.	Applicant
US7882557(B2)	2011-02-01	Coskun et al.	Applicant
US7907966(B1)	2011-03-01	Mammen	Applicant
US7916661(B2)	2011-03-01	Alizadeh-Shabdiz et al.	Applicant
US7978691(B1)	2011-07-01	Cole	Applicant
US7991854(B2)	2011-08-01	Bahl	Applicant
US7999742(B2)	2011-08-01	Alizadeh-Shabdiz et al.	Applicant
US8001610(B1)	2011-08-01	Chickering et al.	Applicant
US8014788(B2)	2011-09-01	Alizadeh-Shabdiz et al.	Applicant
US8019357(B2)	2011-09-01	Alizadeh-Shabdiz et al.	Applicant
US8031657(B2)	2011-10-01	Jones et al.	Applicant
US8037203(B2)	2011-10-01	Accapadi et al.	Applicant
US8054219(B2)	2011-11-01	Alizadeh-Shabdiz	Applicant
US8087082(B2)	2011-12-01	Bloch et al.	Applicant
US8089398(B2)	2012-01-01	Alizadeh-Shabdiz	Applicant
US8089399(B2)	2012-01-01	Alizadeh-Shabdiz	Applicant
US8090386(B2)	2012-01-01	Alizadeh-Shabdiz	Applicant
US8095172(B1)	2012-01-01	Cole et al.	Applicant
US8099764(B2)	2012-01-01	Herzog et al.	Applicant
US8108555(B2)	2012-01-01	Awadallah et al.	Applicant
US8112797(B2)	2012-02-01	Coskun et al.	Applicant
US8121617(B1)	2012-02-01	LaGrotta et al.	Applicant
US8126456(B2)	2012-02-01	Lotter et al.	Applicant
US8127158(B2)	2012-02-01	Jessup et al.	Applicant
US8127350(B2)	2012-02-01	Wei et al.	Applicant
US8127358(B1)	2012-02-01	Lee	Applicant
US8135395(B2)	2012-03-01	Cassett et al.	Applicant
US8195196(B2)	2012-06-01	Haran et al.	Applicant
US8200773(B2)	2012-06-01	Bluestone et al.	Applicant
US8214910(B1)	2012-07-01	Gossweiler et al.	Applicant
US8259568(B2)	2012-09-01	Laudermilch et al.	Applicant
US8261351(B1)	2012-09-01	Thornewell et al.	Applicant
US8266288(B2)	2012-09-01	Banerjee et al.	Applicant
US8266324(B2)	2012-09-01	Baratakke et al.	Applicant
US8346860(B2)	2013-01-01	Berg et al.	Applicant
US8356080(B2)	2013-01-01	Luna et al.	Applicant
US8364785(B2)	2013-01-01	Plamondon	Applicant
US8370580(B2)	2013-02-01	Mobarak et al.	Applicant
US8370933(B1)	2013-02-01	Buckler	Applicant
US8401521(B2)	2013-03-01	Bennett et al.	Applicant
US8447856(B2)	2013-05-01	Drako	Applicant
US8463915(B1)	2013-06-01	Kim	Applicant
US8464335(B1)	2013-06-01	Sinha et al.	Applicant
US8484332(B2)	2013-07-01	Bush et al.	Applicant
US8504775(B2)	2013-08-01	Plamondon	Applicant
US8544060(B1)	2013-09-01	Khetawat	Examiner
US8806647(B1)	2014-08-01	Daswani et al.	Applicant
US8806657(B2)	2014-08-01	Daswani et al.	Applicant
US2001/0044339(A1)	2001-11-01	Cordero et al.	Applicant
US2002/0042886(A1)	2002-04-01	Lahti et al.	Applicant
US2002/0087483(A1)	2002-07-01	Harif	Applicant
US2002/0108058(A1)	2002-08-01	Iwamura	Applicant
US2002/0183060(A1)	2002-12-01	Ko et al.	Applicant
US2002/0191018(A1)	2002-12-01	Broussard	Applicant
US2003/0028803(A1)	2003-02-01	Bunker et al.	Applicant
US2003/0046134(A1)	2003-03-01	Frolick et al.	Applicant
US2003/0079145(A1)	2003-04-01	Kouznetsov et al.	Applicant
US2003/0115485(A1)	2003-06-01	Milliken et al.	Applicant
US2003/0120951(A1)	2003-06-01	Gartside et al.	Applicant
US2003/0131148(A1)	2003-07-01	Kelley et al.	Applicant
US2004/0022258(A1)	2004-02-01	Tsukada et al.	Applicant
US2004/0025042(A1)	2004-02-01	Kouznetsov et al.	Applicant
US2004/0058644(A1)	2004-03-01	Saigo et al.	Applicant
US2004/0133624(A1)	2004-07-01	Park	Applicant
US2004/0158741(A1)	2004-08-01	Schneider	Applicant
US2004/0185900(A1)	2004-09-01	McElveen	Applicant
US2004/0199665(A1)	2004-10-01	Omar et al.	Applicant
US2004/0209608(A1)	2004-10-01	Kouznetsov et al.	Applicant
US2004/0225887(A1)	2004-11-01	O'Neil et al.	Applicant
US2004/0259532(A1)	2004-12-01	Isomaki et al.	Applicant
US2005/0010821(A1)	2005-01-01	Cooper et al.	Applicant
US2005/0015443(A1)	2005-01-01	Levine et al.	Applicant
US2005/0074106(A1)	2005-04-01	Orlamunder et al.	Applicant
US2005/0076246(A1)	2005-04-01	Singhal	Applicant
US2005/0091272(A1)	2005-04-01	Smith	Examiner
US2005/0091308(A1)	2005-04-01	Bookman et al.	Applicant
US2005/0125779(A1)	2005-06-01	Kelley et al.	Applicant
US2005/0130627(A1)	2005-06-01	Calmels et al.	Applicant
US2005/0138395(A1)	2005-06-01	Benco et al.	Applicant
US2005/0138413(A1)	2005-06-01	Lippmann et al.	Applicant
US2005/0138450(A1)	2005-06-01	Hsieh	Applicant
US2005/0154796(A1)	2005-07-01	Forsyth	Applicant
US2005/0186954(A1)	2005-08-01	Kenney	Applicant
US2005/0197099(A1)	2005-09-01	Nehushtan	Applicant
US2005/0221800(A1)	2005-10-01	Jackson et al.	Applicant
US2005/0227669(A1)	2005-10-01	Haparnas	Applicant
US2005/0237970(A1)	2005-10-01	Inoue	Applicant
US2005/0240999(A1)	2005-10-01	Rubin et al.	Applicant
US2005/0254654(A1)	2005-11-01	Rockwell et al.	Applicant
US2005/0278777(A1)	2005-12-01	Loza	Applicant
US2005/0282533(A1)	2005-12-01	Draluk et al.	Applicant
US2006/0026283(A1)	2006-02-01	Trueba	Applicant
US2006/0073820(A1)	2006-04-01	Craswell et al.	Applicant
US2006/0075388(A1)	2006-04-01	Kelley et al.	Applicant
US2006/0080680(A1)	2006-04-01	Anwar et al.	Applicant
US2006/0095454(A1)	2006-05-01	Shankar et al.	Applicant
US2006/0101518(A1)	2006-05-01	Schumaker et al.	Applicant
US2006/0130145(A1)	2006-06-01	Choi et al.	Applicant
US2006/0150238(A1)	2006-07-01	D'Agostino	Applicant
US2006/0150256(A1)	2006-07-01	Fanton et al.	Applicant
US2006/0179485(A1)	2006-08-01	Longsine et al.	Applicant
US2006/0217115(A1)	2006-09-01	Cassett et al.	Applicant
US2006/0218482(A1)	2006-09-01	Ralston et al.	Applicant
US2006/0224742(A1)	2006-10-01	Shahbazi	Applicant
US2006/0236325(A1)	2006-10-01	Rao et al.	Applicant
US2006/0253205(A1)	2006-11-01	Gardiner	Applicant
US2006/0253584(A1)	2006-11-01	Dixon et al.	Applicant
US2006/0272011(A1)	2006-11-01	Ide et al.	Applicant
US2006/0277408(A1)	2006-12-01	Bhat et al.	Applicant
US2006/0294582(A1)	2006-12-01	Linsley-Hood et al.	Applicant
US2007/0005327(A1)	2007-01-01	Ferris	Applicant
US2007/0011319(A1)	2007-01-01	Mcclure et al.	Applicant
US2007/0015519(A1)	2007-01-01	Casey	Applicant
US2007/0016953(A1)	2007-01-01	Morris et al.	Applicant
US2007/0016955(A1)	2007-01-01	Goldberg et al.	Applicant
US2007/0021112(A1)	2007-01-01	Bryne et al.	Applicant
US2007/0028095(A1)	2007-02-01	Allen et al.	Applicant
US2007/0028303(A1)	2007-02-01	Brennan	Applicant
US2007/0028304(A1)	2007-02-01	Brennan	Applicant
US2007/0038677(A1)	2007-02-01	Reasor et al.	Applicant
US2007/0050471(A1)	2007-03-01	Patel et al.	Applicant
US2007/0086476(A1)	2007-04-01	Iglesias et al.	Applicant
US2007/0089165(A1)	2007-04-01	Wei et al.	Applicant
US2007/0090954(A1)	2007-04-01	Mahaffey	Applicant
US2007/0154014(A1)	2007-07-01	Aissi et al.	Applicant
US2007/0174472(A1)	2007-07-01	Kulakowski	Applicant
US2007/0174490(A1)	2007-07-01	Choi et al.	Applicant
US2007/0186275(A1)	2007-08-01	Shahbazi	Applicant
US2007/0186282(A1)	2007-08-01	Jenkins	Applicant
US2007/0190995(A1)	2007-08-01	Wang et al.	Applicant
US2007/0214245(A1)	2007-09-01	Hamalainen et al.	Applicant
US2007/0214504(A1)	2007-09-01	Comparetti et al.	Applicant
US2007/0220608(A1)	2007-09-01	Lahti et al.	Applicant
US2007/0240127(A1)	2007-10-01	Tuvell et al.	Applicant
US2007/0240218(A1)	2007-10-01	Tuvell et al.	Applicant
US2007/0240221(A1)	2007-10-01	Tuvell et al.	Applicant
US2007/0240222(A1)	2007-10-01	Tuvell et al.	Applicant
US2007/0248047(A1)	2007-10-01	Shorty et al.	Applicant
US2007/0250627(A1)	2007-10-01	May et al.	Applicant
US2007/0253377(A1)	2007-11-01	Janneteau et al.	Applicant
US2007/0293263(A1)	2007-12-01	Eslambolchi et al.	Applicant
US2007/0297610(A1)	2007-12-01	Chen et al.	Applicant
US2008/0028470(A1)	2008-01-01	Reminington et al.	Applicant
US2008/0046369(A1)	2008-02-01	Wood	Applicant
US2008/0046557(A1)	2008-02-01	Cheng	Applicant
US2008/0047007(A1)	2008-02-01	Satkunanathan et al.	Applicant
US2008/0049653(A1)	2008-02-01	Demirhan et al.	Applicant
US2008/0065507(A1)	2008-03-01	Morrison et al.	Applicant
US2008/0070495(A1)	2008-03-01	Stricklen et al.	Applicant
US2008/0072329(A1)	2008-03-01	Herschaft et al.	Applicant
US2008/0086638(A1)	2008-04-01	Mather	Applicant
US2008/0086773(A1)	2008-04-01	Tuvell et al.	Applicant
US2008/0086776(A1)	2008-04-01	Tuvell et al.	Applicant
US2008/0109871(A1)	2008-05-01	Jacobs	Applicant
US2008/0127171(A1)	2008-05-01	Tarassov	Applicant
US2008/0127179(A1)	2008-05-01	Moss et al.	Applicant
US2008/0127334(A1)	2008-05-01	Gassoway	Applicant
US2008/0127336(A1)	2008-05-01	Sun et al.	Applicant
US2008/0132218(A1)	2008-06-01	Samson et al.	Applicant
US2008/0134281(A1)	2008-06-01	Shinde et al.	Applicant
US2008/0140767(A1)	2008-06-01	Rao et al.	Applicant
US2008/0148381(A1)	2008-06-01	Aaron	Applicant
US2008/0172746(A1)	2008-07-01	Lotter et al.	Applicant
US2008/0178294(A1)	2008-07-01	Hu et al.	Applicant
US2008/0181116(A1)	2008-07-01	Kavanaugh et al.	Applicant
US2008/0186162(A1)	2008-08-01	Rajan et al.	Applicant
US2008/0196104(A1)	2008-08-01	Tuvell et al.	Applicant
US2008/0200160(A1)	2008-08-01	Fitzpatrick et al.	Applicant
US2008/0208950(A1)	2008-08-01	Kim et al.	Applicant
US2008/0209557(A1)	2008-08-01	Herley et al.	Applicant
US2008/0235801(A1)	2008-09-01	Soderberg et al.	Applicant
US2008/0275992(A1)	2008-11-01	Basty et al.	Applicant
US2008/0276111(A1)	2008-11-01	Jacoby et al.	Applicant
US2008/0293396(A1)	2008-11-01	Barnes et al.	Applicant
US2008/0307243(A1)	2008-12-01	Lee	Applicant
US2008/0318562(A1)	2008-12-01	Featherstone et al.	Applicant
US2009/0064330(A1)	2009-03-01	Shraim	Applicant
US2009/0070283(A1)	2009-03-01	Kang et al.	Applicant
US2009/0119143(A1)	2009-05-01	Silver	Applicant
US2009/0172227(A1)	2009-07-01	Taylor et al.	Applicant
US2009/0199298(A1)	2009-08-01	Miliefsky	Applicant
US2009/0205016(A1)	2009-08-01	Milas	Applicant
US2009/0205047(A1)	2009-08-01	Podjarny	Applicant
US2009/0248623(A1)	2009-10-01	Adelman et al.	Applicant
US2009/0292487(A1)	2009-11-01	Duncan et al.	Applicant
US2009/0293125(A1)	2009-11-01	Szor	Applicant
US2010/0019731(A1)	2010-01-01	Connolly et al.	Applicant
US2010/0064341(A1)	2010-03-01	Aldera	Applicant
US2010/0088398(A1)	2010-04-01	Plamondon	Applicant
US2010/0097494(A1)	2010-04-01	Gum et al.	Applicant
US2010/0100591(A1)	2010-04-01	Burgess et al.	Applicant
US2010/0100939(A1)	2010-04-01	Burgess et al.	Applicant
US2010/0100959(A1)	2010-04-01	Mahaffey	Applicant
US2010/0100963(A1)	2010-04-01	Mahaffey et al.	Applicant
US2010/0100964(A1)	2010-04-01	Burgess et al.	Applicant
US2010/0138501(A1)	2010-06-01	Clinton et al.	Applicant
US2010/0154032(A1)	2010-06-01	Ollmann	Applicant
US2010/0173658(A1)	2010-07-01	Fan et al.	Applicant
US2010/0210240(A1)	2010-08-01	Mahaffey et al.	Applicant
US2010/0240419(A1)	2010-09-01	Horino	Applicant
US2010/0041946(A1)	2010-12-01	Anderson et al.	Applicant
US2010/0313270(A1)	2010-12-01	Kim et al.	Applicant
US2010/0317324(A1)	2010-12-01	Brown et al.	Applicant
US2010/0332593(A1)	2010-12-01	Barash et al.	Applicant
US2011/0047033(A1)	2011-02-01	Mahaffey et al.	Applicant
US2011/0047594(A1)	2011-02-01	Mahaffey et al.	Applicant
US2011/0047597(A1)	2011-02-01	Barton et al.	Applicant
US2011/0047620(A1)	2011-02-01	Mahaffey et al.	Applicant
US2011/0107414(A1)	2011-05-01	Diab et al.	Applicant
US2011/0119765(A1)	2011-05-01	Burgess et al.	Applicant
US2011/0145920(A1)	2011-06-01	Burgess et al.	Applicant
US2011/0171923(A1)	2011-07-01	Daly et al.	Applicant
US2011/0235624(A1)	2011-09-01	Scott et al.	Applicant
US2011/0241872(A1)	2011-10-01	Mahaffey	Applicant
US2011/0296510(A1)	2011-12-01	Hatlelid et al.	Applicant
US2012/0042382(A1)	2012-02-01	Mahaffey	Applicant
US2012/0060222(A1)	2012-03-01	Burgess et al.	Applicant
US2012/0066745(A1)	2012-03-01	Wuthnow	Examiner
US2012/0072569(A1)	2012-03-01	Xu	Applicant
US2012/0084836(A1)	2012-04-01	Mahaffey et al.	Applicant
US2012/0084864(A1)	2012-04-01	Burgess et al.	Applicant
US2012/0096555(A1)	2012-04-01	Mahaffey	Applicant
US2012/0110174(A1)	2012-05-01	Mahaffey et al.	Applicant
US2012/0124239(A1)	2012-05-01	Shribman et al.	Applicant
US2012/0159607(A1)	2012-06-01	Wei et al.	Applicant
US2012/0159636(A1)	2012-06-01	Pandya et al.	Applicant
US2012/0173680(A1)	2012-07-01	Coskun et al.	Applicant
US2012/0179801(A1)	2012-07-01	Luna et al.	Applicant
US2012/0179814(A1)	2012-07-01	Swildens et al.	Applicant
US2012/0188064(A1)	2012-07-01	Mahaffey et al.	Applicant
US2012/0196571(A1)	2012-08-01	Grkov et al.	Applicant
US2012/0215938(A1)	2012-08-01	Fletcher et al.	Applicant
US2012/0233674(A1)	2012-09-01	Gladstone et al.	Applicant
US2012/0233695(A1)	2012-09-01	Mahaffey et al.	Applicant
US2012/0240183(A1)	2012-09-01	Sinha	Applicant
US2012/0246499(A1)	2012-09-01	Jessup et al.	Applicant
US2012/0254285(A1)	2012-10-01	Tiger et al.	Applicant
US2012/0259954(A1)	2012-10-01	McCarthy et al.	Applicant
US2012/0278467(A1)	2012-11-01	Schneider	Applicant
US2012/0303735(A1)	2012-11-01	Raciborski et al.	Applicant
US2012/0311659(A1)	2012-12-01	Narain et al.	Applicant
US2012/0317153(A1)	2012-12-01	Parthasarathy et al.	Applicant
US2012/0317233(A1)	2012-12-01	Redpath	Applicant
US2012/0317370(A1)	2012-12-01	Luna	Applicant
US2012/0324076(A1)	2012-12-01	Zerr et al.	Applicant
US2012/0324094(A1)	2012-12-01	Wyatt et al.	Applicant
US2012/0324259(A1)	2012-12-01	Aasheim et al.	Applicant
US2012/0324568(A1)	2012-12-01	Wyatt et al.	Applicant
US2013/0013775(A1)	2013-01-01	Baumback et al.	Applicant
US2013/0019311(A1)	2013-01-01	Swildens et al.	Applicant
US2013/0023209(A1)	2013-01-01	Fisher et al.	Applicant
US2013/0041946(A1)	2013-02-01	Joel et al.	Applicant
US2013/0041974(A1)	2013-02-01	Luna et al.	Applicant
US2013/0047034(A1)	2013-02-01	Salomon et al.	Applicant
US2013/0054796(A1)	2013-02-01	Baumback et al.	Applicant
US2013/0067054(A1)	2013-03-01	Pulleyn et al.	Applicant
US2013/0074142(A1)	2013-03-01	Brennan	Examiner
US2013/0086682(A1)	2013-04-01	Mahaffey et al.	Applicant
US2013/0097710(A1)	2013-04-01	Basavapatna et al.	Applicant
US2013/0111597(A1)	2013-05-01	Gossweiler et al.	Applicant
US2013/0290388(A1)	2013-10-01	Lenox	Examiner
US2014/0289807(A1)	2014-09-01	Collado	Examiner
GB2430588	2007-03-01		Applicant
WO2005101789	2005-10-01		Applicant
WO2006110181	2006-10-01		Applicant
WO2007081356	2007-07-01		Applicant
WO2008007111	2008-01-01		Applicant
WO2008057737	2008-05-01		Applicant
WO2010048218	2010-04-01		Applicant
WO2010048220	2010-04-01		Applicant
WO2012027588	2012-01-01		Applicant

Non-Patent Literature (102)

Ouellet, Eric. “Magic Quadrant for Content-Aware Data Loss Prevention.” Gartner, Inc. Jan. 3, 2013; downloaded from http://www.gartner.com/technology/reprints.do?id=1-1DGFP7T&ct=1.Applicant
“Five DLP Tips from Security Executives.” Symantec Corporation. Downloaded from http://resources.idgenterprise.com/original/AST-0079952—SymantecFINAL.pdf on Dec. 4, 2013.Applicant
“Discover, monitor and protect your confidential data.” Synmantec Data Loss Prevention. Posted on Nov. 22, 2013 at http://www.symantec.com/data-loss-prevention.Applicant
“What's New in Symantec Data Loss Prevention 12.” Data Sheet: Data Loss Prevention. Symantec. May 2013.Applicant
“Data Leak Prevention.” Symantec Data Loss Prevention. Downloaded from http://www.symantec.com/data-leak-prevention on Dec. 4, 2013.Applicant
“Realtime Privacy Monitoring on Smartphones: TaintDroid Build Instructions for Android 4.1.” Dec. 6, 2012. http://appanalysis.org/download.html.Applicant
Enck et al. “TaintDroid: An Information-Flow Tracking System for Realtime Privacy Monitoring on Smartphones.” In Proceedings of OSDI 2010 (Oct. 2010). Downloaded from http://appanalysis.org/tdroid10.pdf.Applicant
“I'm Aza Raskin@aza. I make shiny things. I simplify.”, “Vote! How to Detect the Social Sites Your Visitors Use”, web D page downloaded Nov. 4, 2013 from http://www.ararask.in/blog/postlsocialhistoryjs, pp. 1-83.Applicant
“Preventing attacks on a user's history through CSS: visited selectors”, “How CSS can be used to query a user's browser history”, L. David Baron, Mozilla Corporation, web page downloaded Nov. 4, 2013 from http://dbaron.org/mozilla/visited-privacy, pp. 1-6.Applicant
Software Engineering Institute, Carnegie Mellon; “Securing Your Web Browser”, Dormann et al., web page downloaded Nov. 4, 2013 from http://www.cert.org/tech—tips/securing—browser/, pp. 1-17.Applicant
Content Security Policy 1.0, “W3C Candidate Recommendation Nov. 15, 2012”, web page downloaded Nov. 4, 2013 from http://www.w3.orgITR/CSP/, pp. 1-16.Applicant
Non-Final Office Action dated Apr. 14, 2011 for U.S. Appl. No. 12/255,614, filed Oct. 21, 2008; pp. 1-6.Applicant
Non-Final Office Action dated Apr. 13, 2011 for U.S. Appl. No. 12/255,621, filed Oct. 21, 2008; pp. 1-7.Applicant
Final Office Action dated Feb. 1, 2011 for U.S. Appl. No. 12/255,626, filed Oct. 21, 2008; pp. 1-18.Applicant
Non-Final Office Action dated Mar. 24, 2011 for U.S. Appl. No. 12/255,635, filed Oct. 21, 2008; pp. 1-17.Applicant
Notice of Allowance dated Nov. 3, 2011 for U.S. Appl. No. 12/255,632, filed Oct. 21, 2008; pp. 1-5.Applicant
Non-Final Office Action dated Apr. 13, 2011 for U.S. Appl. No. 12/255,632, filed Oct. 21, 2008; pp. 1-7.Applicant
Non-Final Office Action dated Dec. 26, 2012 for U.S. Appl. No. 13/160,382, filed Jun. 14, 2011; pp. 1-23.Applicant
Virus Total, VT Community, www.virustotal.com/index.html; Dated Dec. 16, 2011; 44 Pages.Applicant
Windows Update, Internet Archive, Way Back Machine, available at <http://web.archive.org/web/20071022193017/http://en.wikipedia.org/wiki/Windows—Update> Retrieved Feb. 23, 2011, 3 pages.Applicant
Sprite Mobile, Sprite Backup, Internet Archive, Way Back Machine, available at http://web.archive.org/web/20080901220103/http://www.spritesoftware.com/?page—id=280, 4 pages, Retrieved Jan. 16, 2013.Applicant
Sprint Nextel, Mobile Locator, Internet Archive, Way Back Machine, available at http://http://web.archive.org/web/20070516134304/http://nextel.com/en/solutions/gps/mobile—locator.shtml, published May 16, 2007.Applicant
PCT International Preliminary Report on Patentability for PCT/US2011/049182; Mailed on Mar. 7, 2013; pp. 1-9.Applicant
“Virgin Media—Phone Lost or Stolen?”, web page downloaded Apr. 11, 2013 from http://www.virginmobile.com/vm/ukCoverage.do?contentId=insurance.howdoi.sm283.Applicant
Jung, Jaeyeon et al. “DNS Performance and the Effectiveness of Caching,” IEEE/ACM Transactions on Networking, vol. 10, Issue 5, Oct. 2002, pp. 589-603.Applicant
Wu, Yi et al. “Performance Analysis of DNS with TTL Value 0 as Location Repository in Mobile Internet,” IEEE Wireless Communications and Networking Conference (WCNC), Mar. 11-15, 2007, pp. 3250-3255.Applicant
Liljeberg, M. et al. “Optimizing World-Wide Web for Weakly Connected Mobile Workstations: An Indirect Approach,” Second Internatioinal Workshop on Services Distributed and Networked Environments, Jun. 5-6, 1995, pp. 132-139.Applicant
Song, Hui and Cao, Guohong. “Cache-Miss-Initiated Prefetch in Mobile Environments,” Dept. of Computer Science and Engineering, The Pennsylvania State University, Computer Communications, vol. 28, Issue 7, May 2, 2005, pp. 741-753.Applicant
“Sprint—Report that your device is lost or stolen”, web page downloaded Apr. 11, 2013 from http://support.sprint.com/support/article/Report—that—your—device—is—lost—or—stolen/case-ba416758-20090629-143222.Applicant
Tedeschi, Bob, “In Choosing a New Phone, Online Research Goes Only So Far”, The New York Times, Oct. 7, 2009; downloaded Jul. 13, 2013 from http://www.nytimes.com/2009/10/08/technology/personaltech/08smat.html?—r=0.Applicant
PCT “International Search Report and Written Opinion of the International Searching Authority for PCT/US2013/027166”, mailed on Jun. 19, 2013; received on Jun. 21, 2013.Applicant
Paul Wilks “Cerberus anti theft—must-have security app to help find Lost or Stolen phone!”, Dated Jun. 11, 2012; http://www.androidtapp.com/cerberus-anti-theft/, Retrieved Mar. 26, 2013; pp. 1-55.Applicant
Kat Orphanides “Successfully retrieved my phone—which had been stolen & sold on—thanks to tracking data supplied by AVAST! when a new SIM was inserted, even after the phone had been rest to factory defaults by the thief,” Google+, https://plus.google.com/103826845404274377007/posts/1xW5cd6DRzf, Retrieved Mar. 25, 2013; pp. 1-2.Applicant
“Avast! Free Mobile Security Antivirus & Anti-Theft App for Android mobile & tablet,” http://www.avast.com/free-mobile-security, Retrieved Mar. 26, 2013; pp. 1-6.Applicant
Yan Matusevich, “Cerberus—Your Phone's Gaurdian Dog—Testing Android Apps—AndroidPit,” www.androidpit.com/en/android/tests/test/392782/Cerberus-Your-Phone-s-Gaurdian-Dog, Retrieved Mar. 26, 2013; pp. 1-7.Applicant
“Cerberus anti theft LSDroid,” https://play.google.com/store/apps/details?id=com.lsdroid.cerberus&hl=en; pp. 1-31.Applicant
Techsplurge “Cerberus is the best Anti-Theft App for Android,” techsplurge.com4703/cerberus-ladies-gentlemen-antitheft-app-android/, Retrieved Mar. 26, 2013; pp. 1-3.Applicant
Alun Taylor “Cerberus—The Register,” Dated Aug. 23, 2011; www.theregister.co.uk/2011/08/23/app—of—the—week—android—/, Retrieved Mar. 26, 2013; pp. 1-5.Applicant
“Remote SMS commands,” http://myboyfriendisageek.com/market/gotya/, Retrieved Mar. 26, 2013; pp. 1-3.Applicant
Artem Russakovskii “Theft Aware 2.0—The Most Ingenious Android Security Solution With the Best Root Integration We've Seen to Date. Really Hands on Review,” Dated Jul. 24, 2011; http://www.androidpolice.com/2010/11/29/theft-aware-2-0-the-most-ingenious-android-security-solution-with-the-best-root-integration-weve-seen-to-date-really-hand, Retrieved Mar. 26, 2013; pp. 1-13.Applicant
Owusu, Emmanuel, et al., “Password Inference using Accelerometers on Smartphones”, HotMobile '12, Feb. 28, 2012.Applicant
“DeviceOrientation Event Specification”, W3C, available at http://dev.w3.org/geo/api/spec-source-orientation, retrieved on Feb. 28, 2013, published on Jun. 13, 2012.Applicant
Cai, Liang et al., “On the Practicality of Motion Based Keystroke Inference Attack”, Trust and Trustworthy Computing Lecture Notes in Computer Science vol. 7344, 2012, pp. 273-290, Jun. 13, 2012.Applicant
Xu, Zhi et al., “TapLogger: Inferring User Inputs on Smartphone Touchscreens Using On-board Motion Sensors”, WISEC '12 Proceedings of the fifth ACM conference on Security and Privacy in Wireless and Mobile Networkspp. 113-124, Apr. 16, 2012.Applicant
Miluzzo, Emiliano et al., “TapPrints: Your Finger Taps Have Fingerprints”, MobiSys '12 Proceedings of the 10th international conference on Mobile systems, applications, and services, pp. 323-336, Jun. 25, 2012.Applicant
Cai, Liang et al., “TouchLogger: Inferring Keystrokes on Touch Screen From Smartphone Motion”, HotSec'11 Proceedings of the 6th USENIX conference on Hot topics in securitypp. 9-9.Applicant
Richardson, Alexis, “Introduction to RabbitMQ”, Google UK, available at http://www.rabbitmq.com/resources/google-tech-talk-final/alexis-google-rabbitmq-talk.pdf, retrieved on Mar. 30, 2012, 33 pages, published on Sep. 25, 2008.Applicant
Fisher, Oliver, “Malware? We Don't Need No Stinking Malware!”, Google, available at http://googlewebmastercentral.blogspot.com/2008/10/malware-we-dont-need-no-stinking.html, retrieved on Mar. 30, 2012, published on Oct. 24, 2008, 11 pages.Applicant
Reardon, Marguerite, “Mobile Phones That Track Your Buddies,” Cnet, available at <http://news.cnet.com/Mobile-phones-that-track-your-buddies/2100-1039—3-6135209.html, retrieved Mar. 30, 2012, published on Nov. 14, 2006, 6 pages.Applicant
Fette, Ian “Understanding Phishing and Malware Protection in Google Chrome,” The Chromium Blog, available at http://blog.chromium.org/2008—11—01—archive.html, retrieved on May 17, 2011, published on Nov. 14, 2008, 6 pages.Applicant
Kincaid, Jason “Urban Airship Brings Easy Push Notifications to Android,” TechCrunch, available at http://techcrunch.com/2010/08/10/urban-airship-brings-easy-push-notifications-to-android/, retrieved on Jun. 16, 2011, published on Aug. 10, 2010, 5 pages.Applicant
Keane, Justin K. “Using the Google Safe Browsing API from PHP,” Mad Irish, Aug. 7, 2009, available at http://www.madirish.net/node/245, retrieved Mar. 30, 2012, published on Aug. 7, 2009, 5 pages.Applicant
Jefferies, Charles P. “Webroot AntiVirus 2010 With Spy Sweeper Review,” Notebook Review, available at http://www.notebookreview.com/default.asp?newsID=5700&review=Webroot+AntiVirus+2010+With+Spy+Sweeper+Review, retrieved on May 18, 2011, published on Jun. 22, 2010, 3 pages.Applicant
“Berry Locator”, available at http://www.mobireport.com/apps/bl/, retrieved on Aug. 10, 2011, published Feb. 8, 2008.Applicant
Wikipedia, “Firefox Browser”, available at http://en.wikipedia .org/wiki/Firefox—browser, retrieved on Aug. 10, 2011, published on Dec. 15, 2005.Applicant
F-Secure, “F-Secure Mobile Security for S60 Users Guide”, pp. 1-34, retrieved on Aug. 10, 2011, published on Jan. 26, 2009.Applicant
Wikipedia, “Java Virtual Machine”, available at http://en.wikipedia.org/wiki/Java—virtual—machine, retrieved on Aug. 10, 2011, published on Dec. 9, 2003.Applicant
Kaspersky “Kaspersky Mobile Security”, available at http://usa.kaspersky.com/products-services/home-computer-security, published on Jan. 1, 2007, retrieved on Oct. 21, 2008.Applicant
“Kaspersky Mobile Security”, Kaspersky Lab 2008, available at http://www.kaspersky.com/kaspersky—mobile—security, retrieved on Sep. 11, 2008, published on Jun. 22, 2010, 3 Pages.Applicant
Symantec, “Symantec Norton Smartphone Security”, available at http://www.symantec.com/norton/smartphone—security, retrieved on Oct. 21, 2008, published on Jan. 1, 2007.Applicant
“PhoneBak PDA Phone Anti-theft software for your PDA phone”, 2007, Bak2u Pte Ltd (Singapore) pp. 1-4.Applicant
“PhoneBak: Mobile Phone Theft Recovery Software”, 2007, Westin Tech.Applicant
Symantec, “Symantec Endpoint Security, Data Sheet and Product Screen Shot”, retrieved on Oct. 21, 2008, published on Jun. 15, 2008.Applicant
Symantec, “Symantec Mobile Security Suite for Windows Mobile, Data Sheet and Product Screen Shot”, available at http://www.symantec.com/norton/smartphone—security, retrieved on Oct. 21, 2008, published on Mar. 1, 2008.Applicant
TippingPoint “TippingPoint Security Management System (SMS)”, available at http://www.tippingpoint.com/products—sms.html, retrieved on Oct. 21, 2008, published on Mar. 31, 2005, 2 pages.Applicant
Summerson, Cameron “5 Android Antivirus Apps Compared, Find Out Which Ones Are Worth Having!,” Android Headlines, available at http://androidheadlines.com/2011/03/5-android-antivirus-apps-comapred-find-out-which-ones-are-worth-having.html, retrieved on Mar. 30, 2012, published on Mar. 8, 2011, 9 pages.Applicant
“Android Cloud to Device Messaging Framework,” Google Code Labs, available at http://code.google.com/android/c2dm/, retrieved on Sep. 14, 2011, published on Apr. 11, 2011, 9 pages.Applicant
“BlackBerry Push Service Overview,” available at http://us.blackberry.com/developers/platform/pushapi.jsp#tab—tab—resources, retrieved on Sep. 14, 2011, published on Nov. 6, 2010, 21 pages.Applicant
“eSoft unveils SiteFilter 3.0 for OEMs,” Infosecurity, Mar. 23, 2010, available at http://www.infosecurity-magazine.com/view/8273/esoft-unveils-sitefilter-30-for-oems/, retrieved on Mar. 30, 2012, published on Mar. 23, 2010, 2 pages.Applicant
“Get the Physical Location of Wireless Router From its MAC Address (BSSID),” Coderrr, available at http://coderrr.wordpress.com/2008/09/10/get-the-physical-location-of-wireless-router-from-its-mac-address-bssid/, retrieved on Mar. 30, 2012, published on Sep. 12, 2008, 13 pages.Applicant
“Hooking—Wikipedia, the Free Encyclopedia,” Wikipedia, available at http://web.archive.org/web/20100415154752/http://en.wikipedia.org/wiki/Hooking, retrieved Mar. 30, 2012, published on Apr. 15, 2010, 6 pages.Applicant
Mytton, David “How to Build an Apple Push Notification Provider Server (Tutorial),” Server Density, available at http://blog.serverdensity.com/2009/07/10/how-to-build-an-apple-push-notification-provider-server-tutorial/, retrieved on Apr. 2, 2012, published on Jul. 10, 2009, 33 pages.Applicant
“Pidgin the Universal Chat Client,” Pidign, available at http://www.pidgin.im/, retrieved Sep. 14, 2011, published on May 1, 2007, 14 pages.Applicant
Pogue, David “Simplifying the Lives of Web Users,” The New York Times, available at http://www.nytimes.com/2010/08/19/technology/personaltech/19pogue.html, retrieved May 17, 2011, Published on Aug. 18, 2010, 5 pages.Applicant
“Twilio Cloud Communications Web Service API for Building Voice and SMS Applications,” Twilio, available at http://www.twilio.com, retrieved Sep. 14, 2011, published on Jun. 5, 2008, 12 pages.Applicant
“Understanding Direct Push,” Microsoft, Feb. 18, 2009, available at http://technet.microsoft.com/en-us/library/aa997252(v=exchg.80).aspx, retrieved on Mar. 30, 2012, published on Feb. 18, 2009, 3 pages.Applicant
“Urban Airship: Powering Modern Mobile,” available at http://urbanairship.com/products/, retrieved on Sep. 16, 2011, published on Feb. 19, 2010, 14 pages.Applicant
“zVeloDB URL Database,” zVelo, available at https://zvelo.com/technology/zvelodb-url-database, retrieved Mar. 30, 2012, published on Jan. 21, 2012, 2 pages.Applicant
Amazon.com: Mining the Web Discovering Knowledge from Hypertext Data (9781558607545): Soumen Chakrabarti: Books, Amazon available at http://www.amazon.com/exec/obidos/ASIN/1558607544/, retrieved on Jun. 7, 2012, published on Dec. 13, 2001, pp. 1-7.Applicant
Clickatell, available at http://www.clickatell.com, retrieved Sep. 14, 2011, published on Jan. 18, 2011, 11 pages.Applicant
Dashwire: Manage Your Cell Phone on the Web, News Blog, with Jessica Dolocourt, Oct. 29, 2007, 5:00am PDT <http://news.cnet.com/8301-10784—3-9805657-7.html> retrieved Jun. 15, 2009; pp. 1-3.Applicant
Diligenti, M., et al. Focused Crawling Using Context Graphs:, Proceedings of the 26th VLDB Conference, Cairo, Egypt, pp. 1-8, available at www.vldb.org/conf/2000/P257.pdf, retrieved on Oct. 21, 2008, published on Sep. 10, 2000.Applicant
Grafio “Stay Secure”, available at http://widgets.opera.com/widget/4405/, retrieved Oct. 21, 2008, published on Sep. 29, 2008.Applicant
McAfee, Internet Archive, Way Back Machine, available at <http://web.archive.org/web/20080611095201/www.qualys.com/solutions/vulnerability—management>retrieved Feb. 24, 2011, 1 page.Applicant
HTC “Mobile Wipe Smart Phone Management”, pp. 1-4, published on Dec. 5, 2007, retrieved on Dec. 5, 2007.Applicant
PagerDuty, available at http://www.pagerduty.com, retrieved on Sep. 14, 2011, published on Jun. 6, 2009, 23 pages.Applicant
PCT “International Search Report and Written Opinion of the International Searching Authority for PCT/US2009/061370”, mailed on Dec. 14, 2009.Applicant
PCT “International Search Report and Written Opinion of the International Searching Authority for PCT/US2009/061372”, mailed on Mar. 24, 2010; received on Mar. 29, 2010.Applicant
PCT, “International Search Report and Written Opinion of the International Searching Authority for PCT/US2011/049182”, mailed on Dec. 23, 2011.Applicant
Prey, available at http://preyproject.com/, retrieved Jan. 10, 2012, published on May 16, 2009, 4 pages.Applicant
Qualys, “Executive Dashboard,” Internet Archive, Way back Machine, availble at <http://web.archive.org/web20080507161417/www.qualys.com/products/screens/?screen=Executive + Dashboard>, retrieved Feb. 23, 2011, 1 page.Applicant
Qualys, “Vulnerability Management,” Internet Archive, Way Back Machine, available at <http://web.archive.org/web/20080611095201/www.qualys.com/solutions/vulnerability—management> Retrieved Feb. 24, 2011, 1 page.Applicant
Real world Computing, Jun. 16, 2008 (PC Pro), pp. 1-2.Applicant
Simone, “Playing with ActiveMQ,” Mostly Useless, available at http://www.mostly-useless.com/blog/2007/12/27/playing-with-activemq/, retrieved Mar. 30, 2012, published on Dec. 27, 2007, 6 pages.Applicant
Teh, Joe, “Norton 360 Version 3.0 Review,” Mar. 9, 2009, Available at <http://techielobang-com/blog/2009/03/09/norton-360-version-30-review/> Retrieved Feb. 23, 2011, 12 pages.Applicant
Trillian, available at http://www.trillian.im/, retrieved on Sep. 14, 2011, published on Oct. 11, 2007, 24 pages.Applicant
Lide Zhang et al., “Accurate Online Power Estimation and Automatic Battery Behavior Based Power Model Generation for Smartphones,” Codes + ISSS' 10, Oct. 24-29, 2010, Scottsdale, AZ, USA, copyright 2010 ACM 978-1-60558-905-3/10/10, pp. 105-114.Applicant
Luis Corral et al., “A Method for Characterizing Energy Consumption in Android Smartphones,” GREENS 2013, San Francisco, CA, USA, copyright 2013 IEEE 978-1-4673-6267-2/13, pp. 38-45.Applicant
Radhika Mittal et al., “Empowering Developers to Estimate App Energy Consumption,” MobiCom '12, Aug. 22-26, 2012, Istanbul, Turkey, copyright 2012 ACM 978-1-4503-1159-5/12/08, pp. 317-327.Applicant
Kun Yang et al., “On Effective Offloading Services for Resource-Constrained Mobile Devices Running Heavier Mobile Internet Applications,” IEEE Communications Magazine, Jan. 2008 0163-6804/08, copyright 2008 IEEE, pp. 56-63.Applicant
Narseo Vallina-Rodriguez et al., “ErdOS: Achieving Energy Savings in Mobile OS,” MobiArch'11, Jun. 28, 2011, Bethesda, Maryland, USA, copyright 2011 ACM 978-1-4503-0740-6/11/06, pp. 37-42.Applicant
George H. Forman et al., “The Challenges of Mobile Computing,” Computer, copyright 1994 IEE 0018-9162, pp. 38-47.Applicant

Abstract