Click to See Complete Forum and Search –> : Anti-Forensics tools
Click to See Complete Forum and Search –> : Anti-Forensics tools
Anti-forensics being tools that try to prevent digital forensics and gaining of digital evidence.
So this is more of a personal opinion post than advice.
As far as other tools I use to discourage digital evidence or access to important critical information, I have a media destroyer/paper shredder. Before I throw CDs/DVDs away, I make sure I destroy them. NOt sure if this is considered antiforensics, but I can see how it would be a barrier against people trying to steal any type of data.
for antiforensics you have to look into http://metasploit.com/projects/antiforensics/. They hava a very good presentation on this topic http://metasploit.com/confs/toorcon2005/toorcon_vinnie_2005.ppt
another good read on the topic http://www.informit.com/guides/content.asp?g=security&seqNum=108&rl=1
Talisker anti forensic tools (http://www.networkintrusion.co.uk/foranti.htm)
As far as “anti-forensics” go… I think a pretty popular app is Darik’s Boot and Nuke disk (DBAN)
Price and Usage Restrictions
Price per computer: yes FREE
Price per user: yes FREE
Number of wipes: yes UNLIMITED
Open source code: yes YES
User Rights: yes GPL PROTECTED
Wipe Methods
Quick Erase yes YES
Canadian RCMP TSSIT OPS-II Standard Wipe yes YES
American DoD 5220-22.M Standard Wipe yes YES
Gutmann Wipe yes YES
PRNG Stream Wipe yes YES
Enhancements
8/33/137 gigabyte disk size BIOS limit fix: yes YES
Fast PRNG (Mersenne Twister) yes YES
Entropy Seeding yes YES
Verification yes YES
Logging yes YES
Hardware Drivers
Controllers: XT, IDE, PATA, SATA, SCSI yes ALL
Consoles: Serial, HGA, VGA yes ALL
Buses: ISA, MCA, PCI yes ALL
Platform Support
* Hardware
o DBAN has all available drivers for SCSI disks.
o DBAN has all available drivers for IDE, PATA, and SATA disks.
o DBAN runs on all 32-bit x86-class computers (Athlon, Pentium, and others) with at least 8 megs of memory. If you find an incompatible machine, then please report it.
* Software
o DBAN supports all Microsoft platforms and securely destroys FAT, VFAT, and NTFS filesytems.
+ MS-DOS, Windows 3.1
+ Windows 95, Windows 98, Windows ME
+ Windows NT 3.0, Windows NT 3.1, Windows NT 3.5, Windows NT 4.0
+ Windows 2000, Windows XP
o DBAN supports all unix platforms and securely destroys ReiserFS, EXT, and UFS filesystems.
+ FreeBSD, NetBSD, OpenBSD
+ Linux
+ BeOS
+ QNX
Peace,
HT
There are two concepts here:
1. I have a working computer which I use, then delete evidence of what I did.
2. I want to wipe everything off a hard drive and that retained in the RAM sticks.
I think that your question is about #1…………….so you still have a working computer, but it retains no trace that can be discovered by using computer applications, and leaving the device fully functional?
For example, tools like Darik’s Boot and Nuke will clean a machine for redistribution, but you will trash everything in the process. You would need to install an operating system etc. to get it to work afterwards.
If you need a more subtle solution, you first need to find where program accessible data are stored?
Your definition of the scope of your paper would be helpful.
Anything that will disrupt the validity of the data will work as anti forensics.
Encryption, secure deletion, anonamisers.
I think you need to be more specific.
Anything that will disrupt the validity of the data will work as anti forensics.
Encryption, secure deletion, anonamisers.
I think you need to be more specific.
I ask you guys for your opinion on a broad open topic and you still want more specific details. lol. Encryption, secure deletion, anonamisers, these all are great. And i might even throw the sledge hammer into my paper.
My paper covers specific information about what anti-forensics is, how it can be used, and specific anti-forensics tools. I am working with a partner for this paper who is supposed to cover the first two things, and i am just supposed to write about tools. So you have a broad spectrum of opportunity to explore your favorites list, any books your might have read, and even your common knowledge to provide input to the discussion. No Parameters! As long as it’s something anti-forensics.
Disk wiping to the point of no return, encryption, scripts, booby traps such as the Alias command (http://www.computerhope.com/unix/ualias.htm) in linux to have “ls” really delete something. Whatever.
I can think of things like, booby trapped USPs that trip a disk wipe when power goes off.
Badly trained police is a wide shot but it definitely affect the quality of forensic evidence.
Virtual machines? What if someone carried out their illegal acts from within a VMWare virtual computer?
Most forensics data is discredited in court not through the data itself but through the handling of the evidence by the investigating organisation.
may not have a lot of time to act, what attention has been paid to the idea of
destroying the evidence while the cops are beating the door down?
You know, like in old gangster movies, bookies working in the back room
of the pool hall using paper that will instantly burn when touched with
a lighted cigarette?
I think that you need to go a bit deeper. If I find a PC with a blank hard drive and nothing works, I know what has happened and I know that you are hiding something. That is when it goes to the “clean room” and the rat hunt begins. The only limitation will be my determination and my budget.
The only true “anti forensics” is to pulverise the thing and dissolve the powder in a vat of acid. Then pour the acid down the drain (sorry, tree huggers
So, the first anti-forensic “move” is to persuade the investigator that there is no need to use forensics………………………….the more machines that they have to look at, the easier this is.
So something like “Norton Ghost” or a similar hard drive cloning/mirroring program is actually a potential tool. What you would do is format the drive and then use the cloning/mirroring software to superimpose an apparently innocent system image. That would throw most investigators off, as they wouldn’t see anything to excite their interest and attention. Also, you would have overwritten the drive with valid data.
Please realise that once you have overwritten data, it is gone……….no software program will get it back for you…………it is the “clean room” scenario and you are going to have to look at B]”track overlay”[/B] and “magnetic remnance”
Another potentially ignored anti-forensics tool is on the dark side of the web. Make sure that your box has a good few Trojans and Back Doors on it………….that will probably invalidate any forensic evidence that may be found, as it cannot be proven who put it there.
Then look at USB Drives, R/W CDs and DVDs…………………………You simply load your OS and applications onto these, boot from them, and take them away with you afterwards. The only evidence you will leave behind is in the RAM sticks…………and that needs the “clean room”. A similar scenario is the removable drive…………..so long as there is one in the bay, and it looks plausible, who is to know how many others there are out there?
I ask you guys for your opinion on a broad open topic and you still want more specific details
You are obviously very young and naiive. Wait until you get to deal with lawyers, accountants, doctors and the like……………….it is called “being professional”; we don’t do general questions……….. and we charge like hell
I wrote this tutorial a while back: http://www.antionline.com/showthread.php?threadid=248897
I was looking at a different angle, but the second section (electronic security) might give you some ideas?
I do know that Secret Service agents are very careful about not letting any suspects touch anything once they have entered the house/building/room. They have come across a few people who have set up encryption/destruction programs in case of a bust. Most don’t, though. It is possible that the time and effort is too high, and the risk of accidentally setting it off is too great.
Don’t ask.
You are obviously very young and naiive. Wait until you get to deal with lawyers, accountants, doctors and the like……………….it is called “being professional”; we don’t do general questions……….. and we charge like hell
Are you kidding? I asked for everyone’s opinion and gave a very broad spectrum. There is a time and place for details and documentation and protocol, yes. But this question is not one of those times.
Another thought, is the “hidden drive” concept. This software creates a virtual drive or partition that you need passwords to activate (the example I have needs 4 independent ones) and encrypts the data as well. You need to activate the software to get the virtual drive to show up.
Your average law enforcement type wouldn’t even know it was there
Please take this advice as it is intended………….as a general principle it is a good idea to set a few limits and parameters, as they keep people focussed.
You are trying to write a paper?…………….you have chosen the “tools” section?……….well “tools” are specific to jobs, so you have to be more specific in your questions. It is as simple and as complicated as that………….or do you normally eat your burgers with a monkey wrench?
If you want a resonable response…I don’t think you can honestly reach state #1 that nihil mentions above. Unles you overwrite a disk with multiple passes of random bits, you can’t be certain what informaiton is left on a disk. Even if you use some fancy tool to ferret all the data that you may have left behind, if you’re talking about a Windows machine you can’t be certain what has been written or left behind in the slack space of sectors or fragments of a pagefile.
State #2 is easy. Full wipe/format multiple times, or Big F***ing Magnets (cancer causing hiroshima magnets). Hydrochloric acid and a hammer work well, too.
Do these have to be demonstrated and/or documented methods of preventing investigation?
I can think of things like, booby trapped USPs that trip a disk wipe when power goes off.
Badly trained police is a wide shot but it definitely affect the quality of forensic evidence.
Virtual machines? What if someone carried out their illegal acts from within a VMWare virtual computer?
Most forensics data is discredited in court not through the data itself but through the handling of the evidence by the investigating organisation.
Great idea! LoL I’ve been doing my “research” in vmware for a long time now. *none* of those sessions are recoverable….
However, it seems as if the vmware player does have a bit of spyware in it. Snort picks it up as spyware as it phones home. Simple ACLs to block that though…
May as well ask about “super-sneeky-hacker-f***-you-fed” tactics.
If you want a resonable response…I don’t think you can honestly reach state #1 that nihil mentions above. Unles you overwrite a disk with multiple passes of random bits, you can’t be certain what informaiton is left on a disk. Even if you use some fancy tool to ferret all the data that you may have left behind, if you’re talking about a Windows machine you can’t be certain what has been written or left behind in the slack space of sectors or fragments of a pagefile.
State #2 is easy. Full wipe/format multiple times, or Big F***ing Magnets (cancer causing hiroshima magnets). Hydrochloric acid and a hammer work well, too.
Hey Hey,
I’ve never tried recovery on it… but for nihil’s #1 what about things like PGP’s Free Space Wipe… Randomly Overwrites all your free space X number of times.. What I tend to do is defrag or delete my page file, defrag my drives (C: alphabetically since Windows reads DLLs alphabetically when loading them, and the rest by file access so the most recently accessed files (the ones I most likely use the most) are grouped)… and then run PGP’s Free Space Wipe (usually three passes of random data) on them… when you consider that anything important/incriminating has been encrypted while stored and deleted using something like http://www.sys-shield.com/fileshredder.htm… I’d have to say that I feel reasonably comfortable that no one is recoverying anything I’ve deleted.. but then again I could be wrong and it could be totally recoverable.
Peace,
HT
Your Windows PC stores data in sectors and blocks and writes to them accordingly. So if your blocks are 16Kb and you write an 18Kb file, it will use two block of 16Kb the second of which will have 14Kb of slack space in it. This will still contain the previous data.
Similarly the nodes will contain clues as to what used to be there, even if the original data is gone.
for nihil’s #1 what about things like PGP’s Free Space Wipe.
Those cleaning tools will overwrite the free space, slack space and the nodes (assuming it is a professional quality application).
A good quality erasing tool will overwrite with 0, 1 and random 0s and 1s. It will also do this in a series of random passes . That bit is important, because if the forensic investigator knows the overwriting sequence it is trivial to decompose it.
My methodology would be to use both these tools, format, then ghost/mirror an image of a perfectly innocent system on top, and defragment it.
The investigator will then find what they would expect to find rather than stuff that had obviously been deliberately erased That will make them go away unless they KNOW that there is something of interest on the drive.
This is not as far fetched as you might think. All you would do is boot your machine, create your ghost image on CD/DVD, do your naughty stuff, then go through the cleaning process and ghost the image back again.
This will take a very long time, so using removable media or drives is far more efficient.
I can tell you from my experience in the Defense Sector that we use removable hard drives and that anything that was on the “secure network” is pulverised then incinerated or dissolved. Electronic methods are not trusted, other than for non classified material on the general network.
Incidentally, you will doubtless come across Peter Gutmann and be told that his method overwrites with 32 passes. It doesn’t the true number is 17 or 19 depending on the type of hard drive. The 32 is for applications that cannot figure out what sort of hard drive they are dealing with, and I don’t think that I would trust one of those.
Wiping or erasing disk is only the first step of a complete anti-forensics attempt. The next step you would need to write some random but convincing data onto the same disk that looks like the real data before it’s tampered. Any other step(s)? Be creative…
Erasing disk alone will only raise the flag and make them believe that you really hide something. Erasing disk alone is useful for cases like when a company/organization wants to sell used PCs or disks that had some (confidential) data in them.
Peace always,
<jdenny>
If as the topic stated: - ‘Anti-Forensic tools’ is something you look forward, than the actual skill/knowledge. Then at least you might need to know how all those Forensic tools work in-and-out, in order for you to evade or bypass them. Tools like EnCase Enterprise, ProDiscover IR, OnLineDFS, NetDetector, NetIntercept, CS_MARS, SuperView are the most common tools that professional will use to perform the investigation with. If you can’t avoid being trace or penetrate these tools, don’t even mention anti-forensic.
Another method, you might need to build your very own rootkit to cover your back, and i really mean YOUR OWN~! Modified/tuned it payload, attitute, sequence & signature, to alter the kernel and return false info to system calls, rendering unless most tools that incident responders have traditionally used to examine a live system for signs of compromise. Programs like Hacker Defender might perform similar stuff, but still detectable!!
Next thing you need to concern is those NG-Digital Forensic technique. Forensic Investigator also will improve & upgrade their skill & method, where they notice that “Anti-Forensic” are trying to beat their ass. They will migate to more higer level way of perform forensic. So in order for you to competitive back, you also need to know how to break stuff like Digital Evidence Bag(DEB) or finding weakness at Advanced Forensic Format (AFF) file(e.g.aimage..).
Perhaps you also can try out Metasploit Anti-Forensic Investigation Arsenal (MAFIA) from Metasploit project, which i think its only some basic tools for Anti-Forensic. MAFIA include tools like ‘Timestomp’ - allows modify all four NTFS timestamp values: modified, accessed, created, and entry modified. ‘Slacker’ - allows to hide files within the slack space of the NTFS file system. ‘Sam Juicer’ - A Meterpreter module that dumps the hashes from the SAM, but does it without ever hitting disk. ‘Transmogrify’ - First ever tool to defeat EnCase’s file signaturing capabilities by allowing you to mask and unmask your files as any file type.
Hope this info can help~
You have introduced a whole new concept here. We were telling VAIO about retrospective forensics on a PC, and you have raised the subject of live forensic analysis of an ongoing attack.
That is a very valid issue, and I don’t think that it was considered in the original question, which is why some of us asked for more details on the scope of the paper.
1. A remote access trojan that connects at startup to a host in an unfriendly foreign country.
2. A highly competent forensics expert.
3. A relatively competent lawyer.
The RAT that always makes a connection to a machine that cannot be investigated places significant doubt about the identity of the perpetrator of the crime(s). Your forensics expert can refute or show improper handling of etc. any evidence that the prosecution thinks they can still bring against you and the relatively competent lawyer is the icing on the cake that has the judge dismiss the charges if you even get into the courtroom.
Other than a system such as that then the magnitude of your crime dictates how much effort you put into hiding your activity - But, the magnitude of your crime also dictates the the amount of effort and money the government, (deep pockets), will put into uncovering the evidence of your crime. Even these disk wipers that run multiple passes writing random 1’s and 0’s are not foolproof. The surface of the disk can be investigated with an electron microscope and the orientation of the media can indicate what was written there some time ago. Even Nihil’s “overwrite with a new image”, while possibly making an investigator decide that there is no evidence there and move on, can be read and easily reconstructed.
Now, if your crime is that you are a 16 year old who has been downloading MP3’s left and right then Nihil’s solution is more than enough because the RIAA doesn’t have the brains to look under the lid and if they did it would cost them too much. But rest assured if you are a terrorist or the head of a child porn ring you will be able to hide nothing from them….
One final thought…. If you are committing crimes that would bring down the entire weight of a government upon you, you can be sure of one thing if you are committing said crimes by use of the internet…. All your anti-forensics tools are utterly useless… You won’t even be arrested until they have built their case against you from the traffic they are sniffing at your ISP… The corroborative evidence would sink you… no matter how clean your box might appear…. period.
Antiforensics has been In extreme cases, C4 explosives rigged to a fake power buttons on the computer asset has been cause for concern for law enforcement and military, especially in the case of anti-terrorism. That’s why the likes of the RCMP, FBI and British SAS actually take along bomb sniffing dogs when they are going to cease computer equipment from suspected terrorist cells. Damn scary stuff, glad I only deal with call center reps behaving badly
A number of techniques such as compaction (http://en.wikipedia.org/wiki/Data_compaction) , multiple deletions, shredding, cryptographic and stegnographic methods (BMP hermetic, MP3 bit stuffing) can be used. Most of these have been discussed here by some folks and is covered by the link that you sent for MetaSploit (more notable is M.A.F.I.A. that was mentioned as well).
Here are some other tools:
Deletion: Tracks Eraser Pro (http://www.acesoft.net) , srm (http://srm.sourceforge.net/) , dban (http://dban.sourceforge.net) , Necrofile (http://www.necrocosm.com/products.html), DiskScrub (http://www.secure-data.com/diskscrb.html)
Encryption/Hiding: Steganos Security Suite (http://techgage.com/review.php?id=3784), dm-crypt (http://www.saout.de/misc/dm-crypt/), Cryptainer (http://www.cypherix.co.uk/cryptainerle/), Outguess (http://www.outguess.org/),
ID Hiding: IP spoofing (http://en.wikipedia.org/wiki/IP_spoofing), anonymizer proxies (http://www.multiproxy.org/faq.htm), VPN with RDP, VNC or SSH tunneling, stolen authentication credentials
Extreme Destruction: Explosives, Incinerator, Acid, Microwave
I’d like to see you finished paper, post it when you’re done…
Cheers
My paper is due Tuesday so maybe i will post it up here after that. I’m doing this for my digital forensics class BTW. It’s pretty exciting. But like i said i am working with a partner on the paper and she hardly ever pulls her weight on projects so i am not guaranteeing the first half of the paper to be informative in any way. lol. But if it is anything like the last paper, i might have to end up doing the whole thing myself again. And then i would be more proud of it. I hate group projects when the partner sucks. If she bails out on me this time i’m gonna have to do something about it.
Anyways… thanks for all the great input.
The Royal Canadian Mounted Police have a PDF that details secure harddrive information removal and destruction
http://www.rcmp-grc.gc.ca/tsb/pubs/it_sec/g2-003_e.pdf
Information Technology Security Guide
Lead Agency Publication G2-003
Hard Drive Secure
Information Removal and
Destruction Guidelines
Technical Security Branch
Technical Operations
Royal Canadian Mounted Police
Issued: October 2003
Lead agency publication G2-003
RCMP Technical Security Branch October 2003
Disclaimer of Responsibility
This publication was prepared by the RCMP for the use of the federal government. The publication is
informal and limited in scope. It is not an assessment or evaluation, and does not represent an endorsement
of the technology by the RCMP. The material in it reflects the RCMP’s best judgement, in light of the
information available to it at the time of preparation. Any use which a third party makes of this publication,
or any reliance on or decisions made based on it, are the responsibility of such third parties. The RCMP
accepts no responsibility for damages, if any, by any third party as a result of decisions or actions based on
this publication.
©Copyright 2003 Government of Canada, Royal Canadian Mounted Police (RCMP)
1200 Vanier Parkway, Ottawa, Ontario, Canada, K1A 0R2
This publication may be reproduced verbatim, in its entirety, without charge, for educational and personal
purposes only. However, written permission from the RCMP is required for use of the material in edited or
excepted form, or for any commercial purpose
Lead agency publication G2-003
RCMP Technical Security Branch October 2003
i
TABLE OF CONTENTS
1 Executive Summary……………………………………………………………………………………………………………………. 1
2 Introduction ………………………………………………………………………………………………………………………………. 2
2.1 General……………………………………………………………………………………………………………………………….. 2
2.2 Scope …………………………………………………………………………………………………………………………………. 2
2.3 Objective……………………………………………………………………………………………………………………………… 3
3 Problem definition ……………………………………………………………………………………………………………………… 4
3.1 History ………………………………………………………………………………………………………………………………… 4
3.2 Hard Drive Construction ………………………………………………………………………………………………………….. 4
3.3 Security Definitions ……………………………………………………………………………………………………………….. 6
3.4 Media Destruction Types …………………………………………………………………………………………………………. 7
4 Existing problems ……………………………………………………………………………………………………………………… 9
4.1 Disposal Methods………………………………………………………………………………………………………………….. 9
4.2 Data Recovery Methods ………………………………………………………………………………………………………….. 9
4.2.1 Unerase Utilities ……………………………………………………………………………………………………………… 9
4.2.2 Microscopy……………………………………………………………………………………………………………………. 9
4.2.3 Data Recovery Software …………………………………………………………………………………………………. 10
5 Existing solutions…………………………………………………………………………………………………………………….. 11
5.1 Partial Destruction by National Archives …………………………………………………………………………………… 11
5.2 Re-Use of Hard Drives ………………………………………………………………………………………………………….. 11
5.2.1 Re-Use of Media within the Same Environment…………………………………………………………………… 11
5.2.2 Computers for Schools …………………………………………………………………………………………………… 11
5.3 Running Disk Overwrite Utilities ……………………………………………………………………………………………… 12
5.4 Degaussing………………………………………………………………………………………………………………………… 13
5.5 Hard Drive Destruction ………………………………………………………………………………………………………….. 14
5.6 High-Intensity Heat Application……………………………………………………………………………………………….. 15
6 Proposed solutions & procedures ………………………………………………………………………………………………. 16
6.1 Centralized Physical Destruction …………………………………………………………………………………………….. 16
6.2 Centralized Degaussing………………………………………………………………………………………………………… 16
6.3 Disk Overwrite Utility……………………………………………………………………………………………………………. 17
6.4 Computers for Schools Program …………………………………………………………………………………………….. 17
7 Conclusion………………………………………………………………………………………………………………………………. 19
8 References………………………………………………………………………………………………………………………………. 21
APPENDIX A - Disk Overwrite Software “Conditions For Use (CFU)”…………………………………………………….. 22
Lead agency publication G2-003
RCMP Technical Security Branch October 2003
1
1 Executive Summary
The following is a summary of the guidelines recommended by the RCMP as a result of the findings of this
document:
1.1 For a hard drive containing the following security level of information:
· Protected “A” (Protected) or
· Protected “B” (Protected) or
· Confidential (Classified)
We recommend:
That the drives be “cleansed” by a triple overwrite of the RCMP DSX disk-overwrite software (or
a third-party equivalent that meets RCMP overwrite guidelines). It is important that this process be
done in accordance with the Conditions for Use shown at Appendix A. The drives may then be reused
within the department, or if no longer required they may be donated to Industry Canada’s
Computers for Schools (CFS) program as per Treasury Board policy. Following the triple
overwrite, if it is not feasible to re-use the hard drives or to donate them to the CFS program, the
drives may then be disposed of or the material recycled.
1.2 For a hard drive containing the following security level of information:
· Protected “C” (Protected) or
· Secret (Protected) or
· Top Secret (Classified)
or for a hard drive which is deemed to be non-functioning
We recommend:
That the drives be either:
a. passed through a commercial disintegrator having a ¼ inch residue screen (residue must be
finer than ¼ inch to pass through the disintegrator debris screen),
OR
b. passed through a degausser strong enough to overcome the coercivity of the data contained on
the drive. This degausser must be listed on the National Security Agency (U.S. Department of
Defense) Degausser Products List found at http://www.dss.mil/infoas/degausserlst.pdf or
else obtain an independent laboratory’s confirmation of the maximum Oersteds that can be
degaussed.
Under either procedure the drives are no longer functional at this point - all material may then be
disposed of or recycled.
Lead agency publication G2-003
RCMP Technical Security Branch October 2003
2
2 Introduction
2.1 General
The focus of this guide is to address the problems facing government departments regarding the issue of
cleansing, disposal and destruction of computer hard drives which contain various levels of classified or
protected information. Many departments have questioned, both internally and to the lead agencies, what
can and should be done with disk drives from unserviceable or outdated computers. At first glance this
would not seem to be a significant problem. Unfortunately the same problem that exists for the safe
disposal of other media such as paper, diskettes or magnetic tapes is even more complicated for this media.
It is still up to a department to determine the highest classification of data that should be allowed on a disk
drive but when that drive has to be disposed of and it is determined that there is Protected “C” or Secret
and above information contained, special precautions must be taken. In early 2002, the RCMP sent out a
short questionnaire to all members of the ITSC (Information Technology Security Committee). The ITSC
is composed of the senior IT security personnel of most government departments. The questionnaire asked
five questions relating to hard disk drive disposal:
1) How are your hard drives with Protected “C” or Secret and above information currently
being disposed of within your department?
2) Approximately how many hard drives with Protected “C” or Secret and above information
are currently being stored within your department?
3) If a centralized destruction service was provided would your department use the services?
4) Would your department prefer to do its own destruction?
5) Would your department share in the costs of establishing a central destruction site?
The responses varied in how they dealt with the problem. Most do not deal with much high level
information on hard drives or simply do not allow it on their drives. Some already have a disintegrator in
place. Others use only the DSX disk overwrite software.
The majority were in favour of a centrally located destruction facility as long as a secure delivery service
could be established. As well, most did not want to be responsible for the destruction of their own drives
due to the cost and their limited resources. The sharing of costs was not considered appropriate since it
should be centrally funded.
There is no up-to-date Government of Canada standard which addresses the problem of disk drive disposal.
The Technical Security Standard for Information Technology (TSSIT) (August 1997, Royal Canadian
Mounted Police) does refer to disposal in Section 4.6, and the Security Equipment Guide G1-001 (online on
the RCMP GenNet Web site), provides some guidance. However, comments gleaned from the questionnaire
show there is no continuity in the way drives are handled before disposal. One comment summarized the
feeling of many of the respondents: “If we want a formal program that every one will adhere to it must be
centralized, regulated within (government) security policy and centrally funded. Otherwise the destruction
will not be done properly”. Based on those comments, it would be safe to say that until the problem of hard
drive disposal/destruction is addressed, the risk of secure information being accidentally released will
continue to rise with time.
2.2 Scope
The purpose of this guide is to mainly address the issue of Protected “C” or Secret and above information
contained on hard disk drives. However, the content applies equally to all information contained in IT
media and could be used as a reference for the disposal of all data contained on computer hard disk drives.
Lead agency publication G2-003
RCMP Technical Security Branch October 2003
3
The securing of information at lower levels of sensitivity will also be discussed and recommendations made
for their handling as well. The issue of whether disk drives containing encrypted information should also be
cleansed will not be addressed in this guide. Since encryption methods can vary and their effectiveness over
time can diminish with increased technology improvements, for the purpose of this guide, drives that
contain encrypted information should be dealt with in the same manner as those that are not encrypted. This
guide deals with the hard drive information content disposal problem as it relates to the Federal
Government of Canada and its Information Technology security requirements as dictated by the
Government Security Policy.
2.3 Objective
The objective of this guide is to make recommendations for implementing a standardized process which will
address the following issues:
(1) the requirement to update and expand the RCMP TSSIT standards for media sanitization, and
(2) the proposal for a centralized destruction facility and a centralized degaussing facility.
The disclosure of less sensitive than Top Secret and Protected “C” information could potentially cause
moderate harm or embarrassment to the national interest of Canada or individuals. These standards will
then provide government departments with a viable, safe and cost-effective solution for handling this media.
This guide will also serve as a reference for hard drive functionality and the safe destruction of its contents.
Hopefully it will heighten the awareness of the reader and bring a resolution to the ongoing problem of disk
drive disposal/sanitization once and for all. The intention is for ITSC members to review the
recommendations and if they are found to be satisfactory, the guide will be forwarded for approval by the
IT Management Standards Committee established by Treasury Board and the recommendations
implemented on a timely basis. The RCMP Technical Security Branch would be available to assist in an
implementation plan to establish a working model.
Lead agency publication G2-003
RCMP Technical Security Branch October 2003
4
3 Problem definition
3.1 History
The safe and proper disposal of media containing sensitive information is not a new problem. The issue
now, however, is the changing of media type. Information once contained on paper, microfiche or magnetic
tape is now stored on IT media such as diskettes, CD-ROMs, DVDs, flash memory, memory cards and
hard-disk storage drives. IT media is being made from ever more robust material, yet the technology for its
destruction, or at least its availability, has not kept pace with this progression. As technology has
progressed, the storage capability of this media, especially hard disk drives, has increased exponentially.
This has increased the security risk for two reasons:
· The amount of corporate information which is potentially vulnerable has greatly increased.
· The methods by which this media is disposed of and their standards are still in their developmental
stages.
It can be reasonably assumed that the Canadian government, and industry in general, will continue to use
IT media for storage. Therefore, in order to address the concern of the safety of the information, procedures
and standards will have to be implemented to provide a resolution to this growing problem.
There have been papers and guidelines produced in the past. As mentioned the RCMP previously developed
the Technical Security Standard for Information Technology (TSSIT) which provided guidelines in Section
4.6. The Security Equipment Guide G1-001 (online on the RCMP GenNet Web site) also provides
guidance. Other pertinent publications include Operational Security Standards for Handling Magnetic
Media (Department of National Defence, May 1998) and Clearing and Declassifying Electronic Data
Storage Devices, Version 2 (Communication Security Establishment, September 2000) and Media
Sanitization and Data Recovery Technology Assessment Report (Communications Security Establishment,
March 1998). These reports addressed the need for Government of Canada standards for the proper
cleansing and disposal of hard disk drives. However, until Government of Canada standards are adopted
these reports and standards will not be the same for all government departments or may be interpreted as
suggestions only.
3.2 Hard Drive Construction
In order to better understand why the destruction of hard drive information is of such relevance, it is first
necessary to describe their composition and how easily the information could be extracted.
A hard disk is part of a unit, often called a “disk drive”, “hard drive,” or “hard disk drive,” that stores and
provides relatively quick access to large amounts of data on an electromagnetically charged surface or set
of surfaces.
A hard disk is really a set of stacked aluminium “disks” with a magnetic oxide coating. Each of the disks,
like phonograph records, has data recorded electromagnetically in concentric circles or “tracks” on the disk.
Each track is further divided into sectors, a set of which is called a “cluster”. A sector is addressed by its
track number and sector number. A “head” (something like a phonograph arm but in a relatively fixed
position) records (writes) or reads the information on the tracks. Two heads, one on each side of a disk,
read or write the data as the disk spins. Each read or write operation requires that data be located, which is
an operation called a “seek.” Data already in a disk cache, however, will be located more quickly.
Lead agency publication G2-003
RCMP Technical Security Branch October 2003
5
A hard disk/drive unit comes with a set rotation speed varying from 4500 to 7200 rpm inside a metal
container. Disk access time is measured in milliseconds. Data is written and read by read/write heads,
which are designed to ride on a microscopic cushion of air, without touching the platter. They register bits
from the magnetic coating, which races past them. There will typically be six arms, each with read/write
heads. The synchronous movement of these arms is performed by an electro-mechanical system called the
head actuator. The hard disk data can only be attained via one head at a time. Since a hard disk typically
contains three platters with a total of six read/write heads, the concept of cylinders is employed. Read/write
heads move synchronously. Therefore, data is written up and down from platter to platter. One file can
easily be spread over all six platter sides. Today’s computers typically come with a hard disk that contains
billions of bytes (gigabytes) of storage.
The “hard drive” gets its name from the part that actually stores information: a rigid disk called a platter (a),
which is rotated by a spindle motor (b). To increase storage capacity, most hard drives feature two or more
platters. Information is written to and read from the platter by a read/write head, located in the head stack
assembly (c). An actuator arm (d) holds this assembly in place. In turn, the actuator arm is positioned by upper
and lower magnets, also known as mag plates (e). The mag plates control the movement of the actuator arm across
the platter surface. This movement, along with the spinning of the platter, gives the read/write head access to
specific locations on the platter.
Signals that are read or written by the head are amplified by the read/write preamplifier (f) which, along with the
actuator coil (g) and the associated connectors, make up the flex circuit (h). Near the flex circuit is the airlock (i).
When the drive is powered down, this device locks the read/write head into the “landing zone,” a safe place on the
platter where no information is stored. This helps prevents data loss. These components are encased in a base
casting assembly (j) and a cover (k), which are sealed tightly in a clean room environment. This keeps out dust and
other contaminants that can damage or destroy the drive.
Every drive also contains a printed circuit assembly (PCA) (l). The PCA houses the drive electronics that allow the
Lead agency publication G2-003
RCMP Technical Security Branch October 2003
6
hard drive to communicate with the computer, and allow all of the hard drive components to work in synch.
Among these electronics are a microprocessor that controls all of the drive functions; interface electronics, which
communicate with the computer’s interface bus; a controller ASIC, which operates all of the controller hardware
for the drive; the read channel, which encodes and decodes the data; and a motor ASIC, which drives the motor
and actuator coil.
The read/write head consists of a tiny electromagnet. The shape of the head end acts like an air foil, lifting
the read/write head slightly above the spinning disk. When the disk rotates under the read/write head, it can
either read existing data or write new data.
If a current is applied to the coil, the head will become magnetic. This magnetism will orient the micro
magnets in the track. This is write mode. If the head moves along the track without current applied to the
coil, it will sense the micro magnets in the track. This magnetism will induce a current in the coil. These
flashes of current represent the data on the disk. This is read mode.
The read/write heads are incredibly tiny. In modern hard disks they float between 5 and 12 micro inches
(millionths of an inch) above the disk. When the PC is shut down, the heads are auto-parked in a designated
area of the disk so they will not be damaged during transport. The bits of data are stored in microscopic
magnets (called domains) on the disk. They are written in this manner: before recording data, the drive
uses the read/write heads to orient the domains in a small region so that the magnetic poles all point in the
same direction. A reversal of polarity is interpreted as a digit one. Unchanged polarity is interpreted as a
digit zero.
Although the physical location of a file can be identified with cylinder, track and sector locations, these are
actually mapped to a logical block address (LBA) that works with the larger address range on today’s hard
disks. Essential data is held in three areas of the disk and access to this data is essential to the data recovery
process. These three areas are: partition tables, the boot block and file allocation tables. The partition table
contains the structure of the disk including start and end points, errors and details of corrupt areas. A hard
disk contains a Master Boot Record, a file allocation table, a directory and the data area. The Master Boot
Record contains information about the disk partitions. The boot record is a short program written in
machine code which issues the instructions to load the operating system into memory. It also contains
information about the disk such as the number of bytes per sector and the number of sectors per cluster.
The boot record is stored in the first sector of the first track on a disk or platter containing the active
operating system (e.g. MS-DOS). Once the code for the operating system has been found, the boot record
starts loading that code into memory and then hands over the control to the operating system. The operating
system then completes the boot up process. A contiguous set of cylinders must be allocated for storing the
operating system.
3.3 Security Definitions
Most departments have internal policies relating to the security level of the data to be stored on their
network and its devices. Unfortunately, the understanding of what constitutes the level of designated or
classified information can vary from department to department. Even an individual’s interpretation of the
definition can vary and often data resides on storage media which could, unbeknownst to the author, cause
serious compromise to an organization’s integrity if it were to be exposed. For this reason, there exists
various media cleansing methods which can be utilized with a reasonable level of expectation of its
effectiveness. Since this guide is primarily geared towards the methods for protecting Protected “C” or
Secret and above information on hard disk drives, the focus will primarily be geared toward the disposal of
that information. However, the disposal of other less sensitive information will also be addressed.
Lead agency publication G2-003
RCMP Technical Security Branch October 2003
7
In order to better understand what level of security should be applied to information, it is first necessary to
understand the various security levels as defined within section 10.6 of the Government Security Policy:
10.6 Identification of assets
Confidentiality
Departments must identify information and other assets when their unauthorized disclosure, with
reference to specific provisions of the Access to Information Act and the Privacy Act, could
reasonably be expected to cause injury to:
a. the national interest. Such information is classified. It must be categorized and marked
based on the degree of potential injury (injury: “Confidential”; serious injury: “Secret”;
exceptionally grave injury: “Top Secret”).
b. private and other non-national interests. Such information is protected. It must be
categorized and marked based on the degree of potential injury (low: “Protected A”; medium:
“Protected B”, high: “Protected C”).
(National Interest is defined as the “defence & maintenance of the social, political and economic
stability of Canada”).
The highest security level of the information contained on a disk drive that falls within the realm of these
definitions means that the entire disk drive must be treated as if all of its contents were at this higher
security level.
3.4 Media Destruction Types
Not only is data assigned a security classification but also the type of destruction necessary for the media is
assigned a type. The methods of handling and disposal required for the media will depend upon the
classification of data contained upon it. The principal consideration in the destruction of sensitive material
of all kinds is to make the information indecipherable. The equipment or system used to destroy sensitive
material is rated according to the degree of destruction accomplished and the level of sensitivity of the
material being destroyed.
There are four levels of destruction, as defined within the RCMP Security Equipment Guide:
Type I: Destruction ensures that the molecular structure of the piece of information has
changed to the point where no original pieces of information are in the resultant residue. Methods
include incineration and melting. (Up to and including Top Secret).
Type II: Destruction ensures reducing all sensitive information up to and including Top Secret,
written on media, to a size that is deemed safe to dispose of as unclassified waste. On any one
piece of residue, there shall not be more than one complete alphanumeric character from any one
line and not more than one complete alphanumeric character from the lines immediately adjacent.
There shall not be more than three complete alphanumeric characters on any one piece of residue.
Methods include shredding, disintegration and pulping (for paper). (Up to and including Top
Secret).
Type III: Destruction is also accomplished by mechanical shredders and disintegrators however
the standard is reduced. On any one piece of residue, there shall not be more than three complete
alphanumeric characters from any one line. Methods include shredding, disintegration and pulping
(for paper). (Confidential/Up to and including Protected “B”).
Lead agency publication G2-003
RCMP Technical Security Branch October 2003
8
Type IV: As approved on a case-by-case basis. This level of destruction is provided by
contracted mobile or off-site destruction services. (Case by case basis).
The size of the resulting residue must be reduced and specifications be kept up to date as the media
contains a higher and higher density of data. For this reason, it is best to use the above guidelines since they
are not tied to any specific technology limitation. Although these specifications were developed originally
for paper type media the same criteria can be used for IT media (i.e. destroying media to a limited number
of “bits”). For specific devices recommended for the destruction of IT media (by type), the RCMP Security
Equipment Guide is now available online through GeNet at http://www.rcmp-grc.gc.ca/tsbgenet/
seg/guide/destruction_e.htm.
Lead agency publication G2-003
RCMP Technical Security Branch October 2003
9
4 Existing problems
4.1 Disposal Methods
The RCMP has been approached on numerous occasions by federal government departments for a
proposed solution to the problem of hard disk disposal or cleansing. Departments often send their outdated
or unused computers offsite to schools or other organizations. The contents of the hard drives of these
computers is of concern and the correct method of dealing with it requires analysis. Likewise, if a drive is
found to be non-serviceable or in need of repair, it must be properly cleansed before being sent offsite.
The U.S. Assistant Secretary of Defense has published the directive Disposition of Unclassified DoD
Computer Hard Drives (June 4, 2001). The directive addresses four methods and procedures for sanitizing
and clearing hard drives. The four methods are: disk overwrite utilities, degaussing (demagnetizing),
physical destruction and clearing data (deleting files). Their recommendations were taken into consideration
in the development of this paper.
The Canadian Department of National Defence (DND) has published its own Operational Security
Standards for Handling Magnetic Media (May 15, 1998). This standard and the Communications Security
Establishment publication Clearing and Declassifying Electronic Data Storage Devices, Version 2.0
(September 2000) were referenced in an effort to find common guidelines in order to produce
recommendations bearing an industry-wide approval rating at a federal level.
The Universal Secure Overwrite (USO) standard which is being developed within the United States has yet
to be released. This standard will determine the proper procedures of overwriting hard disk drives.
Individual manufacturers are expected to adopt this standard once it becomes available so that the selfsanitization
software will be built in the hard drives.
4.2 Data Recovery Methods
Depending on the level of need and the financial resources available to recover data from a disk drive, the
ability to recover information could be extremely costly and time consuming or it could be as simple as
running commercially-available data recovery software.
4.2.1 Unerase Utilities
Data is stored in random fashion on a computer. Computers use a FAT (File Allocation Table) to track the
used and unused portions of a disk. Since files are not normally stored contiguously on a disk, the FAT
keeps track of where each part of a file is stored on a disk. When data is deleted it is simply removed from
the file allocation table thereby marking those sectors as available to store new data. Until new data which
is stored in a random fashion on the disk is written to each and every sector that housed the deleted data,
portions of that data are recoverable. There are software utilities commercially available which will provide
access to this data which the user thought was “erased”.
4.2.2 Microscopy
Until it is overwritten several times potentially important information can be retrieved from a computer.
Using magneto-resistive microscopy (also known as magnetic force microscopy (MFM)) it is possible to
recover portions of this data. The technique is derived from scanning probe microscopy (SPM) and uses a
sharp magnetic tip attached to a flexible cantilever placed close to the surface of the disk where it interacts
with the emanating stray fields. An image of the field is formed by moving the tip across the surface and
Lead agency publication G2-003
RCMP Technical Security Branch October 2003
10
measuring the force in relation to its position. There are variations to the process but the end result is the
same. Even a relatively inexperienced user can start getting images of the data on a drive platter in
approximately five minutes. According to manufacturers’ sales figures there are several thousand SPMs in
use in the field today. If commercially available SPMs are considered too expensive it is possible to build a
reasonably functional one (less than $2,000 U.S.) using a PC as a controller.
Truly deleting data from magnetic media is very difficult. When data is written to the medium, the write
head sets the polarity of most, but not all, of the magnetic domains. This is partially due to the inability of
the writing device to write in exactly the same location each time, and partially due to the variations in
media sensitivity and field strength over time and among devices. Deviations in the position of the drive
head from the original track may leave significant portions of the previous data along the track edge
relatively untouched. Newly written data is often superimposed over previously recorded data which
persists at the track edges. Each track contains an image of everything ever written to it, but the
contribution from each “layer” gets progressively smaller with each overwrite.
4.2.3 Data Recovery Software
A number of commercial products and services are available which will recover or attempt to recover data
from a disk drive using commonly available or proprietary algorithms. (e.g. a product such as “EnCase”).
Depending on the situation, you can often rebuild the master and partition boot records (MBR, PBR) and
FAT of the hard drive, and you can find and recover lost or damaged files and directories.
The success of the recovery depends on the extent of the damage to the media or the effectiveness of the
means used to delete the data. While there is a strong likelihood that these products will recover a specific
drive, there are some drives that cannot be recovered. The data can be missing, written over, fragmented or
scrambled in a way that makes recovery virtually impossible for a single software tool. The drive may be
electronically or mechanically damaged, making recovery impossible without tearing the drive apart in a
clean room, replacing components, and then trying to bring the drive up.
The exact methodology used for data recovery is usually a trade secret and the cost is often directly related
to the time and effort required for the recovery. The cause of the data loss, overwrite as opposed to a
damaged disk, greatly influences the cost as well. In fact, it was determined that recovery of data damaged
by an overwrite utility was not a feasible solution at most recovery services and that the drives be taken to
specialized laboratories where microscopy techniques are utilized. The cost of microscopy techniques
would certainly be prohibitive to the majority of the population due to its cost and specialized expertise.
Also, the probability of substantial recovery is extremely low given all of the factors listed in the previous
section.
Lead agency publication G2-003
RCMP Technical Security Branch October 2003
11
5 Existing solutions
5.1 Partial Destruction by National Archives
The RCMP visited the National Archives site at Tunney’s Pasture in January 2002. A tour was given of
the facilities and their present disposal methods for both paper and IT materials. In respect to the IT media
disposal, they presently dispose of tapes, diskettes and CDs (up to Protected “B”) by having it ground up
through an SEM (Security Engineered Machinery) disintegrator. This disintegrator however is not robust
enough to handle the destruction of hard drives. Their present means of destroying disk drive media
consists of drilling three or four ¾-inch holes through the disk assembly and then sending it to a local metal
recycling plant (Bakermet) where it is pulverized into three to five inch pieces. The resulting products are
then sent to a steel mill for remelting. The recycling employees are all security cleared.
5.2 Re-Use of Hard Drives
5.2.1 Re-Use of Media within the Same Environment
The RCMP TSSIT Guide has recommendations regarding the re-use of IT media in the same environment
where confidentiality is a concern. These are contained in Appendix OPS-III (page 1). Specifically it
recommends that “media can only be re-used for the same level of sensitivity or above.”
5.2.2 Computers for Schools
Computers for Schools, an Industry Canada program, will pick up unwanted or outdated but functional
computers from government departments/private companies and ship them to schools. The federal
government-led program operates in cooperation with the provinces and territories and the private and
volunteer sectors to collect, repair and refurbish donated surplus computers from government and private
sector sources. The computers are then distributed free to Canada’s schools and libraries after the RCMP’s
DSX Disk Wipe Utility is run on the hard drives.
It is mandatory for Government of Canada departments to offer their surplus computers to the Computers
for Schools program, as per the Appendix, Section 8.2.2 of the Treasury Board policy Disposal of Surplus
Moveable Crown Assets which reads:
8.2.2 All personal computers (MS-DOS/Windows and MacIntosh) and associated monitors, keyboards,
mice, printers, modems, servers, hubs, network cards, disk operating systems and related equipment
which become surplus to government requirements must be offered intact to the Industry Canada
Computers for School Program. Custodians are not authorized to sell, trade, donate or otherwise dispose
of these assets prior to making this offer. Custodians are responsible for disposal of any equipment that is
not accepted by the CFS Program.
Also in the same Appendix, Section 8.2.3 states:
Custodians should ensure that surplus computers are not ‘cannibalized’ or otherwise rendered unusable
prior to transfer. The practice of removing hard drives, random access memory (RAM and other essential
components from computers before transferring them should only be done in those rare situations where
security requirements dictate it”.
It is strongly recommended by the RCMP to run the DSX utility before computers are sent to the
Computers For Schools Program to ensure the confidentiality of data. No data higher than Protected “B”
should reside or have previously resided on these drives before leaving the client department. In order to
Lead agency publication G2-003
RCMP Technical Security Branch October 2003
12
ensure the successful elimination of secure information, CFS uses the RCMP DSX disk overwrite utility at
the triple overwrite setting.
The reason for the success of the CFS program is its cost-effectiveness. In order to ensure this continues,
hard drives must be included with the computers they receive. However, for the very limited number of
machines (less than 5%) whose drives contain Protected “C”, Secret, or Top Secret information, it is
recommended that those drives be destroyed as per our recommendations.
5.3 Running Disk Overwrite Utilities
There is commercially available software available which will entirely overwrite a computer hard disk
multiple times. One would think that the more times the overwrite, the more difficult the recovery.
However, more than three overwrites generally buys little if any added benefit. Multiple overwrites are
likely to track one upon the other and if the recording head has been shifted such that it is leaving trackedges,
then multiple overwrites will do little to eliminate them.
The general concept behind an overwriting scheme is to flip each magnetic domain on the disk back and
forth as much as possible (which is also the basis behind degaussing) without writing the same pattern
twice in a row. Magnetic media must be overwritten many times with alternating patterns in order to erase
it. There is a complication in that the disk surface must be saturated to the greatest possible depth. Very
high frequency signals only scratch the surface of the magnetic medium. Disk drive manufacturers use the
highest possible frequencies in order to achieve ever-higher densities but in order to do an effective
overwrite, the lowest possible frequencies are required in order to penetrate as deeply as possible into the
recording medium. The write frequency also determines how effective previous data can be overwritten.
The track write width is also affected by the write frequency - the track width decreases as the write
frequency increases.
Some recording media are magnetically harder than others. For this reason, drive manufacturers publish
figures for the magnetic “hardness” of their media and call this their coercivity. They use two units to
express their coercivity. The original Oersteds (Oe ) (named for H.C. Oersted 1777-1855) or alternatively
the present day kiloamperes per metre (kA/m). The media coercivity (its bonding capabilities) also affects
the width of the write and erase bands. The width drops as the coercivity of newer higher-density drives
increases.
In order to understand the theory behind the choice of data patterns to write for an effective disk overwrite
it is necessary to understand the recording methods used in disk drives. The head itself only detects
transitions in magnetisation so the simplest recording code uses a transition to encode a 1 and the absence
of a transition to record a 0. Since putting a long string of zeros would make clocking difficult, a limit is
made on the maximum number of consecutive zeros that are written for data patterns to be used for the
overwrite.
The RCMP offers a disk overwrite utility, called DSX, free of charge to all government of Canada
departments and agencies. It was developed in-house and allows for a single or triple pass overwrite. When
the triple pass option is selected, binary 0s are written on the first pass, binary 1s on the second pass and an
ASCII text pattern composed of the DSX version number and date/time stamp for the third pass. Each
overwrite pass is followed by a read verify pass. Media I/O errors are reported and diagnosed at the sector
level.
Lead agency publication G2-003
RCMP Technical Security Branch October 2003
13
Where disk errors occur it is conceivable that intelligible information remains in areas not successfully
overwritten. If the capacity of the disk to be overwritten, as reported by DSX, is less than the
manufacturer’s specifications, the excess portion will not be overwritten. This difference in reported size
could either be an intentional deviation or a technical misrepresentation. This software does not currently
support the UNIX operating system but there is such commercially available software which will perform
similar functions.
There are three possible shortcomings to the effective use of Disk-Overwrite utilities. They are: human
error, software failure and data remnants.
Human error or software failure can be caused by improper running of the overwrite software and the
assumption that the software ran thoroughly when in fact it did not. Appendix “A” of this guide outlines the
“Conditions For Use (CFUs)” for the proper usage of a Disk-Overwrite utility.
Data remnants can occur at track boundaries (edges). The disk read/write heads do not always pass
concentrically over the exact or original bit pattern due mostly to mechanical and electrical variables and
tolerances. The result is that residual “track edges” of the original bit patterns are generally left on the disk
platter even though the bulk of the track will have been overwritten. The microscopy techniques described
above can be used to image these edges. Depending on the number and remnant quality of these edges,
processing can be done on them to reconstruct the original (overwritten) bit patterns of information. In
order to ensure that residual track edge phenomena are not present on a disk, it is essential to perform
deliberate +/- overwrites which extend beyond the original track edges. Standard disk controller firmware
does not provide this type of offset control at this time. In effect, overwriting can never be 100%; some
unknown technique may one day be able to restore data.
Blocks or clusters of data that show damage are eventually marked as bad and this can be done by the
software itself. (i.e. SCSI hard drives) or by software (the operating system). In many cases, it is
impossible to “scrub” bad blocks (the hard drive itself makes them inaccessible). This is where the drive
must by physically destroyed or degaussed.
5.4 Degaussing
Degaussing (or returning the recording media to its original state) is an alternative means of erasing media
which requires specialized equipment. It is possible in most equipment to erase data by passing the medium
across an erase head but this normally would be a lengthy process. It is speedier and much more practical
to submit the medium to a field which can be made to demagnetize it in one short operation. This is
achieved by subjecting it in bulk to a series of fields of alternating polarity and gradually decreasing
strength. Equipment capable of doing this is called a degausser. Its function is to reduce to near zero the
magnetic flux stored in the magnetised medium. Flux density is measured in Gauss or Tesla. The
degaussing field is produced by passing an alternating current through coils which energize the erase heads.
It is considerably stronger than the field used in the original recording and magnetises the medium
alternately in opposite directions each half cycle. The degaussing field is measured in Amps/metre. During
the process, the media item is passed at a slow constant speed across the heads and out of their erasing
fields. This is similar in many respects to a car slowly progressing through the water mist in an automatic
car wash. The erase field is automatically controlled by the unit as the operator loads and processes the
media. However, the operator is still responsible for ensuring that the media is positioned correctly and that
the full erase process is completed. It is achieved by controlling the speed at which the screened drawer
containing the media unit is closed and then withdrawn. In other words, the speed of movement of the
drawer plays a critical part in the degaussing procedure.
Lead agency publication G2-003
RCMP Technical Security Branch October 2003
14
Bell Laboratories in the USA introduced the unit “bel” named after Alexander Graham Bell, the inventor of
the telephone. A unit of one bel was applied to any measurement of sound related to the ear. The bel means
simply “twice as loud as another sound “. For practical purposes the smaller unit the decibel or dB was
employed. A base reference 0dB was introduced, the value of which was dependent upon the type of sound
measurement being made, e.g. sound pressure or electrical energy.
Degaussing will work through most drive cases. Research has shown that the aluminium housings of most
disk drives attenuate the degaussing field by only about two decibels. For typical disk drive media, the
short-term field needed to flip enough of the magnetic domains to be useful in recording a signal is about
1/3 higher than the coercivity of the media. Coercivity, measured in Oersteds (Oe) is a property of magnetic
material and is defined as the amount of field necessary to reduce the magnetic induction in the material to
zero - the higher the coercivity, the harder it is to erase data from the medium.
Each type of magnetic media is distinguished by the rate of coercivity required to ensure the medium is
brought back to its zero state. Due to the variations of media formats and their corresponding magnetic
densities, a correct and effective degaussing process is often difficult to achieve. Coercivity strength of an
applied magnetic media determines which type of degausser should be applied to the particular magnetic
media being targeted for sanitization. Higher coercivity rates are usually required to degauss hard disk
storage media and many degaussers designed for commercial use do not have the magnetic energy required
to erase media with a higher coercivity rate.
Degaussing often destroys the hard drive’s timing tracks and servo motors, and usually demagnetizes the
permanent magnets of the spindle motor on sealed drives. Thus they can seldom be used after degaussing.
5.5 Hard Drive Destruction
Destruction of a hard drive is the process of physically damaging a media so that it is not usable in a
computer and so that no known exploitation method can retrieve data from it.
The level to which destruction of the drive needs to be conducted is a matter of debate or need. A hard drive
could be made inoperable by physical force such as the drilling of holes (as is done at National Archives) or
hammering that will disfigure, bend, mangle or otherwise mutilate the hard drive so that it cannot be reinserted
into a functioning computer. It could be sent to a metal destruction facility (i.e. smelting,
destruction or pulverization). Application of a concentrated abrasive substance such as sanding or grinding
of the disks’ recording surface can be effective but is more labour intensive, including disassembly to gain
access to the drive’s surface.
The most physically effective, environmentally sensitive and cost-effective method of physical destruction
of hard drives would appear to be destruction by industrial quality disintegrators. These machines feature
interchangeable waste sizing security screens and use a fast, dry mechanical cutting process to shred the
average size disk drive assembly. Using rotating blades of varying cutting durability and strength, these
devices grind the metallic drives small enough to fall through a screen sized by a user’s requirements. Disk
drive assemblies could be reduced to a size of ¼ of an inch with an extremely high level of confidence that
the confidentiality of the information on those drives would not be compromised.
Realistically, data is distributed throughout a platter or perhaps multiple platters of a disk assembly. In
order to make meaningful sense of information extracted from these platters, it would more than likely be
necessary to know the exact location of this information throughout the platters to create a contiguous,
Lead agency publication G2-003
RCMP Technical Security Branch October 2003
15
logical reconstruction of the original data. Even if it were possible to reconstruct the File Allocation Table
(FAT), it would be virtually impossible to reassemble the thousands of metal fragments (and disregard the
other non-platter contents of the drive assembly) to re-create the original platters in order to locate that
data. The media would also have to be reconstructed such that it could be mounted again and spinning at
the correct speed to extract the information. A proper threat/risk assessment would be necessary, of course,
to measure the risk of this happening. Also, the level of security of the data contained on the media would
have to be determined. However, the probability of reconstruction would still remain extremely low. In
order to be 100% sure, the media could be destroyed to the molecular level (e.g. melting via heat or
chemical breakdown utilizing acid). Neither of these two solutions is environmentally sound but is worth
consideration. Degaussing and/or using an overwrite utility could also be utilized beforehand to augment
the effectiveness of the disintegration.
5.6 High-Intensity Heat Application
The RCMP Explosives Disposal and Technology Section (EDTS) has developed a Hazardous Material
Portable Thermal Burner for the purpose of destroying ammunition, drugs, exhibits, tobacco, etc. They
have proposed that it could be modified to allow for up to three trays of 40 disks (120) to be subjected to
intense heat for a cycle time of 30 minutes. The heat produced would be from 800 to 1200 degrees
Fahrenheit which should be sufficient to alter the molecular structure of the drives enough to remove all
data from the drives. However, this would have to be tested and verified by an independent laboratory. The
drives would not be operational after this process and would have to be disposed of in a waste disposal
facility, possibly after they have gone through a physical destruction process as an added insurance. The
cost of running the burner would be minimal since the three propane tanks equipped with the device have a
total burning time of approximately 15 hours.
Lead agency publication G2-003
RCMP Technical Security Branch October 2003
16
6 Proposed solutions & procedures
6.1 Centralized Physical Destruction
As previously discussed, the RCMP met with the National Archives of Canada, represented by the Head of
their Reference and Disposition Services, a Disposition Officer and a Reference Processing Officer, to
discuss the idea of centralized destruction. A tour was given of their current operations and they were
questioned on their ability to provide an extension of their current destruction facilities to include hard disk
drives. At the time it was thought that with proper funding for the increased staff and updated shredder
technology they would be receptive to expanding their destruction services to include computer disk drives.
Unfortunately, upon further discussion, they felt it was not a strategic direction they were prepared to
undertake at this time.
At a subsequent meeting of the Information Technology Security Committee (ITSC) a proposal was made
for a business case to be submitted to Public Works and Government Services Canada (PWGSC) for their
analysis concerning the establishment of such a facility. This is currently under development by the RCMP
in conjunction with CSE.
The expense of running a centralized media destruction facility for all government departments would
offset the cost of every department having to run their own. Departments could either store the drives onsite
until they were ready to ship them to the centralized location or send them on an as-needed or regular
schedule. Client departments currently arrange for their own secure delivery of paper products for
shredding and it would be logical for this arrangement to continue for the process of disk drive/media
destruction. Upon running the drives through the shredding machine at a centralized location, the resulting
material would be safe enough for disposal at a smelting plant or landfill site. The cost of providing a
centralized facility would include the purchase of a suitable machine, setting up the proper environmental
conditions (including air filtration and noise reduction) and the staffing of the positions to carry out the
process. The machine would require regular maintenance and the blades would have to be replaced/resharpened
as necessary. The clients would run a disk overwrite utility on the drives, if physically possible,
before sending them away for destruction. If not possible to run the disk overwrite utility, it would be
imperative for the drives to be securely delivered to the facility.
It is proposed:
That, due to processing time factors, costs and limited instances of destruction requirements
for this classification of material, the central destruction of IT storage media only be necessary
for Protected “C” or Secret and above information, and that the media be first run through the
centralized degaussing facility.
6.2 Centralized Degaussing
Likewise, the expense of purchasing and running a centralized degausser for all government departments
would offset the cost of every department having to run their own. A unit could be purchased and run with
one or two operators. Again, the exact costs would be determined by the robustness of the machine, its
environmental requirements and the required technicians. A bonded and security-cleared courier could be
used for transporting the drives to the centralized location where they would be degaussed on a scheduled
or ad hoc basis by security-cleared technicians. The unit would be of a high enough rating such that it
would provide ample Oersteds to erase any size of disk drive.
Lead agency publication G2-003
RCMP Technical Security Branch October 2003
17
As technology improves and the recording density on disk drives increases, the strength of the unit would
be reviewed on a yearly basis and it would be upgraded as necessary. When properly applied, degaussing
would render any previously stored data on the hard drive media unreadable. Persons performing the
degaussing function would have to be properly trained and certified. Because of its physically destructive
nature, degaussing would only be used on drives which were not intended to be reused.
The delivery to the centralized degaussing facility would be the same process as that described for
destruction above. The clients should run a disk overwrite utility on the drives, if physically possible,
before they are sent away for degaussing. If this is not possible, it is imperative that the drives be securely
delivered to the facility.
It is proposed:
That, due to processing time factors, costs and limited instances of degaussing requirements for
this classification of material, the centralized degaussing of IT storage media only be necessary
for Protected “C” or Secret and above information.
6.3 Disk Overwrite Utility
The RCMP will continue to offer its disk overwrite software (DSX) to government departments free of
charge with limited support. Departments wishing to use the RCMP DSX Disk Overwrite Utility would
continue their practice of contacting the Technical Security Branch to have a copy created for them. One
copy would be provided per departmental security officer for distribution within the department. Updates
can be sent either via email or via regular mail. It would be the responsibility of the departments to contact
the RCMP for any updates to the DSX software or to change their contact person within the department.
This software is not suitable for declassifying hard disks and the user assumes all risks for the improper
usage of the software whether intentional or accidental. As mentioned, the risks could include the
possibility of residual data still being available for extract given the right circumstances and the
determination of the attempt to extract.
It should also be noted that overwrite utilities such as DSX only work if the drive is functioning properly. If
there is a physical drive problem, then another method of removal/destruction will be required. In this case
hard drive destruction and/or degassing is recommended. This would however permanently damage the
hard drive and any existing warranty for the drive would most likely be voided. For these limited
conditions, this loss would have to be considered a monetary loss necessary to enforce departmental
security.
It is proposed:
That the DSX software (or equivalent) is suitable for the erasure of up to and including
Protected “B” (for protected information) and is suitable only for Confidential (for classified
information), when the “Disk Overwrite Utility Conditions For Use” (see Appendix A) are
followed. The resulting “cleansed” drives could then be re-used but preferably in the same
environment of the same department and only for storage of data of the previous security level
or lower.
6.4 Computers for Schools Program
Government departments must continue to send their surplus computers to Industry Canada’s Computers
for Schools program. As proposed below, those very limited number of computers which have or
Lead agency publication G2-003
RCMP Technical Security Branch October 2003
18
previously contained very sensitive material must have their hard drives dealt with in the manner explained.
All others - the majority - should first run the RCMP DSX (or equivalent) Disk Overwrite utility to
overwrite the hard disks in these computers before sending them to Industry Canada. Labels should then be
attached to the devices identifying them as being “Overwritten By Department”. Industry Canada must still
run the utility again upon receiving them before sending them for use to the various school boards.
It is proposed:
That Industry Canada’s Computers For Schools Program continue to receive surplus computers
from Government departments as per Treasury Board policy. The hard drives in these
computers must not have previously contained Protected “C” or Secret and above information.
All drives, no matter the security classification, must be functional to the degree that a Disk
Overwrite utility can be run on them and if that is not possible, they also cannot be given to the
program. Those few drives that don’t qualify for the program must be disposed of separately via
the proposed destruction/degaussing facility. All other drives are acceptable within the donated
computers but only if they are functioning and have been through a triple-overwrite Disk
Overwrite utility with a “Overwritten By Department” identifier on them before leaving the
client department. Industry Canada is still required to run an overwrite utility as per their
current pre-distribution process.
Lead agency publication G2-003
RCMP Technical Security Branch October 2003
19
7 Conclusion
Only the user knows the importance of his/her data. That is why it is so vital that a Threat/Risk Analysis be
completed by a department to determine the sensitivity of the data they handle. In the case of hard drives,
one must look at the probability of information being extracted from a drive. If a drive is degaussed and/or
overwritten with a utility and subsequently put through a disintegrator, what is the likelihood of the
resulting shards of metal ending up in the wrong hands with the right equipment and technology? Or if only
a Disk Overwrite Utility is used for cleansing the disk, what are the odds that someone will have the
technology, knowledge and good fortune to be able to extract residual data from these platters? And what
are the odds of someone locating secure information on that material given that data is spread out over one
or more platters? What would be the risks to a government department or individual if this information
were to be made available to the general public or covert entities?
It would appear from the results of the original survey sent out to the ITSC that there is a limited amount of
highly sensitive information contained on hard drives. This would result in a limited amount of labour for
both degaussing/overwriting and physically destroying the drive. Therefore, we recommend the following:
7.1 For a hard drive containing the following security level of information:
· Protected “A” (Protected) or
· Protected “B” (Protected) or
· Confidential (Classified)
We recommend:
That the drives be “cleansed” by a triple overwrite of the RCMP DSX disk-overwrite software (or
a third-party equivalent that meets RCMP overwrite guidelines). It is important that this process be
done in accordance with the Conditions for Use shown at Appendix A. The drives may then be reused
within the department, or if no longer required they may be donated to Industry Canada’s
Computers for Schools (CFS) program as per Treasury Board policy. Following the triple
overwrite, if it is not feasible to re-use the hard drives or to donate them to the CFS program, the
drives may then be disposed of or the material recycled.
7.2 For a hard drive containing the following security level of information:
· Protected “C” (Protected) or
· Secret (Protected) or
· Top Secret (Classified)
or for a hard drive which is deemed to be non-functioning
We recommend:
That the drives be either:
a. passed through a commercial disintegrator having a ¼ inch residue screen (residue
must be finer than ¼ inch to pass through the disintegrator debris screen),
OR
b. passed through a degausser strong enough to overcome the coercivity of the data
contained on the drive. This degausser must be listed on the National Security Agency
(U.S. Department of Defense) Degausser Products List found at
http://www.dss.mil/infoas/degausserlst.pdf or else obtain an independent
laboratory’s confirmation of the maximum Oersteds that can be degaussed.
Lead agency publication G2-003
RCMP Technical Security Branch October 2003
20
Under either procedure the drives are no longer functional at this point - all material may then be
disposed of or recycled.
7.3 Summary
To summarize, departments/agencies are ultimately responsible for the integrity, availability and
confidentiality of their information. In order to ensure these qualities, Government of Canada standards
must be developed for the erasure, destruction and disposal of all hard drives and other magnetic storage
media. Failure to do so could result in a department or the Government of Canada being subjected to
embarrassment, irreparable damage to their reputation or even pose a serious threat to the stability of its
infrastructure or the safety of its employees and Canadian citizens.
In closing, here is an excerpt of the statement made on September 6, 2000 by Mr. Michael Robert Overly
to the Subcommittee on the Constitution of the Committee on the Judiciary, U.S. House of Representatives.
Mr. Overly is a well-respected expert on information technology storage and its legal repercussions. He
was a research engineer for many years in the defence industry. He is an attorney and the author of the
well-known reference book Overly on Electronic Evidence. He was called before the Subcommittee to
present his opinion on a plan to adopt clear policies regarding employees’ use of computer resources:
“Businesses have three general areas of concern regarding employee use of their computer resources:
(1) minimizing potential liability of the business to its employees or third parties; (2) protecting sensitive
business information from unauthorized disclosure; and (3) reducing potential waste of computer
resources. These concerns require businesses to have the ability to monitor and review employee use of
their computer resources to insure those resources are used properly.
Employees, on the other hand, generally evidence a profound lack of appreciation of the potential
liability that may arise from use of their employer’s computer resources, particularly e-mail. Much of the
problem results from the incorrect perception of most employees that their electronic communications are
entirely ephemeral in nature: existing for only a short time and then permanently erased. Nothing could
be further from the truth. Records of e-mail and computer use may be maintained for many years. Even
deleted messages and files may be retrieved weeks or months after they were thought deleted.”
Lead agency publication G2-003
RCMP Technical Security Branch October 2003
21
8 References
1) Government Security Policy (GSP), February 1, 2002, Treasury Board of Canada Secretariat
2) Technical Security Standard for Information Technology (TSSIT), August 1997,
Royal Canadian Mounted Police
3) Beyond Fingerprints - Recovery of Electronic Evidence
http://www.ontrack.com/datatrail/beyondfingerprints.pdf
4) Disposition of Unclassified DoD Computer Hard Drives, U.S. Department of Defense
(June 7, 2001)
http://www.defenselink.mil/nii/org/sio/ia/diap/documents/ASD_HD_Disposition_memo060401.pdf
5) Destruction of DoD Computer Hard Drives Prior to Disposal (January 8, 2001)
http://www.defenselink.mil/nii/org/cio/doc/computerdisposal.pdf
6) Operational Security Standards for Handling Magnetic Media, Canada Department of National
Defence, May 15, 1998
7) Media Sanitization & Data Recovery Technology Assessment Report, Communications Security
Establishment, March 31, 1998
Clearing and Declassifying Electronic Data Storage Devices, Communications Security
Establishment, September, 2000.
9) Digital Archaeology: Rescuing Neglected and Damaged Data Resources
http://www.ukoln.ac.uk/services/elib/papers/supporting/pdf/p2.pdf
10) Hard Disk Overwrite & Inspection Utilities for IBM-PC & Compatible Systems, RCMP,
April 2002
11) Secure Deletion of Data from Magnetic and Solid-State Memory, Peter Gutmann, Department of
Computer Science, University of Auckland.
12) Statement by Mr. Michael Robert Overly before the Subcommittee on the Constitution of the
Committee on the Judiciary, U.S. House of Representatives, September 6, 2000.
http://www.house.gov/judiciary/over0906.htm
13) Electronic Evidence and Records Retention http://www.willyancey.com/electronic_evidence.htm
14) http://www.hivercon.com/hc02/talk-seifried.htm
15) http://cryptome.unicast.org/cryptome022401/nispom/nispom.htm
(DOD 5220.22-M)
16) Treasury Board Policy “Disposal of Surplus Moveable Crown Assets”
http://www.tbs-sct.gc.ca/pubs_pol/dcgpubs/materielmanage/dsmca1_e.asp#Appendix%20-
%20Guidelines
Lead agency publication G2-003
RCMP Technical Security Branch October 2003
22
APPENDIX A - Disk Overwrite Software “Conditions For Use (CFU)”
CFU #1 - Treat and control all overwrite and overwrite-verification utilities as
sensitive, configuration items.
Overwrite applications are not classified, but they should be treated as controlled items with at least the
same configuration management and security protection controls as the disks they will be used to overwrite.
Document your procedures to ensure adequate controls are enforced to prevent unauthorized modification
or subversion of the overwrite software. Place and maintain under Configuration Control. Ensure your
procedures prevent all access by unauthorized users of this program to ensure all data is securely erased.
CFU #2 - Overwrite-verification should use a separate, validated application.
An overwrite-verification utility is used specifically to verify that all addressable locations of the hard drive
have been overwritten with the prescribed pattern. In order to accomplish this function with trust, one must
have an application that has been validated as capable of viewing the entire disk drive. Using a verification
function which has been included as a separate procedure within the overwrite application is problematic.
Any inherent shortcomings the overwrite function may possess will surely be included in the verification
function.
CFU #3 - Prior to overwrite, calculate the REAL disk drive capacity.
It is imperative that the total addressable capacity of the disk drive be determined prior to commencing the
overwrite procedure. It is not adequate to assume the drive has the capacity as reported by the BIOS,
FDISK, CHKDSK or Windows, etc. There is no standard for reporting disk drive capacity. Frequently,
drive capacity is reported using different units, i.e., binary or decimal byte ‘equivalents’. This can be very
confusing, and unless the actual capacity is known, the results of the overwrite process will be in doubt.
The only reliable method of determining the disk drive’s addressable storage capacity is to calculate it.
CFU #4 - Ensure that both the Overwrite and Verification applications report
the REAL disk capacity.
A complete overwrite of all addressable areas of a disk drive is only possible if the overwrite application is
‘aware’ of the total capacity. Calculate and compare the real disk capacity with the capacity reported by
the overwrite application. If the calculated capacity is greater than the reported capacity, then the disk drive
will only be overwritten up to the reported limit, and will NOT be completely overwritten.
It is equally important that the verification application be similarly capable of accessing the entire hard disk
drive.
CFU #5 - Treat disk drives containing BAD sectors as not being overwritten,
until verification proves otherwise.
Occasionally a disk drive will undergo the overwrite procedure and subsequently report the presence of
“bad” sectors. An essential performance requirement for verification applications is that they must be
capable of imaging these reported bad sector areas to allow confirmation that they have been fully
overwritten. Otherwise the bad sectors must be considered as containing residual data, in which case the
disk drive has not been completely sanitized. Disk drives with unverified overwrites of bad sector areas
should not be released for reuse. In certain cases, the disk controller may contain logic to automatically remap
around a bad track, causing no errors to be generated on overwrite.
Lead agency publication G2-003
RCMP Technical Security Branch October 2003
23
CFU #6 - Require that Overwrite applications be run from a bootable floppy
disk.
Disk drive overwrite applications are only designed and tested to run within a very specific operating
system. Due to the drive capacity reporting anomalies reported in CFU #3, the disk overwrite utility will
calculate or determine capacity based on its own algorithms and using operating system-dependent
functions. Never use overwrite applications that are run from within any version of any operating system
unless specifically recommended by the developer and unless the application has been validated for that
particular version of the operating system.
CFU #7 - Enforce the use of documented procedures and/or checklists, when
using Overwrite applications for sensitive situations of the protected and
classified categories.
The development and enforced use of application-specific, documented procedures are recommended to
ensure consistency and repeatability of results for use of overwrite products, and for product-specific user
training. Since typical overwrite software products are highly user-configurable items, and because the
sequence of procedural steps used to overwrite and subsequently verify the correct overwriting of hard
disks is critical, checklists are a useful means of guiding users through a validated and repeatable process.
Ideally, these procedures and checklists should be specific to the product used for overwrite and should be
developed and certified for official use by a competent authority. Any and all changes to these procedures
and checklists should be subjected to formal revalidation and certification for use.
NecroFile Professional Edition
NecroFile Professional Edition
| |
Author: | The Nth System |
Version: | 1.00 (Shareware) |
Updated: | N/A |
Site: | http://www.necrofile.net |

