Slashdot Mirror


The Homemade Hard Disk Destroyer

Barence writes "All businesses have sensitive data they need to destroy when they replace PCs, but disposing of hard disks properly can be an expensive business. This has led one IT manager in the UK to come up with his own, homemade solution — Bustadrive. It uses a powerful 'hydraulic punch' to physically deform a hard disk, rendering it virtually unreadable, and requires nothing more than a pull of the lever on the front — similar to a drinks-can crusher. PC Pro tested the Bustadrive, and also sought the opinions of data destruction companies as to whether the device was really as effective as hoped, or just a fun way to mangle a hard disk or two."

17 of 497 comments (clear)

  1. Overkill? by Miros · · Score: 4, Insightful

    Why not just use a degausser? or DBAN?

    1. Re:Overkill? by Hyppy · · Score: 3, Insightful

      Some places still require both. When it comes to extremely sensitive (classified, etc) data, "absolutely unreadable" must be absolute. Even if only one technician in the entire world, with a billion-dollar lab, is capable of recovering the data from a zero'd drive, it's too much of a risk. What if that one technician is Chinese?

    2. Re:Overkill? by emocomputerjock · · Score: 4, Insightful

      I was agreeing with you.

    3. Re:Overkill? by mlts · · Score: 4, Insightful

      There is one simple thing about physical destruction. It is obvious to an observer that the drive is unusable. If someone has a pile of drives, one before DBAN, one after, it wouldn't be hard for someone to move some drives into the after pile either as a prank, or perhaps to get the information once it leaves the location. Physical destruction prevents this from happening, because almost anyone can tell the difference between a pile of scrap metal and a hard disk that looks like it might function.

    4. Re:Overkill? by TheRaven64 · · Score: 4, Insightful

      Who are you trying to keep the data safe from? If it's a foreign government willing to do a molecular scale image of the entire disk with a scanning tunnelling electron microscope and then have a large team of people painstakingly apply heuristics and get back some small fraction of the stored data in a few years time and after spending several tens of millions of dollars on the project, then this is indeed good advice. If, on the other hand, you're worried about commercial data theft, then a single dd pass is enough.

      --
      I am TheRaven on Soylent News
    5. Re:Overkill? by snemarch · · Score: 3, Insightful

      With normal FS format options, that would only take care of a very small portion of the drive (FS metadata doesn't consume that much space) - it would be pretty easy extracting useful data using plain old software. A single-pass disk wipe would be a lot more useful :)

      --
      Coffee-driven development.
  2. lots of options out there! by farnham · · Score: 4, Insightful

    My drill press makes for a very effective drive killer.

    Use what you got!

    --
    pending committee review
  3. Re:The Columbia test by Miros · · Score: 3, Insightful

    I think it would be easy to melt the disk into a nice puddle of slag, what might be harder is not burning the building down in the process.

  4. Gross Overkill by kingsack · · Score: 3, Insightful

    A ball pean hammer applied vigorously to the drive spindle will render all but the most wealthy and determined effort to recover data fruitless and even then it is highly unlikely that all or even most of the data would be recoverable.

  5. Re:Stand drill by Anonymous Coward · · Score: 4, Insightful

    I'd guess the foundry people would object to contaminating their carefully selected alloy...

  6. Re:Stand drill by mellon · · Score: 4, Insightful

    Dude, haven't you read the Trilogy? It takes half a book just to cross Mordor, plus there's Orcs and shit. That's way more trouble than it's worth. And have you ever tried to find Middle Earth on a map? Sure, lots of people have theories, but what with continental drift and such, it's all pretty obscure. How can you be sure the volcano you use is *really* Mount Doom in this late, degenerate age?

  7. Re:Gutmann was wrong by Anonymous Coward · · Score: 5, Insightful

    Physically overwritten sectors are (almost) certainly unrecoverable. But what about remapped 'bad' sectors? AFAIK these cannot be accessed in any way by software wiping tools, but could be accessed and potentially read by tweaked drive firmware. They might be overwritten if you use the drive's own firmare erase command if it supports this.

  8. In the real world, fire is a bad solution by name_already_taken · · Score: 5, Insightful

    Which would be the better solution.

    A small terracotta pot without a hole in the bottom of it + a small amount of thermite is the cheapest way, thermite is cheap and reasonably easy to make.

    Ok, do that in your office and see how many minutes your job lasts once the fire's out.

    Even if we did it outside at my place of work, we'd get complaints from the neighbors. A mechanical/hydraulic crusher/bender thing could be made into something that looks like an office appliance.

    Nothing says "no data recovery" like a drive reduced to its elemental components.

    Except it's not. Burning is generally a process of rapidly combining reactants, not dividing them up. Plus, it's rather environmentally unfriendly - having a cloud of smoke go up is frowned upon in most places these days.

    --
    Putting moderation advice in your .sig lowers your karma!
  9. There was an interesting bugtraq thread in 2005. by arcade · · Score: 4, Insightful

    Let me pull a bugtraq posting from 2005 out for perusal. There are other interesting tidbits in that thread too.

    http://seclists.org/bugtraq/2005/Jul/0464.html

    ===
    From: dave kleiman
    Date: Sun, 24 Jul 2005 15:30:30 -0400

    Here is a quote directly from Peter I received Saturday, he asked to have it
    passed on to the list.
    -Snip-
    >I'd love to hear some thoughts on this from security and data experts
    >out there.
    People should note the epilogue to the paper:
        Epilogue
        In the time since this paper was published, some people have treated the
    35-
        pass overwrite technique described in it more as a kind of voodoo
        incantation to banish evil spirits than the result of a technical analysis
        of drive encoding techniques. As a result, they advocate applying the
        voodoo to PRML and EPRML drives even though it will have no more effect
    than
        a simple scrubbing with random data. In fact performing the full 35-pass
        overwrite is pointless for any drive since it targets a blend of scenarios
        involving all types of (normally-used) encoding technology, which covers
        everything back to 30+-year-old MFM methods (if you don't understand that
        statement, re-read the paper). If you're using a drive which uses
    encoding
        technology X, you only need to perform the passes specific to X, and you
        never need to perform all 35 passes. For any modern PRML/EPRML drive, a
    few
        passes of random scrubbing is the best you can do. As the paper says, "A
        good scrubbing with random data will do about as well as can be expected".
        This was true in 1996, and is still true now.
        Looking at this from the other point of view, with the ever-increasing
    data
        density on disk platters and a corresponding reduction in feature size and
        use of exotic techniques to record data on the medium, it's unlikely that
        anything can be recovered from any recent drive except perhaps one or two
        levels via basic error-cancelling techniques. In particular the the
    drives
        in use at the time that this paper was originally written have mostly
    fallen
        out of use, so the methods that applied specifically to the older, lower-
        density technology don't apply any more. Conversely, with modern high-
        density drives, even if you've got 10KB of sensitive data on a drive and
        can't erase it with 100% certainty, the chances of an adversary being able
        to find the erased traces of that 10KB in 80GB of other erased traces are
        close to zero.

    Peter.
    ===

    --
    "Rune Kristian Viken" - http://www.nwo.no - arca
  10. Re:Gutmann was wrong by TheRaven64 · · Score: 4, Insightful

    And how many of these are there? SMART can tell you how many sectors have been remapped, and I've only seen this over 50 on a hard drive that completely failed a few hours later. 50 512-byte sectors works out to be 25KB of data, taken at random from the data ever written to the disk. What is the probability of this being something useful? If you use encryption or compression on the disk - or the files - then these sectors will contain data that is completely meaningless without the relevant headers.

    --
    I am TheRaven on Soylent News
  11. Comment removed by account_deleted · · Score: 4, Insightful

    Comment removed based on user account deletion

  12. Reduce, Reuse, Recycle by drinkypoo · · Score: 5, Insightful

    Reduce - Buy the biggest disks you can afford, they're worth repurposing and you won't have to spend as much on successors or the attendant labor.

    Reuse - Repurpose disks for other purposes. Use last years' disks as part of your backup solution. Secure-format them on a low-power machine and put them on eBay.

    Recycle - There must be SOMEONE willing to break the drives down and give you back the platters for destruction. There's significant aluminum in some of those drives.

    All this crushing, drilling, and shooting of drives is fun. But it's also extremely wasteful. I understand destroying the drives if lives are at stake, but otherwise, stop.

    --
    "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"