Creating a method of tracking the events and effects of a cyberattack at the time it occurs is both simple and smart. By making incident documentation a part of your response plan, you avoid trying to recount the incident and estimate its cost after the fact
Stories by Simone Kaplan
Surviving a security incident is just the beginning. Then you need to figure out what it really cost.
When Tom Rossi, director of the Innovation Lab at the US Naval War College in Newport, Rhode Island, began a knowledge management initiative in 1999, he thought he knew everything. Rossi and his team were charged with creating a futuristic environment for computerised war games.
You say you've tried Hawaiian shirt days and pizza party Fridays, and your IT department's morale is still in the pits. Forget gimmicks and lead.
You used to pity Lloyd Taylor. Like other CIOs who work for companies in low-margin industries, he was the guy with the shoestring budget who had to watch every penny, every day
Kevin Murray, CIO OF domestic claims and personal lines for American International Group (AIG), had a mainframe full of fat-client legacy applications. He just trashed it in favour of newly written thin-client Java and XML applications
Content management software is hip, but is it more than document management with a fancy handle?
Lay people off or retrain them? Focus on processes or customers? Outsource or keep in-house? We'll give you some of the best practices around.