Downloads:
*Suggested*: | Installer | All Files | 1.60 MB |
Minimal: | Installer | No Runtimes | 800 KB |
Compressed: | Raw .Zip | No Runtimes | 350 KB |


NecroFile Professional Edition is a state-of-the-art disk protection utility; little beknownst to most of us, when we tell Windows to delete a file from the trash bin, it is not actually deleted at all. NecroFile eliminates the threat of outside forces bringing your files back from the dead by using a unique system that conforms to all DoD standards. Let NecroFile serve as your primary anti-undeletion tool and your new recycle bin to ensure that your worst nightmares do not become a reality!
NecroFile is ideal for both home and business environment security.
Just a few of the features include:
Add drives to safely destroy already deleted files
Shred files, folders, and subfolders with ease
Extensive error handling to avoid troubles
Integrating enables easy drag and drop
NecroFile acts as a Recycle Bin (just drag files onto it!)
Schedule when and what you want to clean
Password protect NecroFile
Can be set to run without appearing or supress all messages/output
The background and color scheme can be customized
Encryption and randomization increase your security
Save, open, and print lists for record-keeping and automation
Choose the individual number of passes and the speed of operation
… and much more!
PGP Desktop Professional
Comprehensive email and full disk encryption for desktop and laptop computers
Email and mobile computers have quickly emerged as industry-standard tools for increasing communication and user productivity. Unfortunately, unprotected email and mobile devices pose a critical risk to an enterprise’s most sensitive data: customer information, financial data, trade secrets, and other proprietary information. Exposure of this data can result in financial loss, legal ramifications, and brand damage.
PGP Desktop Professional provides a comprehensive set of encryption applications to protect sensitive data in email and instant messages and on disk or removable media. PGP Desktop Professional secures confidential data, protecting sensitive business information and helping to meet partner and regulatory mandates for information security and privacy.
- Easy, automatic operation – Protects sensitive email without changing the user experience or email application.
- Enforced security policies – Automatically enforce email and data protection with centrally managed policies.
- Accelerated deployment – Achieves end-to-end email encryption using the existing infrastructure.
- Reduced operation costs – Result from centrally automating email encryption policies.
As a PGP Encryption Platform–enabled application, PGP Desktop Professional can be used with PGP Universal Server to manage existing policies, users, keys, and configurations, expediting deployment and policy enforcement. PGP Desktop Professional can also be used in combination with other PGP encryption applications to provide multiple layers of security.
http://download.pgp.com/pdfs/datasheets/PGP_Desktop_Pro_DS.pdf
Mag EraSURE
Mag EraSURE

