This application is related to U.S. patent application Ser. No. 09/871,877, filed Jun. 4, 2001 by Bunker, et al., entitled SECURE DATA FILE ERASURE.
The invention relates to data security, particularly in marking devices, such as photocopiers, fax machines, and printers.
Many photocopiers, printers, and other reproduction and printing devices now include non-volatile memory (NVM), such as magnetic and optical storage media and including removable disk systems, hard drives, and other storage media systems allowing the device and/or a user to store a job the device uses or is directed to use the stored job. In high security areas (e.g., military installations), there is often a requirement that all jobs that stored on NVM of a device shall be inaccessible once the job is completed. Additionally, users in lower security area often wish to erase data they would like to keep private or confidential for various reasons.
Lately, secure erase systems that overwrite the data with patterns of 1s, 0s, or random combinations thereof have come into use to meet erasure requirements. However, government agencies and other customers have different requirements as to how many times one can overwrite the appropriate portions of NVM once a job or task is completed, which can lead to difficulties in product design and implementation.
Embodiments of the invention allow a user or a system administrator (SA) to program a device to overwrite the region of NVM in which the data file associated with a print, scan, fax, copy, or other job resides. In embodiments, the data file is overwritten more than once, such as from 2 to about 50 times, with the exact number of overwrites being determined according to a stored default value or a user-input value. Further, in embodiments, the data file can be overwritten with a different pattern on each overwrite according to a stored default value or a user-input value. For example, if a user has just printed something stored on a floppy disk, the user can erase it securely with a sequence of patterns of choice. Instead of trying to settle on a single algorithm (e.g., overwrite 3 times, first time with 1s, the second time with 0s, the third time with a random pattern), this allows overwriting “n” times with a set of patterns that can be downloaded to the device.
Embodiments activate an erase trigger automatically, which places the digital copier or printer into, for example, an Image Disk Erasing Routine, where an Image Disk is a storage media used by the device to store data files including scanned images of documents and/or print job data and the like. An example of such an Erasing Routine is a routine that executes three complete erasures with a check to ensure the data is completely erased; per industry or security approved processes. The Erasing Routine removes or destroys any residual data files including documents, images, and the like, on the Image or ESS Disks. In embodiments, a customer selectable UI/client button with confirmation that the process was completed could activate this routine. During this erasing feature, the system would be offline.
Thus, embodiments provide a storage medium security erase system comprising an erase trigger that tells a drive sector analyzer to retrieve data file location information from a CPU and send the location information to a secure storage medium eraser that overwrites the data file according to a predetermined secure erase method, the eraser using a type of overwrite pattern and a number of overwrites determined by an erase pattern determiner according to predetermined criteria and/or user input.
An additional feature is to apply a method of securely erasing a data file by a providing an erase trigger, determining a location of the data file on the storage medium, overwriting the data file according to a predetermined secure erase method, and determining at least a number of times to overwrite the data file in response to the erase trigger and according to predetermined criteria.
However, it is possible that secure erasure can fail. In such instances, security-conscious users will want to know that failure has occurred. Embodiments provide for such notification and allow implementation of such notification on a UI of a marking device on which failure has occurred, and/or on a personal computer connected to the marking device, such as via a network.
For a general understanding of the present invention, reference is made to the drawings. In the drawings, like reference numerals have been used throughout to designate identical elements.
With reference to the accompanying FIGS., various embodiments of the invention include a device 1, such as a scanner, printer, photocopier, or other device, having a non-volatile memory (NVM) 2, such as a magnetic or optical storage medium, to which the device 1 can store data 3 and/or from which the device can read data 3 stored in a data file 4. The NVM can be a relatively permanently installed hard disk drive, or can be a drive that employs removable media; multiple drives can be used as NVM in embodiments employing combinations of hard disk drives, removable drives, and other NVM. In embodiments, the device 1 can use the data 3 to produce output, such as paper hard copy of a word processing document or the like. When a device 1 experiences a power loss, it will typically check for pending jobs on the NVM 2 when power returns, then complete any incomplete pending jobs.
An example of an erase routine usable in embodiments is illustrated schematically in
With additional reference to
Where more than one pattern 10 is available, a set of patterns 12 can be stored in a storage medium 2 in communication with the system. The set of patterns 12 can be stored in a computer memory or another storage medium in, for example, a table, such as a table resembling the pseudocode expression:
Pattern1, Pattern2, Pattern3, . . . PatternN.
The invention can then use the set of patterns 12, the number of times to overwrite 9, and a pattern selection variable to erase the data file 4 by overwriting. For example, in embodiments of the invention, the user-selected pattern NumPatternToUse to be used and a number of times N to overwrite the data file 4 according to the pseudocode expression:
1 to NumPatternToUse Do
Referring to
As should be readily apparent to one of ordinary skill in the art, the preprogrammed values of NumberOfOverwrites and NumberOfTimesToCycle, as well as the preselected patterns, of the particular processes shown in
Thus, in installations where customers wish to ensure data security, such as high security areas like military installations, customers can meet the requirement that all printed/copied jobs stored on hard drive(s) or other storage media of such devices be inaccessible once the job has completed without removing the storage medium. In addition, many customers simply want to ensure the privacy of their information and wish to erase print and/or copy jobs from storage media on which the jobs might be stored. The current conventional method of deleting a file (deleting the pointers to the data) can still be done, but the method according to embodiments of the invention ensures that data files themselves no longer reside on the disk and can not be recovered.
While particular embodiments have been described, alternatives, modifications, variations, improvements, and substantial equivalents that are or may be presently unforeseen may arise to applicants or others skilled in the art. Accordingly, the appended claims as filed and as they may be amended are intended to embrace all such alternatives, modifications variations, improvements, and substantial equivalents.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5265159 | Kung | Nov 1993 | A |
| 5839033 | Takahashi et al. | Nov 1998 | A |
| 5890188 | Okamoto et al. | Mar 1999 | A |
| 6070174 | Starek et al. | May 2000 | A |
| 6377491 | Otani et al. | Apr 2002 | B1 |
| 6834034 | Yokokawa | Dec 2004 | B1 |
| 6941479 | Sugiura | Sep 2005 | B1 |
| 7072054 | Bunker | Jul 2006 | B1 |
| 20030079078 | Zipprich et al. | Apr 2003 | A1 |
| 20030196100 | Grawrock et al. | Oct 2003 | A1 |
| 20030204747 | Gaebel et al. | Oct 2003 | A1 |
| 20040114265 | Talbert | Jun 2004 | A1 |
| 20060109494 | Kizaki | May 2006 | A1 |
| Number | Date | Country | |
|---|---|---|---|
| 20040114182 A1 | Jun 2004 | US |