Slashdot Mirror

← Back to Stories (view on slashdot.org)

When Sysadmins Go Bad

Posted by michael on from the most-of-them-already-are-of-course dept.

An anonymous reader writes "Here is a story about what can happen when you think you're being oh so clever. This sysadmin planted so-called logic bombs on the systems he was responsible for and then quit. He also tried to game the stock market, buying put options on his former company, hoping to cash in when the disaster he engineered struck. Who can companies trust if they're afraid that this kind of thing can happen? How can they prevent it?"

2 of 487 comments (clear)

  1. What OS Was It? by Automatic+Jed · · Score: 0, Troll

    The problem... >>deleted files and led to $3 million in costs >>for PaineWebber to assess and repair the >>damage. He should just blame Microsoft as a defence.

  2. Thats what you get for running Windows by atvspid · · Score: 0, Troll

    Surely he was a MS sysadmin.

    See, now if you were running UNIX you wouldn't have this problem, would you?

    --
    @vSpid Like, Whatever