1바이트의 흔적도 남기지 않는다!!!
Mag EraSURE 후지쯔의 기술력으로 실현됩니다.
Mag EraSURE는 후지쯔에서 개발한 Degausser로 영구자석을 채용하여 강력한 자력(최대 13,000 Gauss)으로 Data를 완전히 소거시켜 HDD/Tape를 안심하고 폐각 할 수 있습니다.
Mag EraSURE Professional
제품사양
![]() | 형태 | 설치형 |
| 조작 | AC모터 채용으로 간단한 작업 (스위치 조작만으로 가능) | |
| 자기력 | 최대 13,000 Gauss | |
| 전원 | AC220V | |
| 대상 HDD | 3.5″, 2.5″, 1.8″ | |
| 대상 테이프 | DLT, LTO, 카트리지, DAT | |
| 소거시간 | 약 30 초 (착탈시간 포함 약 1 분) | |
| 크기 | 340(W) x 650(D) x 215(H) | |
| 중량 | 33Kg |
Mag EraSURE Professional 3
제품사양
![]() | 형태 | 설치형 |
| 조작 | 편리한 원터치 구동방식, 무소음/무발열 | |
| 자기력 | 최대 14,000Gauss, 유효 5,300Oe | |
| 전원 | 220~240V 50/60Hz | |
| 대상 HDD | 3.5”, 2.5”, 1.8” | |
| 대상 테이프 | 두께 1.0”Tape 3480, DLT, LTO, DAT, 8mm, Floppy Disk | |
| 소거시간 | 38초 | |
| 크기 | 680(W) x 1270(D) x 340(H) | |
| 중량 | 170Kg |
Mag EraSURE Mobile
제품사양
![]() | 형태 | 이동형 |
| 조작 | 간단한 수동핸들 조작 전원이 필요없어 전쟁, 소용 등 긴급사태 발생시 사용 | |
| 자기력 | 최대 13,000 Gauss | |
| 전원 | 불필요 | |
| 대상 HDD | 3.5″, 2.5″, 1.8″ | |
| 대상 테이프 | DLT, LTO, 카트리지, DAT | |
| 소거시간 | 약 30 초 (착탈시간 포함 약 1 분) | |
| 크기 | 270(W) x 500(D) x 200(H) | |
| 중량 | 20Kg |
소거효과 검증

