Patent Grant
9900325
As computing technology has advanced, many different types of computing devices have become commonplace. Portable computing devices have become increasingly popular, with users sometimes bringing their personal computing devices to the workplace and using their personal computing devices for work. Such use can result in situations in which files for work are stored on the user's personal computing device. While this can be helpful for users, it is not without its problems. One such problem is that companies typically want to maintain some control over their data because it oftentimes includes confidential information. This control, however, can conflict with the desired use and full enjoyment of the computing device by the user.
This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.
In accordance with one or more aspects, whether a file on the computing device, created prior to implementation of a data protection policy, has been written to by a program is detected. Based at least on detecting that the file has been written to by the program, an identifier of the file is added to a file encryption queue. A determination is made whether any programs on the computing device are currently accessing the file, and the file is encrypted based at least on determining that no programs on the computing device are currently accessing the file.
In accordance with one or more aspects, a computing device includes one or more processors, a data store, and one or more computer-readable storage media having stored thereon multiple instructions that, based on execution by the one or more processors, implement an encryption and decryption system that includes an encryption module and an encryption determination module. The encryption module is configured to encrypt a file in the data store, created prior to implementation of a data protection policy on the computing device, based at least on receiving a request from the encryption determination module to encrypt the file. The encryption determination module is configured to detect whether the file in the data store is to be encrypted due to the data protection policy, to communicate to the encryption module to encrypt the file at an appropriate time, and determine the appropriate time using an encrypt on close technique, an encrypt on open technique, an encrypt without exclusive access technique, and an encrypt location technique.
The detailed description is described with reference to the accompanying figures. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The use of the same reference numbers in different instances in the description and the figures may indicate similar or identical items. Entities represented in the figures may be indicative of one or more entities and thus reference may be made interchangeably to single or plural forms of the entities in the discussion.
Passive encryption of organization data is discussed herein. Situations can arise in which data on a computing device is to be protected from access by unauthorized users. Such data is also referred to herein as organization data, and the person or entity desiring to protect the data is referred to herein as an organization. A data protection policy is implemented on the computing device, the data protection policy indicating how the organization data is to be protected. Protection of the organization data includes encrypting the organization data, and allowing the organization data to be decrypted only by particular programs and/or under particular circumstances (as indicated by the data protection policy).
Some organization data can already be stored in files created on the computing device prior to implementation of the data protection policy on the computing device. In such situations, these files already stored on the computing device are encrypted using a passive encryption technique. A passive encryption technique refers to an encryption technique that is designed to encrypt files but operate in a manner such that the encryption interferes little, if any, with the operation of other programs on the computing device. Such an encryption technique operates, for example, in the background or in response to particular conditions being satisfied, rather than stopping all other operation of the program so that data can be encrypted when a data protection policy is applied. The passive encryption technique can include one or more of an encrypt on close technique, an encrypt on open technique, an encrypt without exclusive access technique, and an encrypt location technique.
Generally, the encrypt on close technique refers to a technique in which a file including organization data is encrypted in response to two conditions being satisfied: 1) data is written to the file, and 2) no program (including the program that wrote the organization data to the file) is currently accessing the file. The encrypt on open technique refers to a technique in which a file including organization data is encrypted in response to the file being opened by a program. The encrypt without exclusive access technique refers to a technique in which a file including organization data is encrypted without requiring exclusive access to the file. The encrypt location technique refers to a technique in which files stored in a particular location, such as a particular directory or folder, are encrypted.
Using a passive encryption technique allows the files including organization data to be encrypted and thus protected as desired by the organization, and does so in a way that reduces or eliminates interference with the operation of other programs by the user. Security of the organization data, and thus the computing device storing the organization data, is improved while maintaining usability of the computing device (e.g., reducing performance by a small amount that may not even be noticeable to a user of the computing device).
References are made herein to encryption, decryption, and keys. Encryption and decryption can be performed using symmetric key cryptography as well as public key cryptography with public/private key pairs. Although such key cryptography is well-known to those skilled in the art, a brief overview of such cryptography is included here to assist the reader. In public key cryptography, an entity (such as a user, hardware or software component, a device, a domain, and so forth) has associated with it a public/private key pair. The public key can be made publicly available, but the entity keeps the private key a secret. Without the private key it is computationally very difficult to decrypt data that is encrypted using the public key. So, data can be encrypted by any entity with the public key and only decrypted by an entity with the corresponding private key.
In symmetric key cryptography, on the other hand, a shared key (also referred to as a symmetric key) is known by and kept secret by the two entities. Any entity having the shared key is typically able to decrypt data encrypted with that shared key. Without the shared key it is computationally very difficult to decrypt data that is encrypted with the shared key. So, if two entities both know the shared key, each can encrypt data that can be decrypted by the other, but other entities cannot decrypt the data if the other entities do not know the shared key. Similarly, an entity with a shared key can encrypt data that can be decrypted by that same entity, but other entities cannot decrypt the data if the other entities do not know the shared key.
The computing device 100 includes a data protection system 102, an operating system 104, an enlightened program 106, and an unenlightened program 108. The operating system 104 manages the running of various different programs (including the enlightened program 106 and the unenlightened program 108), manages control of various components or other devices, and so forth. The data protection system 102 facilitates enforcing a data protection policy set by an entity, as discussed in more detail below. Although illustrated separately, it should be noted that the data protection system 102 can be included as part of the operating system 104.
Various different organizations (also referred to herein as entities) can desire to set a data protection policy for organization data on the computing device 100. Such organizations can include, for example, an entity (e.g., company, university or other school, government, etc.) that employs a user of the computing device 100 and that desires to keep various data regarding its operations confidential, a user of the computing device 100 that desires to keep various personal information confidential, and so forth. Organization data refers to data that is associated with an organization and that is managed or controlled by the organization. For example, the organization data can be user-entered data or program data, program instructions, binary code, and so forth.
Generally, a data protection policy identifies how organization data is to be protected. The data protection policy can include various settings or rules identifying various different ways in which the organization data is to be protected, such as restrictions on how the plaintext data (unencrypted data) in files can be used, which programs can access the plaintext data, how to identify which programs can use the plaintext data, dates or times when data can be accessed, configurations or settings that a computing device is to have in order to access the data, and so forth. These settings or rules in the data protection policy are specified by the organization and are whatever settings or rules the organization desires.
Organization data is protected by a particular organization by encrypting the data using one or more keys associated with the organization, and decrypting the data when appropriate using a key associated with the entity. The encryption and decryption can be done by invoking an encryption/decryption component of the computing device 100, which may be implemented for example by the data protection system 102 or the operating system 104. The key associated with a particular organization can be maintained locally at the computing device 100, or alternatively obtained from another device or service. Alternatively, the encryption and/or decryption can be performed by another device or service (e.g., a service trusted by the computing device 100 and accessed over a network).
The computing device 100 also includes a data store 110 that can store organization data 112 and/or data that is not organization data (shown as non-organization data 114). The data store 110 includes one or more data storage devices for the computing device 100, such as Flash memory disks, magnetic disks, optical discs, random access memory (RAM), combinations thereof, and so forth. The data storage devices can be fixed or removable devices, and can be included as part of the computing device 100 or coupled to the computing device 100. The organization data 112 optionally includes both encrypted organization data as well as non-encrypted organization data, or alternatively includes just encrypted organization data or just non-encrypted organization data.
In the discussions herein, organization data 112, as well as non-organization data 114, is oftentimes referred to as being data stored in a file (also referred to as a data file). However, it should be noted that the techniques discussed herein can be used with data stored in other manners. For example, the techniques discussed herein can be used analogously for data stored in records or entries of a database.
Organization data 112 can be distinguished from non-organization data 114 in a variety of different manners. In one or more embodiments, a file has corresponding metadata that is stored as part of the file itself This metadata can include an indication of whether the data is organization data (and optionally which of multiple organizations organization data is associated with), such as an identifier of a data protection policy for the data or an identifier of an organization. Additionally or alternatively, an indication of which data is organization data can be maintained in different manners. For example, an indication of which data is organization can be maintained using a table, list or other record that identifies organization data (and optionally which of multiple organization data that data is associated with). By way of another example, different portions of the data store 110 (e.g., different folders or directories of the data store 110), optionally with different portions being associated with different ones of multiple organizations, can be used for organization data than for non-organization data, so any data stored in a portion of the data store 110 used for organization data is assumed to be organization data.
The data protection system 102 includes an encryption and decryption system 120 as well as an access determination module 122. The encryption and decryption system 120 manages the encryption and decryption of organization data. The organization data is decrypted by the system 120 when accessed by a program that is permitted, based on the data protection policy, to access the organization data. The organization data is encrypted by the system 120 at various different times, such as when the organization data is written to the data store 110, as discussed in more detail below.
The access determination module 122 determines whether a program (such as enlightened program 106 or unenlightened program 108) is permitted to access organization data for an organization. A program that is permitted to access organization data is also referred to as an organization program or an enterprise program. Whether a program is permitted to access organization data can be determined in various manners. In one or more embodiments, the access determination module 122 maintains or has access to a list of programs that are permitted to access organization data (optionally different programs for different organizations). In such embodiments, the access determination module 122 determines the program is permitted to access the organization data if the program is on the list, and otherwise determines the program is not permitted to access the organization data. Additionally or alternatively, the access determination module 122 can determine whether an application is permitted to access the organization data in other manners. For example, various rules, properties, criteria, algorithms, and so forth can be applied to determine whether a program is permitted to access the organization data. Such rules, criteria, algorithms, and so forth can be provided by the organization that sets the data protection policy for the organization data, or alternatively by another entity, component, or module. If a program is permitted to access the organization data, then the encryption and decryption system 120 decrypts the organization data using one or more keys. Otherwise, the encryption and decryption system 120 does not decrypt the organization data, and the program is not able to access the plaintext (unencrypted) organization data.
Programs are referred to herein as being enlightened or unenlightened.
An enlightened program refers to a program that protects data in accordance with the data protection policy for an organization, invoking the functionality of the computing device 100 as appropriate to protect and handle organization data according to the data protection policy for the organization. For example, application programming interface (API) methods exposed by the data protection system 102 can be invoked by the enlightened program 106 to have organization data encrypted and decrypted. The data protection system 102 can allow an enlightened program to access organization data protected by a data protection policy, automatically decrypting the data for the enlightened program and/or decrypting the data in response to a request from the enlightened program, and relying on the enlightened program to have data encrypted as appropriate given the data protection policy.
An unenlightened program refers to a program that does not (or need not) protect data in accordance with the data protection policy for the organization, and lets the data protection system 102 enforce the data protection policy for the organization. For an unenlightened program, the data protection system 102 performs encryption and decryption to maintain the protection on the organization data in accordance with the data protection policy because the data protection system 102 knows that the unenlightened program cannot be relied on to do so. The data protection system 102 decrypts organization data for the unenlightened programs when the organization data is accessed by the unenlightened programs. For example, when data is accessed by the unenlightened program 108, the data protection system 102 is notified (e.g., by the operating system 104), and decrypts the data for the unenlightened program 108.
The data protection system 102 also encrypts data for the unenlightened program 108. This encryption can be performed at different times. For organization data in an already-encrypted file (e.g., a file that was decrypted when accessed by an unenlightened program), the data protection system 102 detects or is notified of the closing of the file by the unenlightened program and encrypts the file at that time. For an already-encrypted file, organization data that is read from the file is decrypted as part of the read operation, but the file remains encrypted and does not need to be re-encrypted when the file is closed. For organization data that is not in an already-encrypted file, the data protection policy 102 determines an appropriate time to encrypt the data using a passive encryption technique. A passive encryption technique refers to an encryption technique that is designed to operate in a manner that interferes little, or any, with the operation of the other programs (e.g., the enlightened program 102 and the unenlightened program 108) on the computing device 100, reducing the performance of other programs on the computing device 100 (e.g., an amount of time that the other programs are scheduled to run, an amount of resources (e.g., processing power or memory) allocated to the other programs) by a small (e.g., less than a threshold amount) amount if at all.
In one or more embodiments, the data protection system 102 supports as a passive encryption technique at least one of an encrypt on close technique, an encrypt on open technique, an encrypt without exclusive access technique, and an encrypt location technique. These different techniques are discussed in more detail below. The data protection system 102 can implement a single one of these techniques, or alternatively can implement two or more of these techniques concurrently. It should be noted that these techniques are used by the data protection system 102 to encrypt files that have been created and stored in the data store 110 prior to the data protection policy being implemented by the data protection system 102 (or prior to the data protection policy indicating that organization data is to be encrypted or protected). For files created after implementation of the data protection policy by the data protection system 102, the data protection system 102 detects or is notified of the creation of file and encrypts the file at the time of creation (or when the file is closed).
The implementation of the data protection policy for organization data refers to the data protection policy for that organization data being activated (e.g., enabled or turned on), such as due to a new data protection policy being provided to the computing device 100, a change in a previous data protection policy (e.g., a change in which programs are organization programs), and so forth.
Encrypting files that have been created and stored in the data store 110 prior to the data protection policy being enforced by the data protection system 102 (or prior to the data protection policy indicating that organization data is to be encrypted or protected) can be challenging in many systems. For example, in situations in which multiple programs can open and access the data in a file concurrently, it can be difficult to encrypt the file.
In process 200, a file that was created prior to implementation of a data protection policy on a computing device and that is to be encrypted due to the data protection policy is detected (act 202). This file is a file that includes organization data. The implementation of the data protection policy can be an initial establishment or beginning enforcement of the data protection policy on the computing device, a change in a previously established or enforced data protection policy on the computing device, and so forth.
Depending on the detection logic that is used, for a given file the data protection system may or may not know whether the file contains organization data. If a file is not known to contain organization data, it is assumed not to contain organization information unless a program known to be an organization program has written data to this file (or, for the encrypt on open technique, opened this file) and/or the source of data being written to the file is known to be an organization source (e.g., a source on an organization network). To summarize, in those cases the decision to encrypt is based on the properties of the program and/or data written to the file rather than properties of the existing file.
An appropriate time to encrypt the file is determined using a passive encryption technique (act 204). The passive encryption technique is designed to reduce or eliminate the impact of the encryption on other programs as discussed above. For example, the passive encryption technique is designed to use a small amount of resources (e.g., processing power, memory) in the computing device and attempt to avoid inconveniently preventing access to the file if encryption requires exclusive access so as not to interfere with other programs in the computing device. These passive encryption techniques include an encrypt on close technique, an encrypt on open technique, an encrypt without exclusive access technique, and an encrypt location technique. These different techniques are discussed in more detail below.
The file is then encrypted at the appropriate time (act 206).
One of the passive encryption techniques is the encrypt on close technique. The encrypt on close technique refers to a technique in which a file including organization data is encrypted by the data protection system 102 in response to two conditions being satisfied: 1) data is written to the file, and 2) no program (including the program that wrote the organization data to the file) is currently accessing the file. The encrypt on close technique reduces the chances of a program running into errors when accessing the file (e.g., due to an attempt to encrypt the file while it is being accessed), and also retains responsiveness of programs (e.g., there is no long delay while other programs wait for all of the files including organization data to be encrypted). The encrypt on close technique can be used, for example, when the design or implementation of the encryption system is such that the encryption system requires exclusive access to a file in order to encrypt the file.
Generally, using the encrypt on close technique, a record is maintained of files that include organization data and that have been written to (and not yet encrypted). Those files are then encrypted at a time when no program is accessing the files. In one or more embodiments, being written to by an organization program is what causes the file to contain organization data, so the file does not necessarily have to initially contain organization data, and if the file does contain organization data, the file does not necessarily need to be written to.
The encryption and decryption system 300 includes an encryption module 302, a decryption module 304, a file encryption queue 306, and an encryption determination module 308. In one or more embodiments, the encryption and decryption system 300 implements the encrypt on close technique passive encryption technique.
The encryption module 302 manages encryption of the file. Any of a variety of encryption techniques can be used by the encryption module 302, and the key used to encrypt the file can be obtained from a variety of different sources as discussed above.
The decryption module 304 manages decryption of the file. Any of a variety of decryption techniques can be used by the decryption module 304, and the key used to decrypt the file can be obtained from a variety of different sources as discussed above. The key used to decrypt the file can be the same key, or alternatively a different key, than is used to encrypt the file.
The file encryption queue 306 is a record of files that have been written to by a program but not yet encrypted. An identifier of an unencrypted file is added to the file encryption queue 306 (also referred to as adding the file to the file encryption queue 306) in response to data being written to the unencrypted file. The identifier can be added to the file encryption queue 306 by the encryption determination module 308 or alternatively another component or module. Which files on the data store 110 are encrypted and which files are unencrypted can be determined in various manners, such as by metadata included as part of the files, by a separate record maintained by the encryption and decryption system 300 or a file system 124 of the operating system 104, and so forth.
It should be noted that programs can freely open files for any access rights and the files are not added to the file encryption queue 306 as long as they are not written to. This prevents users from losing access to their personal data which they might accidentally open in organization programs. If a personal file is modified and saved by the user in an organization program, the encryption and decryption system 300 assumes that the file could potentially have organization data and is to be encrypted.
In one or more embodiments, a separate file encryption queue 306 is maintained for (corresponds to) each user of the computing device 100. Different users can log into the computing device 100, and at any given time the encryption and decryption system 300 encrypts files on the file encryption queue 306 corresponding to the user that is currently logged into the computing device 100, and does not encrypt files on the file encryption queue 306 corresponding to other users of the computing device 100. Alternatively, the encryption and decryption system 300 can encrypt files on the file encryption queues 306 of other users not currently logged into the computing device 100, or a single file encryption queue 306 can be used by the encryption and decryption system 300 for all users of the computing device 100.
The encryption determination module 308 determines when to encrypt files in the file encryption queue 306. The encryption determination module 308 determines that a file in the file encryption queue 306 is to be encrypted if there is no program (including the program that wrote organization data to the file) currently accessing the file. Whether any programs are currently accessing the file can be determined in a variety of different manners.
In one or more embodiments, each file has an identifier referred to as a file handle. The file handle uniquely identifies the file within the computing device 100 regardless or independent of where the file is stored on the computing device 100, and is maintained by the operating system 104. In contrast to a file path name, the file handle remains the same regardless of the location of the file in the data store 110. In order to access a file (e.g., to read from or write to the file), a program opens the file handle for the file. Multiple different programs can have the file handle for the file open concurrently. The encryption determination module 308 determines that no program is accessing a file in response to no programs having the file handle open. Whether (and/or how many) programs have a file handle open for a file can be determined by querying the operating system 104, or the encryption determination module 308 can register with the operating system 104 to receive notification from the operating system 104 when no program has a file handle open to the file.
Alternatively, the encryption determination module 308 can determine when no program has a file open in various other manners. Any technique supported by the operating system 104 for keeping track of which programs are accessing which files can be leveraged by the encryption determination module 308 to determine when no program is accessing a particular file. For example, the encryption determination module 308 could request to exclusively access the file so that only the encryption determination module 308 is accessing the file. If the operating system 104 allows such exclusive access, then the encryption determination module 308 knows that the file is not being accessed by any other programs.
In one or more embodiments, the file handles to the files are the identifiers included in the file encryption queue 306. This allows higher resiliency when managing changes to files in the file encryption queue 306 because the file handle for a file, once created, stays constant across modifications, moves and renames. Alternatively, other file identifiers can be used. For example, file path names that identify where the file is stored in the data store 110 can be used as the identifiers included in the file encryption queue 306.
In one or more embodiments, in response to determining that a file is to be encrypted, the encryption determination module 308 opens the file (e.g., opens a file handle to the file). The encryption determination module 308 communicates an indication of the file handle for the file to the encryption module 302, which in turn encrypts the file. As part of encrypting the file, the encrypted file is written back to the data store 110. Upon completing encrypting the file, the encryption module 302 communicates an indication that the encryption is completed to the encryption determination module 308, which in turn closes the file (e.g., closes the file handle to the file) and removes the identifier of the file from the file encryption queue 306. Any other record keeping used by the encryption and decryption system 300 and/or the operating system 104 to determine which files are encrypted is also updated to reflect that the file is now encrypted.
In one or more embodiments, the encryption module 302 encrypts a temporary file rather than the opened file. The opened file is read, the data contained therein encrypted, and the encrypted data is written to the temporary file. The encryption determination module 308 then replaces the opened file with the temporary file (e.g., by notifying the file system 124 to close the file and replace the file with the temporary file, by overwriting the opened file with the temporary file, etc.). By using a temporary file, the encryption process can be interrupted without adverse consequences. For example, if another program requests to access the file with write access while the file is being encrypted, the file system 124 can notify the encryption and decryption system 300 of the request and the encryption and decryption system 300 can abort the encryption process, delete the temporary file, and (optionally) close the file handle for the file so that the other program can access the file.
Alternatively, the encryption determination module 308 can open the file for exclusive access, and the encryption module 302 can complete encryption of the file regardless of whether other programs are requesting access to the file. Thus, in such situations the encryption and decryption system 300 can effectively block access to the file by other programs while the file is being encrypted.
In one or more embodiments, the file encryption queue 306 is stored in a nonvolatile memory (e.g., Flash memory, magnetic disk, etc.) that is updated each time the file encryption queue 306 changes (e.g., a file is added to the file encryption queue 306 or a file on the file encryption queue 306 is encrypted and the file is removed from the file encryption queue 306). The file encryption queue 306 is stored in a protected or secure location of the nonvolatile memory, preventing unauthorized programs (e.g., programs other than the encryption and decryption system 300) from altering the file encryption queue 306. Storing the file encryption queue 306 in nonvolatile memory helps ensure that, in the event of a power loss or reboot, organization data written by a program is eventually encrypted. The file encryption queue 306 in nonvolatile memory persists across reboots of the computing device 100, allowing encryption of files on the file encryption queue 306 to continue after the computing device 100 is rebooted. File system atomicity functionality can also be leveraged to maintain consistency when accessing the file encryption queue 306. A copy of the file encryption queue 306 can also optionally be stored in a volatile memory (e.g., RAM), which may allow faster access to the file encryption queue 306.
In one or more embodiments, the file encryption queue 306 is accessible only to kernel-mode file system drivers (e.g., which may be included as part of the encryption and decryption system 300 or accessed by the encryption and decryption system 300), and cannot be updated without administrative privileges on the computing device 100. This prevents malicious or infected programs (e.g., which would be running in user-mode rather than kernel-mode, and would not have administrative privileges) from adding rogue entries to the queue with the intention of attacking or overloading the computing device.
As discussed above, the access determination module 122 determines whether a program requesting to access organization data in a file is permitted to access the organization data, and if so the decryption module 304 decrypts the file using one or more keys. In situations in which the file is not yet encrypted but is in the file encryption queue 306, access to the file is denied (e.g., by the access determination module 122) even though the file is not yet encrypted. Thus, the data protection system 102 operates to restrict access to the file only to those permitted to access the file even if the file is not yet encrypted.
Additionally, situations can arise in which organization data is to no longer be accessible on the computing device 100, in which case access to the organization data is removed (also referred to as wiping the files that include organization data or wiping the organization data). The encryption and decryption system 300 can be notified of these situations in different manners, such as by receiving a request from a management service coupled to the computing device 100 (e.g., via the Internet or a local area network) to wipe the organization data from the computing device 100, or by a user choice locally or remotely to opt the computing device 100 out of organization management. The organization data is removed by deleting the key used to decrypt the file, thus effectively removing the ability for a program to retrieve the plaintext (unencrypted) organization data. In situations in which there are multiple users of the computing device 100, each such user has his or her own key. If some but not all of the multiple users are to no longer have access to the organization data, then the keys for those users that are to no longer have access to the organization data are deleted. Thus, the users that are to no longer have access to the organization data will no longer have a key allowing the organization data to be decrypted, but other users that are still allowed to access the organization data will have a key allowing the organization data to be decrypted.
In situations in which files are being wiped, but some files are in the file encryption queue 306, simply deleting the key is insufficient to remove access to the files in the file encryption queue 306 because those files are not yet encrypted. In such situations, the encryption and decryption system 300 deletes the files that are in the file encryption queue 306. This deletion can take various forms, such as having identifiers of the files removed from a file directory maintained by the file system 124, having the files securely deleted (e.g., having the portions of the data store 110 where the files are stored overwritten one or more times with other data), and so forth. As part of the deletion process, the identifiers of the files are also removed from the file encryption queue 306. Thus, those files are wiped from the computing device despite not being encrypted yet.
All files in the file encryption queue 306 can be deleted, or alternatively only some of the files in the file encryption queue 306 can be deleted (e.g., those that include organization data for a particular organization). For example, organization data for two organizations may be stored on the computing device, and a request received to wipe organization data for a first of the two organizations but not a second of the two organizations. In this situation, files in the file encryption queue 306 that include organization data for the first organization are wiped from the computing device, but files in the file encryption queue that include organization data for the second organization are not wiped from the computing device.
In process 400, whether a file that was created prior to implementation of a data protection policy on a computing device has been written to is detected (act 402). The implementation of the data protection policy can be an initial establishment or beginning enforcement of the data protection policy on the computing device, a change in a previously established or enforced data protection policy on the computing device, and so forth. It should be noted that the detection in act 402 is of a file that is or has been written to—a file that is read, but not written to, is not detected in act 402.
An identifier of the file detected in act 402 is added to a file encryption queue (act 404) based at least on detecting that the file is or has been written to. The identifier can be a file handle or other identifier as discussed above.
A determination is subsequently made whether any programs are currently accessing the file (act 406). This determination can be made in a variety of different manners, such as by determining when no programs have an open file handle for the file.
The file is encrypted (act 408) based at least on determining that no programs on the computing device are currently accessing the file. The file can then be treated by the operating system and the data protection system as any other encrypted file that was created after implementation of the data protection policy. In act 408, the file can be exclusively accessed for encryption so that any other programs requesting access to the file are blocked from accessing the file while the file is being encrypted. Alternatively, the encrypting of the file can be aborted in response to a request by another program to access the file. If encrypting of the file is aborted, the identifier of the file remains in the file encryption queue. After the file has been successfully encrypted, the identifier of the file is removed from the encryption queue.
The encrypt on close technique takes a passive approach to encrypting organization data at the cost of delaying encryption for a relatively negligible amount of time. Files are only encrypted when they are actually written to, and only when they are not being accessed by other programs on the computing device. This reduces the chances of a program running into errors when accessing the file and retains responsiveness of applications, while also providing security of the organization data as desired by the data protection policy.
Referring again to
The encrypt on open technique refers to a technique in which a file including organization data is encrypted by the data protection system 102 in response to the file being opened by a program. In one or more embodiments, the encrypt on open technique is implemented using the encryption and decryption system 300 of
The encrypt on open technique maintains protection of organization data in files as desired by the data protection policy, although can reduce the performance and responsiveness of the program accessing the file relative to the encrypt on close technique. Nonetheless, the encrypt on open technique improves security of the organization data, and thus of the computing device 100, and prevents access to a file including organization data regardless of whether the file is being written to. The encrypt on open technique can be used, for example, when the design or implementation of the encryption system is such that the encryption system requires exclusive access to a file in order to encrypt the file.
The encrypt without exclusive access technique refers to a technique in which a file including organization data is encrypted by the data protection system 102 without requiring exclusive access to the file. In one or more embodiments, the encrypt without exclusive access technique is implemented using the encryption and decryption system 300 of
The encrypt without exclusive access technique maintains protection of organization data in files as desired by the data protection policy. Security of the organization data, and thus of the computing device 100, is improved. Furthermore, delays due to waiting for a file to be opened or closed need not be incurred—any file including organization data can be encrypted in response to implementation of the data protection policy regardless of which, if any, programs are accessing the file.
The encrypt location technique refers to a technique in which files stored in a particular location, such as a particular directory or folder, are encrypted. In one or more embodiments, the encrypt location technique is implemented using the encryption and decryption system 300 of
The encrypt location technique maintains protection of organization data in files as desired by the data protection policy. Security of the organization data, and thus of the computing device 100, is improved. Furthermore, delays due to waiting for a file to be opened or closed need not be incurred—any file stored in the particular location is encrypted regardless of when opened or closed by a program on the computing device.
Although particular functionality is discussed herein with reference to particular modules, it should be noted that the functionality of individual modules discussed herein can be separated into multiple modules, and/or at least some functionality of multiple modules can be combined into a single module. Additionally, a particular module discussed herein as performing an action includes that particular module itself performing the action, or alternatively that particular module invoking or otherwise accessing another component or module that performs the action (or performs the action in conjunction with that particular module). Thus, a particular module performing an action includes that particular module itself performing the action and/or another module invoked or otherwise accessed by that particular module performing the action.
The example computing device 502 as illustrated includes a processing system 504, one or more computer-readable media 506, and one or more I/O Interfaces 508 that are communicatively coupled, one to another. Although not shown, the computing device 502 may further include a system bus or other data and command transfer system that couples the various components, one to another. A system bus can include any one or combination of different bus structures, such as a memory bus or memory controller, a peripheral bus, a universal serial bus, and/or a processor or local bus that utilizes any of a variety of bus architectures. A variety of other examples are also contemplated, such as control and data lines.
The processing system 504 is representative of functionality to perform one or more operations using hardware. Accordingly, the processing system 504 is illustrated as including hardware elements 510 that may be configured as processors, functional blocks, and so forth. This may include implementation in hardware as an application specific integrated circuit or other logic device formed using one or more semiconductors. The hardware elements 510 are not limited by the materials from which they are formed or the processing mechanisms employed therein. For example, processors may be comprised of semiconductor(s) and/or transistors (e.g., electronic integrated circuits (ICs)). In such a context, processor-executable instructions may be electronically-executable instructions.
The computer-readable media 506 is illustrated as including memory/storage 512. The memory/storage 512 represents memory/storage capacity associated with one or more computer-readable media. The memory/storage 512 may include volatile media (such as random access memory (RAM)) and/or nonvolatile media (such as read only memory (ROM), Flash memory, optical disks, magnetic disks, and so forth). The memory/storage 512 may include fixed media (e.g., RAM, ROM, a fixed hard drive, and so on) as well as removable media (e.g., Flash memory, a removable hard drive, an optical disc, and so forth). The computer-readable media 506 may be configured in a variety of other ways as further described below.
The one or more input/output interface(s) 508 are representative of functionality to allow a user to enter commands and information to computing device 502, and also allow information to be presented to the user and/or other components or devices using various input/output devices. Examples of input devices include a keyboard, a cursor control device (e.g., a mouse), a microphone (e.g., for voice inputs), a scanner, touch functionality (e.g., capacitive or other sensors that are configured to detect physical touch), a camera (e.g., which may employ visible or non-visible wavelengths such as infrared frequencies to detect movement that does not involve touch as gestures), and so forth. Examples of output devices include a display device (e.g., a monitor or projector), speakers, a printer, a network card, tactile-response device, and so forth. Thus, the computing device 502 may be configured in a variety of ways as further described below to support user interaction.
The computing device 502 also includes an encryption and decryption system 514. The encryption and decryption system 514 provides passive encryption of organization data as discussed above. The encryption and decryption system 514 can implement, for example, the encryption and decryption system 120 of
Various techniques may be described herein in the general context of software, hardware elements, or program modules. Generally, such modules include routines, programs, objects, elements, components, data structures, and so forth that perform particular tasks or implement particular abstract data types. The terms “module,” “functionality,” and “component” as used herein generally represent software, firmware, hardware, or a combination thereof. The features of the techniques described herein are platform-independent, meaning that the techniques may be implemented on a variety of computing platforms having a variety of processors.
An implementation of the described modules and techniques may be stored on or transmitted across some form of computer-readable media. The computer-readable media may include a variety of media that may be accessed by the computing device 502. By way of example, and not limitation, computer-readable media may include “computer-readable storage media” and “computer-readable signal media.”
“Computer-readable storage media” refers to media and/or devices that enable persistent storage of information and/or storage that is tangible, in contrast to mere signal transmission, carrier waves, or signals per se. Thus, computer-readable storage media refers to non-signal bearing media. The computer-readable storage media includes hardware such as volatile and non-volatile, removable and non-removable media and/or storage devices implemented in a method or technology suitable for storage of information such as computer readable instructions, data structures, program modules, logic elements/circuits, or other data. Examples of computer-readable storage media may include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, hard disks, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or other storage device, tangible media, or article of manufacture suitable to store the desired information and which may be accessed by a computer.
“Computer-readable signal media” refers to a signal-bearing medium that is configured to transmit instructions to the hardware of the computing device 502, such as via a network. Signal media typically may embody computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as carrier waves, data signals, or other transport mechanism. Signal media also include any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media include wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared, and other wireless media.
As previously described, the hardware elements 510 and computer-readable media 506 are representative of instructions, modules, programmable device logic and/or fixed device logic implemented in a hardware form that may be employed in some embodiments to implement at least some aspects of the techniques described herein. Hardware elements may include components of an integrated circuit or on-chip system, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), a complex programmable logic device (CPLD), and other implementations in silicon or other hardware devices. In this context, a hardware element may operate as a processing device that performs program tasks defined by instructions, modules, and/or logic embodied by the hardware element as well as a hardware device utilized to store instructions for execution, e.g., the computer-readable storage media described previously.
Combinations of the foregoing may also be employed to implement various techniques and modules described herein. Accordingly, software, hardware, or program modules and other program modules may be implemented as one or more instructions and/or logic embodied on some form of computer-readable storage media and/or by one or more hardware elements 510. The computing device 502 may be configured to implement particular instructions and/or functions corresponding to the software and/or hardware modules. Accordingly, implementation of modules as a module that is executable by the computing device 502 as software may be achieved at least partially in hardware, e.g., through use of computer-readable storage media and/or hardware elements 510 of the processing system. The instructions and/or functions may be executable/operable by one or more articles of manufacture (for example, one or more computing devices 502 and/or processing systems 504) to implement techniques, modules, and examples described herein.
As further illustrated in
In the example system 500, multiple devices are interconnected through a central computing device. The central computing device may be local to the multiple devices or may be located remotely from the multiple devices. In one or more embodiments, the central computing device may be a cloud of one or more server computers that are connected to the multiple devices through a network, the Internet, or other data communication link.
In one or more embodiments, this interconnection architecture enables functionality to be delivered across multiple devices to provide a common and seamless experience to a user of the multiple devices. Each of the multiple devices may have different physical requirements and capabilities, and the central computing device uses a platform to enable the delivery of an experience to the device that is both tailored to the device and yet common to all devices. In one or more embodiments, a class of target devices is created and experiences are tailored to the generic class of devices. A class of devices may be defined by physical features, types of usage, or other common characteristics of the devices.
In various implementations, the computing device 502 may assume a variety of different configurations, such as for computer 516, mobile 518, and television 520 uses. Each of these configurations includes devices that may have generally different constructs and capabilities, and thus the computing device 502 may be configured according to one or more of the different device classes. For instance, the computing device 502 may be implemented as the computer 516 class of a device that includes a personal computer, desktop computer, a multi-screen computer, laptop computer, netbook, and so on.
The computing device 502 may also be implemented as the mobile 518 class of device that includes mobile devices, such as a mobile phone, portable music player, portable gaming device, a tablet computer, a multi-screen computer, and so on. The computing device 502 may also be implemented as the television 520 class of device that includes devices having or connected to generally larger screens in casual viewing environments. These devices include televisions, set-top boxes, gaming consoles, and so on.
The techniques described herein may be supported by these various configurations of the computing device 502 and are not limited to the specific examples of the techniques described herein. This functionality may also be implemented all or in part through use of a distributed system, such as over a “cloud” 522 via a platform 524 as described below.
The cloud 522 includes and/or is representative of a platform 524 for resources 526. The platform 524 abstracts underlying functionality of hardware (e.g., servers) and software resources of the cloud 522. The resources 526 may include applications and/or data that can be utilized while computer processing is executed on servers that are remote from the computing device 502. Resources 526 can also include services provided over the Internet and/or through a subscriber network, such as a cellular or Wi-Fi network.
The platform 524 may abstract resources and functions to connect the computing device 502 with other computing devices. The platform 524 may also serve to abstract scaling of resources to provide a corresponding level of scale to encountered demand for the resources 526 that are implemented via the platform 524. Accordingly, in an interconnected device embodiment, implementation of functionality described herein may be distributed throughout the system 500. For example, the functionality may be implemented in part on the computing device 502 as well as via the platform 524 that abstracts the functionality of the cloud 522.
In the discussions herein, various different embodiments are described. It is to be appreciated and understood that each embodiment described herein can be used on its own or in connection with one or more other embodiments described herein. Further aspects of the techniques discussed herein relate to one or more of the following embodiments.
A method implemented in a computing device, the method comprising: detecting whether a file on the computing device, created prior to implementation of a data protection policy, has been written to by a first program; adding, based at least on detecting that the file has been written to by the first program, an identifier of the file to a file encryption queue; determining whether any programs on the computing device are currently accessing the file; and encrypting the file based at least on determining that no programs on the computing device are currently accessing the file.
Alternatively or in addition to any of the above described methods, any one or combination of: the method further comprising allowing the first program to open and read the file without adding the file to the file encryption queue; the method further comprising storing the file encryption queue in a nonvolatile memory that persists in the file encryption queue across reboots of the computing device; the identifier of the file comprising a file handle that uniquely identifies the file within the computing device independent of the location where the file is stored on the computing device; the method further comprising receiving a request to wipe organization data for an organization from the computing device, identifying one or more files in the file encryption queue that include the organization data for the organization, and deleting the identified one or more files from a data store of the computing device; the method further comprising blocking access to the file by any additional programs on the computing device while encrypting the file; the method further comprising determining whether access to the file is requested by a second program on the computing device while encrypting the file, aborting the encrypting based at least on determining that access to the file is requested by the second program while encrypting the file, and allowing the second program to access the file; the method further comprising removing the file from the encryption queue after the file is encrypted, receiving, from a second program, a request to access the file while the file is in the file encryption queue, and denying the second program access to the file.
A computing device comprising: one or more processors; a data store; and one or more computer-readable storage media having stored thereon multiple instructions that, based on execution by the one or more processors, implement an encryption and decryption system that includes an encryption module and an encryption determination module; the encryption module configured to encrypt a file in the data store, created prior to implementation of a data protection policy on the computing device, based at least on receiving a request from the encryption determination module to encrypt the file; the encryption determination module configured to: detect whether the file in the data store is to be encrypted due to the data protection policy, communicate to the encryption module to encrypt the file at an appropriate time, and determine the appropriate time using an encrypt on close technique, an encrypt on open technique, an encrypt without exclusive access technique, and/or an encrypt location technique.
Alternatively or in addition to any of the above described computing devices, any one or combination of: the encrypt on close technique comprising a technique in which the file is encrypted based at least on a first condition and a second condition both being satisfied, the first condition being that data is written to the file after implementation of the data protection policy, and the second condition being that no program is currently accessing the file; the encryption determination module further configured to allow programs to open and read the file without communicating to the encryption module to encrypt the file; the computing device further comprising a nonvolatile memory that stores a file encryption queue, the file encryption queue including file identifiers of files that have been detected as to be encrypted due to the data protection policy and that have been written to after implementation of the data protection policy, the file encryption queue persisting file identifiers across reboots of the computing device; the encrypt on open technique comprising a technique in which the file is encrypted based at least on the file being opened by a program on the computing device; the encrypt without exclusive access technique comprising a technique in which the file is encrypted without requiring the encryption module to have exclusive access to the file; the encrypt location technique comprising a technique in which the file is encrypted based at least on the file being stored in a particular location of the data store.
A computing device comprising: one or more processors; a data store; a nonvolatile memory storing a file encryption queue; and one or more computer-readable storage media having stored thereon multiple instructions that, based on execution by the one or more processors, implement an encryption and decryption system that includes an encryption module and an encryption determination module; the encryption module configured to encrypt a file, created prior to implementation of a data protection policy on the computing device, based at least on a request from the encryption determination module to encrypt the file; the encryption determination module configured to: detect whether the file has been written to by a first program, add, based at least on the file having been written to by the first program, an identifier of the file to the file encryption queue, determine whether any programs on the computing device are currently accessing the file, and communicate the request to the encryption module to encrypt the file based at least on determining that no programs on the computing device are currently accessing the file.
Alternatively or in addition to any of the above described computing devices, any one or combination of: the encryption determination module further configured to allow the first program to open and read the file without adding the file to the file encryption queue; the non-volatile memory persisting the file encryption queue across reboots of the computing device; the encryption determination module further configured to determine whether access to the file is requested by a second program while the encryption module is encrypting the file, abort the encrypting based at least on determining that access to the file is requested by the second program while encrypting the file, and allow the second program to access the file; the encryption determination module further configured to receive a request to wipe organization data for an organization from the computing device, identify one or more files in the file encryption queue that include the organization data for the organization, and delete the identified one or more files from a data store of the computing device.
Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5495533 | Linehan et al. | Feb 1996 | A |
| 5787131 | Bottomley | Jul 1998 | A |
| 5897661 | Baranovsky et al. | Apr 1999 | A |
| 5944783 | Nieten | Aug 1999 | A |
| 5966263 | Freitas et al. | Oct 1999 | A |
| 5974503 | Venkatesh et al. | Oct 1999 | A |
| 6016402 | Thomas et al. | Jan 2000 | A |
| 6028725 | Blumenau | Feb 2000 | A |
| 6041386 | Bello | Mar 2000 | A |
| 6067199 | Blumenau | May 2000 | A |
| 6076143 | Blumenau | Jun 2000 | A |
| 6134062 | Blumenau | Oct 2000 | A |
| 6151665 | Blumenau | Nov 2000 | A |
| 6170037 | Blumenau | Jan 2001 | B1 |
| 6170055 | Meyer et al. | Jan 2001 | B1 |
| 6253300 | Lawrence et al. | Jun 2001 | B1 |
| 6292317 | Alexander | Sep 2001 | B1 |
| 6292790 | Krahn et al. | Sep 2001 | B1 |
| 6550011 | Sims, III | Apr 2003 | B1 |
| 6665784 | Ihde et al. | Dec 2003 | B2 |
| 6727896 | Tsang | Apr 2004 | B2 |
| 6728379 | Ishibashi et al. | Apr 2004 | B1 |
| 6789162 | Talagala et al. | Sep 2004 | B1 |
| 6944742 | Shoff et al. | Sep 2005 | B1 |
| 6968973 | Uyttendaele et al. | Nov 2005 | B2 |
| 6996696 | Shoff et al. | Feb 2006 | B2 |
| 7197638 | Grawrock | Mar 2007 | B1 |
| 7356662 | Shoff et al. | Apr 2008 | B2 |
| 7360073 | Billstrom et al. | Apr 2008 | B1 |
| 7380140 | Weissman et al. | May 2008 | B1 |
| 7382883 | Cross et al. | Jun 2008 | B2 |
| 7409623 | Baker et al. | Aug 2008 | B2 |
| 7451484 | Nadalin et al. | Nov 2008 | B1 |
| 7536536 | Joshi et al. | May 2009 | B1 |
| 7559088 | Cohen et al. | Jul 2009 | B2 |
| 7580950 | Kavuri et al. | Aug 2009 | B2 |
| 7594087 | Zeevi et al. | Sep 2009 | B2 |
| 7646380 | Tsang | Jan 2010 | B2 |
| 7694134 | Witt et al. | Apr 2010 | B2 |
| 7711923 | Rogers et al. | May 2010 | B2 |
| 7725703 | Hunter et al. | May 2010 | B2 |
| 7757100 | Weissman et al. | Jul 2010 | B2 |
| 7849254 | Ash et al. | Dec 2010 | B2 |
| 7890664 | Tao et al. | Feb 2011 | B1 |
| 7903549 | Judge et al. | Mar 2011 | B2 |
| 7930540 | Ahuja et al. | Apr 2011 | B2 |
| 7962739 | Childs et al. | Jun 2011 | B2 |
| 7979626 | Rogers | Jul 2011 | B2 |
| 8046365 | Saito | Oct 2011 | B2 |
| 8046533 | Kompella et al. | Oct 2011 | B2 |
| 8085933 | Ferguson | Dec 2011 | B2 |
| 8214656 | Plotkin et al. | Jul 2012 | B1 |
| 8234477 | Shaath | Jul 2012 | B2 |
| 8249257 | Brutch et al. | Aug 2012 | B2 |
| 8321688 | Auradkar et al. | Nov 2012 | B2 |
| 8341427 | Auradkar et al. | Dec 2012 | B2 |
| 8341430 | Ureche et al. | Dec 2012 | B2 |
| 8387109 | Ureche et al. | Feb 2013 | B2 |
| 8411863 | Ureche et al. | Apr 2013 | B2 |
| 8416954 | Raizen et al. | Apr 2013 | B1 |
| 8417973 | Cooper et al. | Apr 2013 | B2 |
| 8423792 | Luciani et al. | Apr 2013 | B2 |
| 8458490 | Konetski et al. | Jun 2013 | B2 |
| 8527561 | Moody, II et al. | Sep 2013 | B1 |
| 8538919 | Nielsen et al. | Sep 2013 | B1 |
| 8549271 | Joshi et al. | Oct 2013 | B1 |
| 8583879 | Na et al. | Nov 2013 | B2 |
| 8588422 | Beachem et al. | Nov 2013 | B2 |
| 8625802 | Parann-Nissany | Jan 2014 | B2 |
| 8661193 | Cobos et al. | Feb 2014 | B1 |
| 8667213 | Rogers et al. | Mar 2014 | B2 |
| 8689279 | Basmov et al. | Apr 2014 | B2 |
| 8726343 | Borzycki et al. | May 2014 | B1 |
| 8726407 | Etchegoyen | May 2014 | B2 |
| 8769305 | Blaisdell | Jul 2014 | B2 |
| 8874935 | Basmov et al. | Oct 2014 | B2 |
| 8875304 | Celi, Jr. et al. | Oct 2014 | B2 |
| 9323465 | Flynn et al. | Apr 2016 | B2 |
| 9369289 | Harrison et al. | Jun 2016 | B1 |
| 9430664 | Adam et al. | Aug 2016 | B2 |
| 9477614 | Basmov et al. | Oct 2016 | B2 |
| 9537656 | Debout et al. | Jan 2017 | B2 |
| 9740639 | Basmov et al. | Aug 2017 | B2 |
| 9825945 | Adam et al. | Nov 2017 | B2 |
| 9853812 | Mehta et al. | Dec 2017 | B2 |
| 9853820 | Adam et al. | Dec 2017 | B2 |
| 20010000265 | Schreiber et al. | Apr 2001 | A1 |
| 20020019935 | Andrew et al. | Feb 2002 | A1 |
| 20030081784 | Kallahalla | May 2003 | A1 |
| 20030084298 | Messerges et al. | May 2003 | A1 |
| 20030196114 | Brew et al. | Oct 2003 | A1 |
| 20030221095 | Gaunt et al. | Nov 2003 | A1 |
| 20040044912 | Connary et al. | Mar 2004 | A1 |
| 20040090811 | Kang | May 2004 | A1 |
| 20040146015 | Cross et al. | Jul 2004 | A1 |
| 20040174345 | Tsang | Sep 2004 | A1 |
| 20050071280 | Irwin et al. | Mar 2005 | A1 |
| 20050091661 | Kurien et al. | Apr 2005 | A1 |
| 20050097341 | Francis et al. | May 2005 | A1 |
| 20050213377 | Shoff et al. | Sep 2005 | A1 |
| 20050262361 | Thibadeau | Nov 2005 | A1 |
| 20050265074 | Shoff et al. | Dec 2005 | A1 |
| 20050283730 | Uyttendaele et al. | Dec 2005 | A1 |
| 20060101027 | Hotchkiss | May 2006 | A1 |
| 20060155919 | Lasser et al. | Jul 2006 | A1 |
| 20060190984 | Heard et al. | Aug 2006 | A1 |
| 20060206507 | Dahbour | Sep 2006 | A1 |
| 20060277590 | Limont et al. | Dec 2006 | A1 |
| 20060279556 | Tsang | Dec 2006 | A1 |
| 20070028231 | Kelso et al. | Feb 2007 | A1 |
| 20070058806 | Ferguson | Mar 2007 | A1 |
| 20070150886 | Shapiro | Jun 2007 | A1 |
| 20070244940 | Devarakonda et al. | Oct 2007 | A1 |
| 20070250678 | Ueoka et al. | Oct 2007 | A1 |
| 20070300008 | Rogers et al. | Dec 2007 | A1 |
| 20070300037 | Rogers et al. | Dec 2007 | A1 |
| 20080002830 | Cherkasov et al. | Jan 2008 | A1 |
| 20080005467 | Morley et al. | Jan 2008 | A1 |
| 20080010468 | Ruiz | Jan 2008 | A1 |
| 20080082448 | Meijer et al. | Apr 2008 | A1 |
| 20080083036 | Ozzie et al. | Apr 2008 | A1 |
| 20080107262 | Helfman et al. | May 2008 | A1 |
| 20080130156 | Chu et al. | Jun 2008 | A1 |
| 20080141040 | Biddle et al. | Jun 2008 | A1 |
| 20080155316 | Pawar et al. | Jun 2008 | A1 |
| 20080168315 | Mead et al. | Jul 2008 | A1 |
| 20080229428 | Camiel | Sep 2008 | A1 |
| 20080240253 | Au et al. | Oct 2008 | A1 |
| 20080240441 | Kawakami | Oct 2008 | A1 |
| 20080263371 | Weissman et al. | Oct 2008 | A1 |
| 20080301470 | Green et al. | Dec 2008 | A1 |
| 20090024795 | Kobara | Jan 2009 | A1 |
| 20090063756 | Asipov | Mar 2009 | A1 |
| 20090075630 | McLean | Mar 2009 | A1 |
| 20090132474 | Ma et al. | May 2009 | A1 |
| 20090205012 | Jain et al. | Aug 2009 | A1 |
| 20090210267 | Fish et al. | Aug 2009 | A1 |
| 20090287874 | Rogers et al. | Nov 2009 | A1 |
| 20090307563 | Marquez et al. | Dec 2009 | A1 |
| 20100082898 | Mangold et al. | Apr 2010 | A1 |
| 20100100721 | Su et al. | Apr 2010 | A1 |
| 20100107213 | Ureche | Apr 2010 | A1 |
| 20100169948 | Budko et al. | Jul 2010 | A1 |
| 20100250847 | Chen | Sep 2010 | A1 |
| 20100266132 | Bablani et al. | Oct 2010 | A1 |
| 20100299152 | Batchu et al. | Nov 2010 | A1 |
| 20100306175 | Johnson et al. | Dec 2010 | A1 |
| 20100332725 | Post et al. | Dec 2010 | A1 |
| 20110010560 | Etchegoyen | Jan 2011 | A1 |
| 20110035577 | Lin et al. | Feb 2011 | A1 |
| 20110055559 | Li et al. | Mar 2011 | A1 |
| 20110055560 | Meissner et al. | Mar 2011 | A1 |
| 20110060915 | Tal | Mar 2011 | A1 |
| 20110078760 | De Perthuis | Mar 2011 | A1 |
| 20110087890 | Munsil et al. | Apr 2011 | A1 |
| 20110154023 | Smith et al. | Jun 2011 | A1 |
| 20110202916 | VoBa et al. | Aug 2011 | A1 |
| 20110225431 | Stufflebeam, Jr. et al. | Sep 2011 | A1 |
| 20110225640 | Ganapathy et al. | Sep 2011 | A1 |
| 20110246785 | Linsley et al. | Oct 2011 | A1 |
| 20110247047 | Loureiro et al. | Oct 2011 | A1 |
| 20110252232 | De Atley et al. | Oct 2011 | A1 |
| 20110264925 | Russo et al. | Oct 2011 | A1 |
| 20110276683 | Goldschlag et al. | Nov 2011 | A1 |
| 20110277013 | Chinta | Nov 2011 | A1 |
| 20120017095 | Blenkhorn et al. | Jan 2012 | A1 |
| 20120036347 | Swanson et al. | Feb 2012 | A1 |
| 20120036370 | Lim et al. | Feb 2012 | A1 |
| 20120079603 | Brown et al. | Mar 2012 | A1 |
| 20120087033 | Yang | Apr 2012 | A1 |
| 20120110345 | Pigeon | May 2012 | A1 |
| 20120159148 | Behren et al. | Jun 2012 | A1 |
| 20120173882 | Horn et al. | Jul 2012 | A1 |
| 20120239618 | Kung | Sep 2012 | A1 |
| 20120297190 | Shen et al. | Nov 2012 | A1 |
| 20120331550 | Raj et al. | Dec 2012 | A1 |
| 20130013856 | Rogers et al. | Jan 2013 | A1 |
| 20130054977 | Basmov | Feb 2013 | A1 |
| 20130054979 | Basmov | Feb 2013 | A1 |
| 20130061035 | Hook et al. | Mar 2013 | A1 |
| 20130067242 | Lyakhovitskiy et al. | Mar 2013 | A1 |
| 20130074142 | Brennan et al. | Mar 2013 | A1 |
| 20130086691 | Fielder | Apr 2013 | A1 |
| 20130091543 | Wade | Apr 2013 | A1 |
| 20130117561 | Chawla et al. | May 2013 | A1 |
| 20130117805 | Kent et al. | May 2013 | A1 |
| 20130124859 | Pestoni et al. | May 2013 | A1 |
| 20130138971 | Budko et al. | May 2013 | A1 |
| 20130198474 | Shaath | Aug 2013 | A1 |
| 20130208893 | Shablygin et al. | Aug 2013 | A1 |
| 20130283392 | Mirashrafi et al. | Oct 2013 | A1 |
| 20130291055 | Muppidi et al. | Oct 2013 | A1 |
| 20130318359 | Morris et al. | Nov 2013 | A1 |
| 20140007182 | Qureshi | Jan 2014 | A1 |
| 20140007222 | Qureshi et al. | Jan 2014 | A1 |
| 20140019753 | Lowry et al. | Jan 2014 | A1 |
| 20140032691 | Barton et al. | Jan 2014 | A1 |
| 20140032759 | Barton et al. | Jan 2014 | A1 |
| 20140032933 | Smith et al. | Jan 2014 | A1 |
| 20140041046 | Vantalon et al. | Feb 2014 | A1 |
| 20140059690 | Li et al. | Feb 2014 | A1 |
| 20140075493 | Krishnan et al. | Mar 2014 | A1 |
| 20140081980 | Aad | Mar 2014 | A1 |
| 20140109178 | Barton | Apr 2014 | A1 |
| 20140156705 | Beecham et al. | Jun 2014 | A1 |
| 20140156706 | Beecham et al. | Jun 2014 | A1 |
| 20140164774 | Nord et al. | Jun 2014 | A1 |
| 20140181512 | Spalka et al. | Jun 2014 | A1 |
| 20140230007 | Roth et al. | Aug 2014 | A1 |
| 20140259117 | Wachendorf et al. | Sep 2014 | A1 |
| 20140344570 | Adam et al. | Nov 2014 | A1 |
| 20140344571 | Adam et al. | Nov 2014 | A1 |
| 20140359793 | Dobson | Dec 2014 | A1 |
| 20150033039 | Basmov et al. | Jan 2015 | A1 |
| 20150160879 | Flynn et al. | Jun 2015 | A1 |
| 20150186657 | Nakhjiri | Jul 2015 | A1 |
| 20150270956 | Basmov et al. | Sep 2015 | A1 |
| 20150278531 | Smith et al. | Oct 2015 | A1 |
| 20160072796 | Adam et al. | Mar 2016 | A1 |
| 20160080149 | Mehta et al. | Mar 2016 | A1 |
| 20160127327 | Mehta et al. | May 2016 | A1 |
| 20160154744 | Zheng et al. | Jun 2016 | A1 |
| 20160173281 | White et al. | Jun 2016 | A1 |
| 20160255079 | Harrison et al. | Sep 2016 | A1 |
| 20160283406 | Linga et al. | Sep 2016 | A1 |
| 20170004094 | Basmov et al. | Jan 2017 | A1 |
| 20170005809 | Adam et al. | Jan 2017 | A1 |
| Number | Date | Country |
|---|---|---|
| 1653422 | Aug 2005 | CN |
| 1713756 | Dec 2005 | CN |
| 102646077 | Aug 2012 | CN |
| 103092664 | May 2013 | CN |
| 103092938 | May 2013 | CN |
| 103500116 | Jan 2014 | CN |
| 103577567 | Feb 2014 | CN |
| 2393033 | Dec 2011 | EP |
| 2448303 | May 2012 | EP |
| 2509275 | Oct 2012 | EP |
| 2562675 | Feb 2013 | EP |
| 2680487 | Jan 2014 | EP |
| 200519595 | Jun 2005 | TW |
| 200723093 | Jun 2007 | TW |
| 201032559 | Sep 2010 | TW |
| I540453 | Jul 2016 | TW |
| WO-0049488 | Aug 2000 | WO |
| 2004034184 | Apr 2004 | WO |
| WO-2004107646 | Dec 2004 | WO |
| WO-2009069043 | Jun 2009 | WO |
| WO-2009149019 | Dec 2009 | WO |
| WO-2012016091 | Feb 2012 | WO |
| WO-2012167392 | Dec 2012 | WO |
| Entry |
|---|
| “Adobe AIR 1.5 Applications with Flex—Storing Encrypted Data”, Retrieved From: <http://help.adobe.com/en—US/AIR/1.5/devappsflex/WS5b3ccc516d4fbf351e63e3d118666ade46-7e31.html> May 1, 2015, Oct. 19, 2012, 2 pages. |
| “BitLocker Drive Encryption in Windows Vista”, Microsoft TechNet, retrieved from <http://technet.microsoft.com/en-us/library/cc725719(WS.10).aspx> on Apr. 25, 2011, Aug. 6, 2010, 9 pages. |
| “Blackberry 10”, Retrieved from <http://en.wikipedia.org/wiki/BlackBerry—10#BlackBerry—Balance> on Apr. 2, 2013, Apr. 1, 2013, 8 pages. |
| “Divide: The Next Generation of Enterprise Mobility”, Retrieved at <<http://www.divide.com/download/Divide—Product—Sheet—1116.pdf<< on May 8, 2013, Jan. 20, 2013, 2 pages. |
| “Exchange ActiveSync”, Retrieved from <http://en.wikipedia.org/wiki/Exchange—ActiveSync> on Apr. 1, 2013, Apr. 1, 2013, 5 pages. |
| “Exchange ActiveSync: Provisioning Protocol”, Retrieved from <http://msdn.microsoft.com/en-us/library/dd299443(v=Exchg.80).aspx> on Apr. 1, 2013, Dec. 3, 2008, 4 Pages. |
| “Extended European Search Report”, EP Application No. 11871440.1, dated Mar. 16, 2015, 5 pages. |
| “Extended European Search Report”, EP Application No. 11871825.3, dated May 11, 2015, 7 pages. |
| “Final Office Action”, U.S. Appl. No. 13/221,629, dated Dec. 23, 2013, 24 pages. |
| “Final Office Action”, U.S. Appl. No. 13/898,368, dated Apr. 16, 2015, 16 pages. |
| “Foreign Notice of Allowance”, CN Application No. 201210314631.1, dated Aug. 20, 2015, 4 pages. |
| “Foreign Notice of Allowance”, CN Application No. 201210314748.X, dated Jul. 3, 2015, 3 pages. |
| “Foreign Office Action”, CN Application No. 201210314631.1, dated Dec. 1, 2014, 14 pages. |
| “Foreign Office Action”, CN Application No. 201210314748.X, dated Mar. 17, 2015, 7 pages. |
| “Foreign Office Action”, CN Application No. 201210314748.X, dated Sep. 23, 2014, 14 Pages. |
| “Foreign Office Action”, TW Application No. 100136564, dated Oct. 20, 2015, 11 pages. |
| “How Can We Ensure Data Security on Mobile Devices??”, Retrieved From: <http://enterprise.huawei.com/topic/byod—en/solution—byod—info—3.html> Mar. 6, 2014, Jun. 16, 2013, 4 Pages. |
| “How Do I Prevent 'Sensitive Data Exposure'?”, Retrieved From: <https://www.owasp.org/index.php/Top—10—2013-A6-Sensitive—Data—Exposure> May 12, 2015, Jun. 23, 2013, 2 pages. |
| “InnoSetup Help”, Retrieved From: <http://www.jrsoftware.org/ishelp/index.php?topic=filessection> May 12, 2015, 8 pages. |
| “International Search Report and Written Opinion”, Application No. PCT/US2013/061053, dated Jan. 30, 2014, 10 Pages. |
| “International Search Report and Written Opinion”, Application No. PCT/US2015/021125, dated Jul. 3, 2015, 9 Pages. |
| “International Search Report and Written Opinion”, Application No. PCT/US2011/055600, dated Jul. 30, 2012, 9 pages. |
| “International Search Report and Written Opinion”, Application No. PCT/US2011/055626, dated Sep. 19, 2012, 9 pages. |
| “Mobile Device Management”, Retrieved from <http://www.bing.com/search?q=mobile+device+management&src=IE-TopResult&Form=IE10TR> on Apr. 2, 2013, 2013, 2 pages. |
| “MobileIron Introduces the First Complete Mobile App Persona for the Enterprise”, Retrieved from <http://www.mobileiron.com/en/company/press-room/press-releases/371-mobileiron-introduces-the-first-complete-mobile-app-persona-for-the-enterprise> on Mar. 25, 2013, Nov. 6, 2012, 2 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 13/221,629, dated May 17, 2013, 27 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 13/221,699, dated Apr. 1, 2013, 16 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 13/898,368, dated Aug. 4, 2015, 17 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 13/898,368, dated Dec. 8, 2014, 12 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 13/933,928, dated Oct. 21, 2015, 11 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 14/221,105, dated Aug. 4, 2015, 25 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 14/489,288, dated Nov. 6, 2015, 25 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 14/506,167, dated Jun. 29, 2015, 16 pages. |
| “Notice of Allowance”, U.S. Appl. No. 13/221,629, dated Jun. 27, 2014, 16 pages. |
| “Notice of Allowance”, U.S. Appl. No. 13/221,699, dated Oct. 30, 2013, 9 pages. |
| “OMA Device Management”, Retrieved from <http://en.wikipedia.org/wiki/OMA—DM> on Apr. 2, 2013, Mar. 25, 2013, 4 Pages. |
| “OMA Device Management”, Retrieved from <http://msdn.microsoft.com/en-us/library/bb737369.aspx>, Aug. 4, 2010, 4 Pages. |
| “Search Report”, TW Application No. 100136565, dated Aug. 3, 2015, 1 pages. |
| “Securing end-user mobile devices in the enterprise”, In Proceedings: Thought Leadership White Paper, IBM Global Technology Services, Apr. 2011, 6 Pages. |
| “Security Solutions and Services”, retrieved from <http://www.csc.com/public—sector/offerings/11043/17449-security—solutions—and—services> on Apr. 25, 2011, 2 pages. |
| “ThoriumCloud Enterprise Container”, Retrieved from <http://www.thoriumcloud.com/> on Mar. 25, 2013, 2013, 4 Pages. |
| “Unlock BitLocker under Windows PC”, Retrieved from: <http://windows7migration.info/index.php option=com—content&view=article&id=1836:unlock-bitlocker-under-windows-pe&catid=42:4sysops&Itemid=61> on Aug. 4, 2011, 5 pages. |
| “Various Mobile Device Management (MDM) Solutions”, Retrieved From: <http://www.bing.com/search?q=mobile+device+management&src=IE-TopResult&FORM=IE10TR> Mar. 5, 2014, 2 Pages. |
| “What Android Sync'd Data is Encrypted?”, Retrieved From: <http://android.stackexchange.com/questions/3129/what-android-syncd-data-is-encrypted>, Nov. 25, 2010, 3 pages. |
| “Windows Selective Wipe for Device Data Management”, Retrieved from <http://technet.microsoft.com/en-us/library/dn486874.aspx>, Nov. 1, 2013, 4 pages. |
| Becher,“Mobile Security Catching Up? Revealing the Nuts and Bolts of the Security of Mobile Devices”, Proceedings of IEEE Symposium on Security and Privacy, May 22, 2011, pp. 96-111. |
| Bugiel,“Practical and Lightweight Domain Isolation on Android”, Proceedings of the 1st ACM Workshop on Security and privacy in Smartphones and Mobile Devices, Oct. 17, 2011, 12 pages. |
| Gudeth,“Delivering Secure Applications on Commercial Mobile Devices: The Case for Bare Metal Hypervisors”, Proceedings of the 1st ACM Workshop on Security and privacy in Smartphones and Mobile Devices, Oct. 17, 2011, pp. 33-38. |
| Lawson,“Meeting Regulatory Compliance Challenges with Data Management Tools Solutions”, YL & A, www.ylassoc.com, available at <ftp://public.dhe.ibm.com/software/data/db2imstools/solutions/lawson-reg-compliance.pdf>, Sep. 19, 2006, pp. 1-18. |
| Li,“Managing Data Retention Policies at Scale”, IFIP/IEEE International Symposium on Integrated Network Management 2011, Dublin, Ireland, May 23-27, 2011., available at <http://www.hpl.hp.com/techreports/2010/HPL-2010-203.pdf>, Dec. 21, 2010, 9 pages. |
| Li,“Scalable and Secure Sharing of Personal Health Records in Cloud Computing Using Attribute-Based Encryption”, IEEE Transactions on Parallel and Distributed Systems, vol. 24, Issue 1, Jan. 2013, pp. 131-143. |
| Mitchell,“What is a Selective Wipe?”, Retrieved from <http://www.landesk.com/blog/what-is-a-selective-wipe/> on Mar. 25, 2013, Apr. 30, 2012, 1 page. |
| Mont,“A Systemic Approach to Privacy Enforcement and Policy Compliance Checking in Enterprises”, Trusted Systems Laboratory, HP Laboratories Bristol, HPL-2006-44, available at <http://www.hpl.hp.com/techreports/2006/HPL-2006-44.pdf>, Mar. 16, 2006, 11 pages. |
| Oberheide,“When Mobile is Harder Than Fixed (and Vice Versa): Demystifying Security Challenges in Mobile Environments”, Proceedings of Eleventh International Workshop on Mobile Computing Systems and Applications, Feb. 22, 2010, 6 pages. |
| Pecherle,“Data Wiping System with Fully Automated, Hidden and Remote Destruction Capabilities”, In Journal of WSEAS Transactions on Computers, vol. 9, Issue 9, Available at <http://www.wseas.us/e-library/transactions/computers/2010/88-110.pdf>, Sep. 2010, pp. 939-948. |
| Pisko,“Trusted Computing in Mobile Platforms—Players, Usage Scenarios, and Interests”, Proceedings of Privacy and Security, Sep. 2005, pp. 526-530. |
| Purdy,“Thumb Drive”, Retrieved From: <http://lifehackercom/5583307/top-10-usb-thumb-drive-tricks-2010-edition> May 12, 2015, Oct. 7, 2010, 6 pages. |
| Reardon,“Secure Deletion on Log-structured File Systems”, In Proceedings: Technical Report, Department of Computer Science, ETH Zurich Available at: <http://arxiv.org/pdf/1106.0917.pdf>, Jun. 5, 2011, 11 pages. |
| Stehle,“Provisioning, Policies, Remote Wipe, and the Allow/Block/Quarantine list in Exchange ActiveSync”, Retrieved from <http://msdn.microsoft.com/en-us/library/exchange/hh509085(v=exchg.140).aspx> on Apr. 1, 2013, 2013, 20 pages. |
| Stockton,“Divide and your Data: Privacy, Sync, Backup, Restore, Storage and Wipe”, Retrieved from <http://support.divide.com/entries/20964987-Divide-and-your-data-privacy-sync-backup-restore-storage-and-wipe> on Mar. 25, 2013, Feb. 8, 2012, 2 pages. |
| Toegl,“acTvSM: A Dynamic Virtualization Platform for Enforcement of Application Integrity”, Lecture Notes in Computer Science vol. 6802, 2011, Retrieved from <https://online.tugraz.at/tug—online/voe—main2.getvolltext?pCurrPk=60165>, 2011, 20 pages. |
| Zeis,“The security of BlackBerry Balance”, Retrieved From: <http://crackberry.com/security-blackberry-balances Mar. 6, 2014, Aug. 2, 2013, 13 pages. |
| “Final Office Action”, U.S. Appl. No. 14/481,672, dated Feb. 9, 2017, 16 pages. |
| “Final Office Action”, U.S. Appl. No. 14/506,167, dated Nov. 23, 2015, 19 pages. |
| “Final Office Action”, U.S. Appl. No. 14/533,921, dated Feb. 24, 2017, 15 pages. |
| “Foreign Notice of Allowance”, TW Application No. 110501128, dated Dec. 29, 2016, 4 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 14/221,105, dated Feb. 24, 2017, 42 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 14/489,288, dated Jan. 19, 2017, 30 pages. |
| Kher,“Securing Distributed Storage: Challenges, Techniques, and Systems”, ACM Workshop on Storage security and survivability, 2005, p. 9-25. |
| Sharma,“TransCrypt: Design of a Secure and Transparent Encrypting File System”, Master's Thesis, Indian Institute of Technology Kanpur, Aug. 2006, 50 pages. |
| “Final Office Action”, U.S. Appl. No. 13/898,368, dated Dec. 2, 2015, 19 pages. |
| “International Preliminary Report on Patentability”, Application No. PCT/US2013/061053, dated Nov. 24, 2015, 8 pages. |
| “International Search Report and Written Opinion”, Application No. PCT/US2015/049981, dated Dec. 3, 2015, 11 pages. |
| Menezes,“Handbook of Applied Cryptography”, CRC Press LLC,, Jan. 1, 1997, pp. 25-27 & 551-553. |
| “Advisory Action”, U.S. Appl. No. 14/506,167, dated Apr. 13, 2016, 3 pages. |
| “Final Office Action”, U.S. Appl. No. 14/221,105, dated Feb. 22, 2016, 35 pages. |
| “Foreign Notice of Allowance”, TW Application No. 100136564, dated Feb. 25, 2016, 4 pages. |
| “International Search Report and Written Opinion”, Application No. PCT/US2015/058707, dated Jan. 20, 2016, 11 Pages. |
| “International Search Report and Written Opinion”, Application No. PCT/US2015/048750, dated Apr. 11, 2016, 22 pages. |
| “Second Written Opinion”, Application No. PCT/US2015/021125, dated Feb. 2, 2016, 6 pages. |
| Chen,“Hardware-Assisted Application-Level Access Control”, ISC '09 Proceedings of the 12th International Conference on Information Security, 090/7/2009, 16 pages. |
| “Final Office Action”, U.S. Appl. No. 14/489,288, dated Jun. 15, 2016, 25 pages. |
| “Foreign Notice of Allowance”, TW Application No. 100136565, dated Mar. 25, 2016, 4 pages. |
| “International Preliminary Report on Patentability”, Application No. PCT/US2015/021125, dated May 11, 2016, 7 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 14/533,921, dated Apr. 19, 2016, 18 pages. |
| “Notice of Allowance”, U.S. Appl. No. 13/933,928, dated Apr. 22, 2016, 8 pages. |
| “Batch File Encrypt—Encrypt and decrypt whole files or their parts using symmetric algorithms”, Retrieved at: https://web.archive.org/web/20131217055640/http://www.binarymark.com/products/batchfileencrypt/default.aspx—on Dec. 15, 2016, Dec. 17, 2013, 21 pages. |
| “File locking—Wikipedia”, Retrieved at: https://en.wikipedia.org/w/index.php?title=File—locking&oldid=679856482—on Dec. 15, 2016, 5 pages. |
| “International Preliminary Report on Patentability”, Application No. PCT/US2015/048750, dated Dec. 6, 2016, 11 pages. |
| “International Preliminary Report on Patentability”, Application No. PCT/US2015/049981, dated Oct. 18, 2016, 6 pages. |
| “International Preliminary Report on Patentability”, Application No. PCT/US2015/058707, dated Oct. 27, 2016, 7 pages. |
| “International Search Report and Written Opinion”, Application No. PCT/US2016/054036, dated Dec. 1, 2016, 12 pages. |
| “Second Written Opinion”, Application No. PCT/US2016/039468, dated Dec. 1, 2016, 5 pages. |
| “Corrected Notice of Allowance”, U.S. Appl. No. 14/506,167, dated Sep. 7, 2016, 2 pages. |
| “Examiner's Answer to Appeal Brief”, U.S. Appl. No. 13/898,368, dated Sep. 8, 2016, 7 pages. |
| “Foreign Office Action”, TW Application No. 105101128, dated Aug. 23, 2016, 5 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 14/481,672, dated Jul. 28, 2016, 12 pages. |
| “Notice of Allowance”, U.S. Appl. No. 14/506,167, dated Jun. 22, 2016, 11 pages. |
| “Restriction Requirement”, U.S. Appl. No. 14/481,672, dated Jun. 28, 2016, 6 pages. |
| “Second Written Opinion”, U.S. Appl. No. PCT/US2015/049981, dated Jul. 26, 2016, 5 pages. |
| “Corrected Notice of Allowance”, U.S. Appl. No. 14/506,167, dated Sep. 27, 2016, 2 pages. |
| “International Search Report and Written Opinion”, Application No. PCT/US2016/039468, dated Sep. 1, 2016, 10 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 14/788,377, dated Sep. 23, 2016, 14 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 15/266,591, dated Oct. 12, 2016, 10 pages. |
| “Second Written Opinion”, Application No. PCT/US2015/048750, dated Aug. 8, 2016, 9 pages. |
| Lane, Adrian, “Cracking the Confusion: Encryption Layers”, Published on: Feb. 12, 2015 Available at: https://securosis.com/blog/cracking-the-confusion-encryption-layers. |
| “About EFS (Encrypting File System)”, Published on: Oct. 28, 2014 Available at: https://www.elcomsoft.com/help/en/aefsdr/about—efs.html. |
| “CheckVision Enterprise Encryption”, Published on: Apr. 24, 2013 Available at: http://assetsl.csc.com/banking/downloads/CardsPayments—CheckVisionEnterprise—DS.pdf. |
| Wahl, Peter, “Oracle Advanced Security Transparent Data Encryption Best Practices”, In Oracle White Paper, Jul. 2012, 29 pages. |
| Kalogeropoulos, John, “Oracle Data Pump Encrypted Dump File Support”, In Oracle White Paper, Jul. 2011, 15 pages. |
| “DataStax Enterprise 3.2”, Retrieved on: Jul. 23, 2015 Available at: http://docs.datastax.com/en/datastax—enterprise/3.2/datastax—enterprise/sec/secTDE.html. |
| “Application Encryption-Vormetric Data Security Products”, Published on: Jun. 27, 2014 Available at: http://www.vormetric.com/products/vormetric-application-encryption. |
| “Oracle Advanced Security”, Published on: Apr. 16, 2011 Available at: http://www.oracle.com/technetwork/database/security/ds-advanced-security-tde-psft-129631.pdf. |
| “Transparent Data Encryption (TDE)”, Retrieved on: Jul. 23, 2015 Available at https://msdn.microsoft.com/en-in/library/bb934049.aspx. |
| “Approaches for Encryption of Data at Rest in the Enterprise”, In White Papers, Jan. 2008, pp. 1-24. |
| Magnabosco, John, “Transparent Data Encryption”, Published on: Mar. 16, 2010 Available at: https://www.simple-talk.com/sql/database-administration/transparent-data-encryption/. |
| Adam, Derek, “Enterprise Data Protection: Building Universal Windows Apps That Keep Work and Personal Data Separate and Secure”, Retrieved on: Jul. 23, 2015 Available at: https://mix.office.com/watch/fd0jojbqv6qx. |
| “Corrected Notice of Allowance”, U.S. Appl. No. 15/266,591, dated Jul. 5, 2017, 2 pages. |
| “Corrected Notice of Allowance”, U.S. Appl. No. 15/266,591, dated Jul. 19, 2017, 2 pages. |
| “Final Office Action”, U.S. Appl. No. 14/788,377, dated May 8, 2017, 20 pages. |
| “Foreign Office Action”, CN Application No. 201380076761.9, dated May 31, 2017, 17 pages. |
| “Notice of Allowance”, U.S. Appl. No. 15/266,591, dated May 11, 2017, 11 pages. |
| “Notice of Allowance”, U.S. Appl. No. 14/481,672, dated Jul. 27, 2017, 7 pages. |
| “Second Written opinion Issued in PCT Application No. PCT/US2016/054036”, dated Aug. 8, 2017, 6 Pages. |
| “Final Office Action”, U.S. Appl. No. 14/221,105, dated Aug. 23, 2017, 41 pages. |
| “International Preliminary Report on Patentability”, Application No. PCT/US2016/039468, dated Oct. 9, 2017, 7 pages. |
| “International Preliminary Report on Patentability”, Application No. PCT/US2016/054036, dated Nov. 6, 2017, 7 pages. |
| “Notice of Allowance”, U.S. Appl. No. 14/489,288, dated Aug. 25, 2017, 8 pages. |
| “Notice of Allowance”, U.S. Appl. No. 14/533,921, dated Oct. 5, 2017, 9 pages. |
| “Notice of Allowance”, U.S. Appl. No. 14/788,377, dated Sep. 14, 2017, 15 pages. |
| “PTAB Decision”, U.S. Appl. No. 13/898,368, filed Oct. 18, 2017, 6 pages. |
| “Supplemental Notice of Allowance”, U.S. Appl. No. 14/489,288, dated Sep. 8, 2017, 2 pages. |
| “Notice of Allowance”, U.S. Appl. No. 14/788,377, dated Dec. 1, 2017, 13 pages. |
| “Foreign Office Action”, EP Application No. 11871440.1, dated Nov. 21, 2017, 4 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20170104768 A1 | Apr 2017 | US |
