IT & Network Infrastructure : Eight Things to Learn from the Gawker Fiasco
When it became clear over the weekend of Dec. 11-12 that Gawker Media's user database had been compromised by a hacker group, perhaps the most shocking thing about the case was not the break-in itself or the sizable number of people using the Gawker sites who use a business or U.S. government e-mail as their point of contact. Instead, the real attention grabber from a technical point of view turned out to be how woefully unsecure Gawker's servers and data were. The haul included the user-and-password database, e-mail and chat room threads that detailed Gawker Media's day-to-day operations, and the proprietary source code for the Gawker sites, which the company considered an asset with commercial potential. With user identities compromised, the once-secret source code now published for anyone to pick over and more than a few people cheering at the iconoclasts hoisted by their own petard, here are eight lessons that we can learn from the humbling of Gawker's IT staff.