신호 Level(Single Disk Tester)

Degausser에 대하여
Degausser는 강력한 자력으로 자기매체 즉 Hard Disk와 자기Tape에 기록된 자기Data를 삭제시키는 장치이다. Degausser는 영구자석을 사용하는 것과 전자석을 사용하는 것이 있다. 전자석을 사용한 제품은 콘덴서에 전기를 충전한 후에 순간적으로 방전시켜 자력을 얻는 방식으로 일반적으로 많이 사용하고 있으나 일정 회수 이상 사용하면 콘덴서의 수명이 다하여 콘덴서를 교체하여야 한다. 이에 반해 영구자석을 사용한 Degausser는 고장과 부품교체없이 반영구적으로 사용 할 수 있는 장점이 있다.
후지쯔사의 Degausser 제품인 Mag EraSURE는 영구자석을 사용하고 있으며. 특히 Mag EraSURE Mobile형은 입력전기가 필요없어, 군대의 야전 작전 수행시, 전쟁/소요로 정전이 되었을 때 등 긴급상황에서 사용이 가능한 제품이다
Degausser는 자기매체상에 기록된 보자력(기록된 자력의 세기, 단위: Oersted) 보다 강력한 자력을 자기매체면에 직접 인가하여야 완벽하게 자기매체상의 기록된 Data를 삭제 할 수 있다.
일부 저가의 소형 Degausser제품은 소자능력이 떨어져 요즈음 출시되는 4000Oe이상의 높은 보자력의 HDD에 대해서는 Data가 제대로 소거가 되지않고 잔류자기 성분이 남아 있어 복구가 가능 할 수도 있으며, Degausser제품의 성능표시도 자기매체상에 직접 인가되는 유효 소자능력이 아닌 발생되는 최대자기력을 표시하는 제품도 있어 Degausser 제품선정에 주의가 필요하다.
Hard Disk 와 자기Tape가 대용량화 되면서 자기매체상의 보자력이 점점 강해지는 추세이어서 자기매체상에 직접 인가되는 유효소자력 4000Oe이상의 고성능의 Degausser를 선택하는 것이 재투자를 방지하며 정보유출을 방지하는 효율성있는 방법이라 할 수 있다.
Hard Disk내 정보의 삭제방법
사용완료된 Hard Disk내의 정보삭제에는 전용 Software를 사용한 Soft Erase, Degausser를 사용한 Hard Erase와 물리적 처리 방법 등이 있으며 각 방법에 대하여 알아보자.
- Soft Erase(전용 Software사용 삭제)
전용Soft를 사용하여 Hard Disk에 전면적으로 특정의 Data를 덧쓰는 방법이나, 3회이상 재실시하여도 일부는 복구 가능성이 있어 보안성은 떨어진다. 또한 120GB의 Hard Disk 3회 소거에 8시간 이상 소요되어 중요한 정보의 삭제나 대량 의 Hard Disk 처리에는 부적합 하다. 소량 HDD의 Data를 소거하거나 높은 보안성이 요구되지않는 경우에 사용 될 수 있다.
- Hard Erase(Degausser사용 삭제)
HDD Data 삭제전용 Degausser를 사용하여 강력한 자기력을 Hard Disk에 인가해 기록 된 정보를 완전히 삭제하는 방법으로 단시간에 처리가 가능하여 가장 효율성 있고 안전 성이 확보된 방법이라 할 수 있다. Degausse를 사용하여 HDD Data를 삭제하면 HDD를 재사용 할 수 없는 단점이 있으나 대부분 사용이 만료된 PC의 오래된 HDD이므로 경제적인 가치는 대부분 몇천원 정도의 가치를 가지고 있으며 정보유출시 발생되는 막대한 피해에 비교하면 아주 적은 금액 이라 할 수 있다.
- 물리적 방법
1) 파쇄 : 보안성을 확보하려면 Hard Disk 매체를 사방 5mm 이내로 파쇄하여야 하며 대형장치가 필요하다.
2) Drill로 천공 : 부분적으로 복구의 가능성이 있으며, 천공시 소음등으로 사무실내에서 처리가 불가하다.
3) 소각, 산성물질로 용해 : 부분적으로 복구의 가능성이 있으며 현실적으로 곤란하다.
4) 물리적인방법은 사무실내 처리가 불가능하여 처리를 위하여 운반과 이동시에 과실 또는 악의에 의해 분실과 도난의 위험이 있다.
이상의 3가지 방법중 Degausser를 사용한 Hard소거 방법이 가장 완벽하게 HDD Data를소거하며, 소거시간도 짧아 대량의 삭체처리가 가능한 가장 효율적인 방법이라 하겠다.
Degaussing
Degaussing is the process of decreasing or eliminating an unwanted magnetic field. It is named after Carl Friedrich Gauss, an early researcher in the field of magnetism. Due to magnetic hysteresis it is generally not possible to reduce a magnetic field completely to zero, so degaussing typically induces a very small “known” field referred to as bias.
The term was first used by (then) Cmdr. Charles F. Goodeve, RCNVR, during World War II while trying to counter the German magnetic mines that were playing havoc with the British fleet. The mines detected the increase in magnetic field when the steel in a ship concentrated the Earth’s magnetic field over it. Goodeve developed a number of systems to induce a small “N-pole up” field into the ship to offset this effect, meaning that the net field was the same as background. Since the Germans used the gauss as the unit of the strength of the magnetic field in their mines’ triggers (this was not yet a standard measure), Goodeve referred to the various processes to counter the mines as degaussing. The term became a common word.
The original method of degaussing was to install electromagnetic coils into the ships, known simply as coiling. In addition to being able to continually bias the ship, coiling also allowed the bias field to be reversed in the southern hemisphere, where the mines were set to detect “S-pole down” fields. British ships, notably cruisers and battleships, were well protected by about 1943.
Installing such special equipment was, however, far too expensive and difficult to service all ships that would need it, so the navy developed an alternative called wiping (devised by Goodeve), which simply dragged a large electrical cable along the side of the ship with about 2000 amps flowing through it. This induced the proper field into the ship in the form of a slight bias. It was originally thought that the pounding of the sea and the ship’s engines would slowly randomize this field, but in testing this was found not to be a real problem. A more serious problem was later realized: as a ship travels through the Earth’s magnetic field it will slowly pick up that field, counteracting the effects of the degaussing. From then on captains were instructed to change direction as often as possible to avoid this problem. Nevertheless the bias did wear off eventually, and ships had to be degaussed on a schedule. Smaller ships continued to use wiping through the war.
After the war the capabilities of the magnetic fuses were greatly improved, by detecting not the field itself, but changes in it. This meant a degaussed ship with a magnetic “hot spot” would still set off the mine. Additionally, the precise orientation of the field was also measured, something a simple bias field could not remove, at least for all points on the ship. A series of ever-increasingly complex coils were introduced to offset these effects, with modern systems including no fewer than three separate sets of coils to reduce the field in all axes.
[edit] Degaussing monitors
Today the most common use of degaussing is in CRT-based TV sets and computer monitors. For example, many monitors use a metal plate near the front of the tube to focus the electron beams from the back. This plate, the shadow mask, can pick up strong external fields and from that point produce discoloration on the display.
To minimize this, CRTs have a copper coil wrapped around the front of the display, known as the degaussing coil. Tubes without an internal coil can be degaussed using an external hand held version. Internal degaussing coils in CRTs are generally much weaker than external degaussing coils, since a better degaussing coil takes up more space. A degauss causes a magnetic field inside the tube to oscillate rapidly, with decreasing amplitude. This leaves the shadow mask with a small and somewhat randomized field, removing the discoloration.
Many televisions and monitors automatically degauss their picture tube when switched on, before an image has been displayed. The high current surge which takes place during this automatic degauss is the cause of the audible ‘thunk’ which can be heard (and felt) when televisions and CRT computer monitors are switched on. Visually, this causes the image to shake dramatically for a second or so.
In most commercial equipment the current surge to the degauss coil is regulated by a simple PTC thermistor device which initially has a low resistance but quickly changes to a high resistance due to the heating effect of the current flow. Such devices are designed for a one-off transition from cold to hot at power up, so ‘experimenting’ with the degauss effect by repeatedly switching the device on and off is not recommended as it may cause this component to fail. The effect will also be weaker, since the PTC won’t have had time to cool off.
[edit] Degaussing magnetic data storage media
Data is stored in magnetic media, such as hard drives, floppy disks and magnetic tape, by making very small areas called magnetic domains change their magnetic alignment to be in the direction of an applied magnetic field. This phenomenon occurs in much the same way a compass needle points in the direction of the earth’s magnetic field. Degaussing, commonly called erasure, leaves the domains in random patterns with no preference to orientation, thereby rendering previous data unrecoverable. There are some domains whose magnetic alignment is not randomized after degaussing. The information these domains represent is commonly called magnetic remanence since it is due to remanent magnetization. Proper degaussing will ensure there is insufficient magnetic remanence to reconstruct the data.[1]
Erasure via degaussing may be accomplished in two ways: in AC erasure, the media is degaussed by applying an alternating field that is reduced in amplitude over time from an initial high value (i.e., AC powered); in DC erasure, the media is saturated by applying a unidirectional field (i.e., DC powered or by employing a permanent magnet). A degausser is a device that can generate a magnetic field for degaussing magnetic storage media.[2]
[edit] Alternative methods
Monitors without a degauss function can be degaussed by placing a degauss-enabled monitor face-to-face with the target monitor. Activating the degauss function on the enabled monitor can help degauss the other.[citation needed].
Degaussing can also help reduce the distortion due to static electricity that often results from long-term usage of the monitor, especially in older monitors.[citation needed]
Anti-forensic techniques
Anti-forensic techniques
From Forensics Wiki
Anti-forensic techniques try to frustrate forensic investigators and their techniques.
This can include refusing to run when debugging mode is enabled, refusing to run when running inside of a virtual machine, or deliberately overwriting data. Although some anti-forensic tools have legitimate purposes, such as overwriting sensitive data that shouldn’t fall into the wrong hands, like any tool they can be abused.
Traditional anti-forensics
Overwriting Data and Metadata
Secure Data Deletion
Securely deleting data, so that it cannot be restored with forensic methods.
Overwriting programs typically operate in one of three modes:
- The program can overwrite the entire media.
- The program can attempt to overwrite individual files. This task is complicated by journaling file systems: the file itself may be overwritten, but portions may be left in the journal.
- The program can attempt to overwrite files that were previously “deleted” but left on the drive. Programs typically do this by creating one or more files on the media and then writing to these files until no free space remains, taking special measures to erase small files — for example, files that exist entirely within the Windows Master File Table of an NTFS partition (Garfinkel and Malan, 2005).
Programs employ a variety of techniques to overwrite data. Apple’s Disk Utility allows data to be overwritten with a single pass of NULL bytes, with 7 passes of random data, or with 35 passes of data. Microsoft’s cipher.exe, writes a pass of zeros, a pass of FFs, and a pass of random data, in compliance with DoD standard 5220.22-M. (US DoD, 1995). In 1996 Gutmann asserted that it might be possible to recover overwritten data and proposed a 35-pass approach for assured sanitization (Gutmann 1996). However, a single overwriting pass is now viewed as sufficient for sanitizing data from ATA drives with capacities over 15 GB that were manufactured after 2001 (NIST 2006).
Be aware that software ‘data destroyers’ may not necessarily do what they state on the burb site. In particular a common mistake is the oversight of how the underlying file system actually stores files, for instance a ‘wipe drive’ application that will write a series of random values across unallocated space on the hard disk may not take into account the slack space at the end of allocated data blocks. Thus allowing a large portion of old data to still be recoverable. This is a very handy for a forensic analyst, but not so handy for IT Managers.
Overwriting Metadata
If the examiner knows when an attacker had access to a Windows, Mac or Unix system, it is frequently possible to determine which files the attacker accessed, by examining file “access” times for every file on the system. Some CFTs can prepare a “timeline” of the attacker’s actions by sorting all of the computer’s timestamps in chronological order. Although an attacker could wipe the contents of the media, this action itself might attract attention. Instead, the attacker might hide her tracks by overwriting the access times themselves so that the timeline could not be reliably constructed.
For example, Timestomp will overwrite NTFS “create,” “modify,” “access,” and “change” timestamps (Metasploit 2006). The Defiler’s Toolkit can overwrite inode timestamps and deleted directory entries on many Unix systems; timestamps on allocated files can also be modified using the Unix touch command (Grugq 2003).
Preventing Data Creation
Prevent the creation of certain data in the first place. Data which was never there, obviously cannot be restored with forensic methods.
For example, a partition can be mounted read-only or accessed through the raw device to prevent the file access times from being updated. The Windows registry key HKLM\SYSTEM\CurrentControlSet\Control\FileSystem\NtfsDisableLastAccessUpdate can be set to “1” to disable updating of the last-accessed timestamp; this setting is default under Windows Vista (Microsoft 2006).
Cryptography, Steganography, and other Data Hiding Approaches
Encrypted Data
Cryptographic file systems transparently encrypt data when it is written to the disk and decrypt data when it is read back, making the data opaque to any attacker (or CFT) that does not have the key. These file systems are now readily available for Windows, Mac OS, and Linux. The key can be protected with a passphrase or stored on an auxiliary device such as a USB token. If there is no copy of the key, intentionally destroying the key makes the data stored on the media inaccessible (Boneh and Lipton, 1996). Even if the cryptographic system lacks an intentional sanitization command or “self-destruct,” cryptography can still be a potent barrier to forensic analysis if the cryptographic key is unknown to the examiner.
Cryptography can also be used at the application level. For example, Microsoft Word can be configured to encrypt the contents of a document by specifying that the document has a “password to open.” Although older versions of Microsoft Word encrypted documents with a 40-bit key that can be cracked with commercial tools, modern versions can optionally use a 128-bit encryption that is uncrackable if a secure passphrase is used.
Encrypted Network Protocols
Network traffic can likewise be encrypted to protect its content from forensic analysis. Cryptographic encapsulation protocols such as SSL and SSH only protect the content of the traffic. Protecting against traffic analysis requires the use of intermediaries. Onion Routing (Goldschlag, Reed and Syverson, 1999) combines both approaches with multiple layers of encryption, so that no intermediary knows both ends of the communication and the plaintext content.
Program Packers
Packers are commonly used by attackers so that attack tools will not be subject to reverse engineering or detection by scanning. Packers such as PECompact (Bitsum 2006) and Burneye (Vrba 2004) will take a second program, compress and/or encrypt it, and wrap it with a suitable extractor. Packers can also incorporate active protection against debugging or reverse engineering techniques. For example, Shiva will exit if its process is being traced; if the process is not being traced, it will create a second process, and the two processes will then trace each other, since each process on a Unix system may only be traced by one other process. (Mehta and Clowes, 2003)
Packed programs that require a password in order to be run can be as strong as their encryption and password. However, the programs are vulnerable at runtime. Burndump is a loadable kernel module (LKM) that automatically detects when a Burneye-protected file is run, waits for the program to be decrypted, and then writes the raw, unprotected binary to another location (ByteRage 2002). Packed programs are also vulnerable to static analysis if no password is required (Eagle 2003).
Steganography
Steganography can be used to embed encrypted data in a cover text to avoid detection. Steghide embeds text in JPEG, MBP, MP3, WAV and AU files (Hetzl 2002). Hydan exploits redundancy in the x86 instruction set; it can encode roughly 1 byte per 110 (El-Khalil 2004). Stegdetect (Provos 2004) can detect some forms of steganography.
StegFS hides encrypted data in the unused blocks of a Linux ext2 file system, making the data “look like a partition in which unused blocks have recently been overwritten with random bytes using some disk wiping tool” (McDonald and Kuhn, 2003).
TrueCrypt allows a second encrypted file system to be hidden within the first (TrueCrypt 2006). The goal of this filesystem-within-a-filesystem is to allow the TrueCrypt users to have a “decoy” file system with data that is interesting but not overtly sensitive. A person who is arrested or captured with a TrueCrypt-protected laptop could then give up the first file system’s password, with the hope that the decoy would be sufficient to satisfy the person’s interrogators.
Generic Data Hiding
Data can also be hidden in unallocated or otherwise unreachable locations that are ignored by the current generation of forensic tools.
Metasploit’s Slacker will hide data within the slack space of FAT or NTFS file system. FragFS hides data within the NTFS Master File Table. RuneFS (Grugq 2003) stores data in bad blocks. (Thompson and Monroe, 2006). Waffen FS stores data in the ext3 journal file (Eckstein and Jahnke 2005). KY FS stores data in directories (Grugq 2003). Data Mule FS stores data in inode reserved space (Grugq 2003). It is also possible to store information in the unallocated pages of Microsoft Office files.
Information can be stored in the Host Protected Area (HPA) and the Device Configuration Overlay (DCO) areas of modern ATA hard drives. Data in the HPA and DCO is not visible to the BIOS or operating system, although it can be extracted with special tools.
Detecting Forensic Analysis
There are methods to detect whether an investigator tries to perform a (live) forensic analysis on the system. A malicious user or program could react to that by destroying evidence, for example.
References
Garfinkel, S., Anti-Forensics: Techniques, Detection and Countermeasures, The 2nd International Conference on i-Warfare and Security (ICIW), Naval Postgraduate School, Monterey, CA, March 8-9, 2007. [1]
Henrique, G. Wendel, Anti Forensics: Making computer forensics hard, Code Breakers III, São Paulo, Brazil, Setember 2006
The Defiler’s Toolkit
The Defiler’s Toolkit is a set of programs that is designed to prevent |
sisp-ga rated this answer: and gave an additional tip of: $20.00 Very good, thanks for helping me and giving me very good web links |
Defeating Forensic Analysis on Unix
by grugq
The purpose of this article is to describe weaknesses in current forensic tools so that those weaknesses may be exploitable by those hoping to avoid forensic analysis (in a word, anti-forensics) and in the hope that developers of forensic tools will improve said tools so as not to permit the exploitation of these vulnerabilities in future releases of their toolkits. The author developed several tools for the exploitation of those vulnerabilities and published them uuencoded inside the document. The author assumes a familiarity with the Unix file system and digital forensic analysis.
The first section is an attempt to briefly explain the basic elements of a Unix file system (in our case it will be the ext2fs, the older non-journaling file system which was the standard file system provided with most flavors of Linux). The quality of this brief tutorial leaves much to be desired. A much better job of explaining the structure of the system is done in Appendix A, where the headers for each type of structure in the ext2fs are listed and comments are included for most of the data elements.
Basically there are two types of elements in a Unix file system, the contents of the files (data) and information about the files (or “meta-data”). Each file fills up a number of data blocks to store its contents. There are two types of meta-data, “inodes” and directory entries. An inode stores information about the file, like which data blocks are associated with the file, its owner, permissions, creation time, etc. Each file also has at least one entry in a directory entry table. The table lists the file’s inode number and filename. Because Unix allows multiple filenames to be associated with one actual file (these are called links), an attribute of the inode is link count. When a file is deleted the link count becomes zero. Quite simply no more filenames link to this inode and it’s associated data blocks. Rather than delete the contents of the inode and the data block, the file system is lazy and just adds the inode and data block addresses to the list of available inodes and data blocks for later reuse. There are many more details to the Unix file system, but this information should be sufficient for the purposes of this paper. For a much more thorough treatment of the Unix file systems, see “File System Forensic Analysis” by Carrier.
The author discusses forensics next. He points out that there are two reasons to perform forensics on a system, as part of a legal investigation or for a “casual investigation”. A causal investigation is defined as any investigation that is not associated with a legal proceeding. A legal investigation must follow specific forensic rules for the admissibility of evidence in a court and, as a result, it is much easier to circumvent their evidence. Simply overwriting data with random bytes is sufficient to remove any admissible evidence. However a “casual investigation” does not need to obey criminal evidence standards. As such, it can be far more difficult to protect against the discovery of evidence by the casual investigator.
The author covers briefly some of the steps in a forensics investigation and how a forensics investigator will try to piece together information for a recovered disk drive. As mentioned above, when files are deleted, the file system does not bother to scrub the meta-data or the data blocks that contain the file contents. A forensic examiner can recover a great deal of information from this deleted but not yet overwritten information (referred to as level 2 and level 3 information in Remembrance of Data Passed: A Study of Disk Sanitation Practices in the Network Telescopes section).
The paper is about how to make sure specific data is not recoverable by the forensic examiner, or anti-forensics. There are two ways to do this, destroy the data (and the associated meta-data) or hide the data. Data destruction is far more reliable; there’s simply no information left on the system for the analyst to recover. Data hiding is trickier; it depends on hiding the data in places the examiner and his tools cannot find. The paper addresses data hiding first.
A popular forensics tool for Unix is the “The Coroner’s Toolkit” (TCT) developed by Dan Farmer and Wietse Venema. These authors also wrote a popular book on the subject (“Forensic Discovery”) in which they discuss their toolkit. One aspect of TCT is that it does not analyze bad blocks. These are data blocks marked by the file system as unusable. However, grugq discovered that he can mark as many blocks as he wants as bad, hide data in them and the file system never complains about his technique. The tool he developed is called “runefs”. He shows an example of how he can hide data in bad blocks and a TCT tool is unable to discover it. The tool provided with this paper is older and less flexible, yet the author has developed an improved tool that allows for encryption and dynamic resizing, but the author is not releasing it to the public. The author promises that there are other ways to hide data on a file system, which will be presented in future papers.
The second topic is data destruction. The author states that there a number of tools to overwrite the data blocks on a Unix file system, but most tools don’t bother to remove the meta-data information, which can be equally valuable to the forensic investigator. He developed a toolkit called “The Defiler’s Toolkit” which addressed the destruction of this meta-data for deleted files. The toolkit contains two tools, Necrofile and Klismafile. Necrofile overwrites all inodes that no longer have a filename associated with them (in the inode, links_count = 0). It overwrites the inode with blank inode information. Klismafile removes evidence of a file in a directory entry table. While the blank space in the directory entry table could be an indicator of use of this tool, the author comments that no forensics tool has been developed to look for this. The author gives examples of uses of each of these tools and the inability of forensic tools to uncover the erased meta-data information. As mentioned above, the Defiler’s Toolkit is also included in the article.
In the concluding comments, the author talks about how surprised he is that buggy software like the Coroner’s Toolkit is so respected in the industry. He recommends ways to circumvent his Defiler’s Toolkit by writing inode updates to a log on a secure server so they can be recovered later. He hopes articles like this will encourage the security software developers to improve their tools in the never-ending arms race of computer security.
Anti-forensics: the removal, or hiding, of evidence in an attempt to mitigate the effectiveness of a forensics investigation.
Digital forensic analysis is rapidly becoming an integral part of incident response, capitalizing on a steady increase in the number of trained forensic investigators and forensic toolkits available. Strangely, despite the increased interest in, and focus on, forensics within the information security industry, there is surprisingly little discussion of anti-forensics. In an attempt to remedy the lack of coverage in the literature, this article presents anti-forensic strategies to defeat digital forensic analysis on Unix file systems. Included are example implementations of these strategies targeting the most common Linux file system — ext2fs.
To facilitate a useful discussion of anti-forensic strategies it is important that the reader possess certain background information. In particular, the understanding of anti-forensic file system sanitization requires the comprehension of basic Unix file system organization. And, of course, the understanding of any anti-forensic theory demands at least a rudimentary grasp of digital forensic methodology and practice. This article provides a limited introduction to both Unix file systems and digital forensics. Space constraints, however, limit the amount of coverage available to these topics, and the interested reader is directed to the references, which discuss them in greater depth.
Anti-Forensic Tools
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
- Anti-Forensic
- Biology
- Drug Culture
- Electronic Music
- Medical
- Medicine
- SEO+WEBPR
- VJ
- Web Design
- 개념
- 게임
- 기초의학
- 데이타베이스
- 독백 (monologue)
- 뮤지션 (musician)
- 분자생리학
- 상식
- 생리학개론
- 서버관련정보
- 성형및시술
- 세포생리학
- 아바타 (avatar)
- 영어공부
- 인터넷활용
- 자작 VJ-Video
- 조직학
- 종양학
- 즐겨찾는곳 (link)
- 증상학
- 질병분류
- 컴퓨터활용
- 컴퓨팅관련노하우
- 코스메틱
- 튜어리즘(Tourism)
- 팁+노하우 (howto)
- 파티 (party)
- 패션
- 프로그래밍
- 피부과학
- 한자공부
- 해킹및보안
Author:
Version:
Updated:
Site:
*Suggested*:
Minimal: 


and gave an additional tip of: $20.00 