Patent Application
20080226082
1. Field of the Invention
The present invention relates generally to the field of backing up digital content and more particularly to providing security for the backed up content.
2. Description of the Prior Art
Data security is an ever increasing problem. As the volume of digital data and the number of devices, systems and media containing digital data has increased, the risk of inadvertent or unwanted exposure of digital data has likewise increased. This risk is heightened when digital data is backed up to another device or media because this provides yet another opportunity for such exposure. A backed up copy of one's digital data may be as accessible as the device or media onto which the data has been backed up. What is needed is a way to ensure that the backed up data can remain secure even if the device or media itself becomes accessible by others.
An exemplary method of the invention comprises locating, on a first computing system, identification unique to the first computing system, creating a first encryption key using the located first computing system unique identification, storing the first encryption key on a backup device, encrypting, using the first encryption key, a data file from the first computing system, and storing the encrypted data file from the first computing system on the backup device.
In some embodiments, the method further comprises locating again, on the first computing system, identification unique to the first computing system, creating a second encryption key using the again located computing system unique identification, and decrypting, using either the first encryption key or the second encryption key, the encrypted data file from the first computing system stored on the backup device if the second encryption key matches the first encryption key stored on the backup device.
In still further embodiments, the method further comprises storing the first encryption key on an external source.
In yet further embodiments, the method further comprises locating, on a second computing system, identification unique to the second computing system, creating a second encryption key using the located second computing system unique identification, obtaining the first encryption key from the external source, if the second encryption key does not match the first encryption key stored on the backup device, and decrypting, using the obtained first encryption key, the encrypted data file from the first computing system stored on the backup device.
In yet still further embodiments, the method further comprises storing the second encryption key on the backup device, encrypting, using the second encryption key, a data file from the second computing system, and storing the encrypted data file from the second computing system on the backup device.
The present invention also provides a computer readable medium having stored thereupon computing instructions. The computing instructions comprise a code segment to locate, on a first computing system, identification unique to the first computing system, a code segment to create a first encryption key using the located first computing system unique identification, a code segment to store the first encryption key on a backup device, a code segment to encrypt, using the first encryption key, a data file from the first computing system, and a code segment to store the encrypted data file from the first computing system on the backup device.
An exemplary backup device of the present invention comprises a computer readable medium having stored thereupon computing instructions. The computing instructions include a code segment to locate, on a first computing system, identification unique to the first computing system, a code segment to create a first encryption key using the located first computing system unique identification, a code segment to store the first encryption key on a backup device, a code segment to encrypt, using the first encryption key, a data file from the first computing system, and a code segment to store the encrypted data file from the first computing system on the backup device.
The present invention is directed to systems and methods for securely backing up data from a computing system onto a backup device. An encryption key is generated using some identification found on and unique to the computing system. The encryption key is used to encrypt the data which is then stored on the backup device as encrypted backed up data. The encrypted backed up data stored on the backup device can later be accessed, e.g., for data recovery purposes, by once again using the computing system unique identification to generate the encryption key which can then be used to decrypt the encrypted backed up data. Optionally, the encryption key can also be stored on an external source, as described further herein.
Using another computing system to access the encrypted backed up data generally results in failure in that a different encryption key, generated using identification found on the other computing system, will not properly decrypt the backed up data thus maintaining its security.
However, if the encryption key generated from the first computing system was stored on an external source, it can be obtained from that external source and used in decrypting the backed up data using another computing system. Security is maintained by controlling access to the external source.
The systems and methods described herein can be used, for instance, to augment backup applications to provide security for the backed up data. In particular, these systems and methods can be used in conjunction with the backup systems and methods disclosed in the several related applications listed above.
The data being backed up onto the backup device 100 is encrypted to maintain its security. The encryption is performed with an encryption key unique to the computing system 110 because the encryption key is generated from identification unique to the computing system. In this way, a relationship or binding is established between the computing system 110 and the encrypted backed up data on the backup device 100.
The identification unique to the computing system can be any alphanumeric sequence existing on the computing system such as computing system serial number, microprocessor serial number, memory device (e.g., disk drive) serial number, operating system serial number, etc., or any combination or variant thereof.
At a later point in time the encrypted backed up data can be stored back to the computing system 110 from the backup device 100 thus restoring the data of the computing system 110. A user might seek to restore the data to the computing system 110 following the accidental modification or erasure of the data on the computer system 110 as well as after the loss of the data from the computing system 110 due to a computer virus or other malicious attack. It will be understood that the backup device 100 need not remain connected to the computing system 110 during the period between backing up the data and later restoring the data to the computing system 110.
Storing the backed up data from the backup device 100 to the computing system 110 involves decrypting the encrypted backed up data using an encryption key. The identification unique to the computing system 110 is again used to create the encryption key. However, if a user tries to store the encrypted backed up data from the backup device 100 to some other computing system, then identification unique to that other computing system would generate a different encryption key which would not properly decrypt the backed up data. In this way, the encrypted backed up data remains secure even if the backup device 100 containing the backed up data is lost or stolen.
Optionally, the encryption key created when the backed up data is encrypted and stored on the backup device 100 can also be stored on some external source. The external source may be a removable storage device such as a flash memory based “thumb drive.” Alternatively, the external source may be another computing system or server coupled to the computing system via a local area network, wide area network or the internet.
Another possible use of the invention is illustrated generally by
Launching the backup application in step 305 may be triggered by an auto-launch operation as described in the various patent applications listed herein as related applications. Alternatively, the backup application may be launched in the same manner as launching any other computing system application as is known in the art.
The backup application optionally verifies a user in step 310 by requesting a user of the computing system or backup device to enter a password and confirming that it matches a previously entered password. Password creation and user verification can follow any standard approach as is known by one of ordinary skill in the art. Alternative known forms of user verification may likewise be used such as biometrics, etc.
A unique identification of the computing system is then located on or within the computing system in step 315. This may involve reading one or more identification on the computing system. An encryption key is created in step 320 using the located computing system identification. Creation of the encryption key can be performed using any process known in the art.
The backup device is then checked, in step 325, for a previously stored encryption key. If no encryption key is found on the backup device, which would typically indicate that the backup device has not previously been used with the present invention, the encryption key created in step 320 is stored, in step 340, onto the backup device and onto an external source such as a flash memory based device (e.g., a thumb drive) or to a networked computing system as described further herein.
In step 350, the encryption key is then used to encrypt the data being backed up by the backup application and the encrypted data is stored on the backup device. Using the encryption key to encrypt the data being backed up can follow any known encryption approach known in the art.
The encryption key can then be used in step 355 to access the encrypted data stored on the backup device by decrypting the encrypted data using the encryption key, as known in the art. Such access may occur when, for example, a user requests data recovery from the backup device according to a typical backup recovery operation.
Returning to step 325, if an encryption key is found on the backup device, which would typically indicate that the backup device has previously been used with the present invention, a determination is made in step 330 regarding whether the encryption key created in step 320 matches the encryption key found on the backup device. If they match, which would typically indicate a binding of data already backed up on the backup device with the particular computing system, then in an optional step 350 a backup operation is performed including encrypting data being backed up from the computing system and storing the encrypted data onto the backup device. Note that in some situations, such as when accessing already backed up data is the desired result rather than backing up any additional data, step 350 may be skipped.
Finally, the encryption key (either the encryption key created in step 320 or the encryption key stored on the backup device) can then be used in step 355 to access the encrypted data stored on the backup device by decrypting the encrypted data using the encryption key. This access may be for a variety of reasons such as restoring the backed up data to the computing system, simply to read, view or listen to the backed up data, etc.
Returning to step 330, if the encryption key created in step 320 does not match the encryption key found on the backup device, which would typically indicate no previous binding of the backed up data on the backup device with the particular computing system, a determination is made in step 355 as to whether this particular computing system should be added to those being backed up to the backup device (i.e., establishing a binding relationship with this particular computing system). This determination can be made by posing a query to the user in the form of a dialogue box or other known means for a user to indicate their choice of action. If this particular computing system is to be added then the process continues as described above by storing the new encryption key in step 340, encrypting and backing up data files from this particular computing system onto the backup device in step 350, and optionally accessing the encrypted backed up data files on the backup device by decrypting the encrypted data using the new encryption key in step 355.
Alternatively, if the determination made in step 355 is that this particular computing system is not to be added to those being backed up to the backup device (i.e., no new binding is to be established) and instead, for example, the user merely wishes to access previously encrypted and backed up data on the backup device using this particular computing system then, in step 345, the old encryption key is obtained from an external source. As described elsewhere, this may involve asking the user to connect a thumbdrive to the computing system or backup device, providing an address or link to a networked location where the encryption can be found, or simply reading the encryption key from this particular computing system where it was previously stored. Finally, in step 355, the encrypted backed up data files on the backup device are accessed by decrypting them using the obtained encryption key.
The present invention is also directed to a backup device 100 (
The first logical storage area 450 represents a logical area of the computer readable medium 440 that is meant to be inaccessible to the user and safe from accidental erasure. The first logical storage area 450 can contain, for example, a backup application, a look-up table, system files, drivers, and other setup and configuration software. The first logical storage area 450 is represented to the computing system 110 by the emulation component 430 as being an auto-launch device. As used herein, auto-launch devices are those devices that will trigger the automatic execution functionalities of certain operating systems, such as the AutoRun function of the Microsoft Windows operating system.
The second logical storage area 460 represents a logical area of the computer readable medium 440 that is dedicated to storing backed-up data files. Accordingly, the emulation component 430 represents the second logical storage area 460 to the computing system 110 as being a writable computer readable medium. With reference to
It will be appreciated that the Windows Vista operating system allows devices to designate themselves as auto-launching. The emulation components 430, 830 in the backup devices 400, 500, and 800 are therefore optional in those embodiments where these backup devices will be used with Windows Vista or some other operating system that provides similar functionality. In these embodiments, because the backup device can designate itself as auto-launching, the backup application can auto-launch.
In the foregoing specification, the invention is described with reference to specific embodiments thereof, but those skilled in the art will recognize that the invention is not limited thereto. Various features and aspects of the above-described invention may be used individually or jointly. Further, the invention can be utilized in any number of environments and applications beyond those described herein without departing from the broader spirit and scope of the specification. The specification and drawings are, accordingly, to be regarded as illustrative rather than restrictive. It will be recognized that the terms “comprising,” “including,” and “having,” as used herein, are specifically intended to be read as open-ended terms of art.
This application claims the benefit of U.S. Provisional Patent Application No. 60/906,244 filed on Mar. 12, 2007 and entitled “A Method and System for Securely Binding a Backup Appliance to a Trusted Environment.” This application is related to U.S. patent application Ser. No. 11/506,386 filed on Aug. 18, 2006 and entitled “Data Backup Devices and Methods for Backing up Data” which is a divisional application of U.S. patent application Ser. No. 11/492,380 filed on Jul. 24, 2006 and entitled “Emulation Component for Data Backup Applications.” This application is also related to U.S. patent application Ser. No. 11/546,176 filed on Oct. 10, 2006 and entitled “Optical Disc Initiated Data Backup.” This application is also related to U.S. patent application Ser. No. 11/601,040 filed on Nov. 16, 2006 and entitled “Methods for Selectively Copying Data Files to Networked Storage and Devices for Initiating the Same” which is also a Continuation-in-Part of U.S. patent application Ser. Nos. 11/506,386 and 11/546,176. Each of the aforementioned applications is incorporated herein by reference.
| Number | Date | Country | |
|---|---|---|---|
| 60906244 | Mar 2007 | US |
