The typical response to trouble - the deer caught in the headlights - is exactly why organizations need a detailed incident response plan. Incident response goes beyond business continuity and disaster recover, outlining specific details to efectively respond to data security breaches and network crashes. Given their breadth and specificity, these documents are usually lengthy and in need of regular upkeep. Here are five points that all IT-specific plans should contain.
Some three years after North America's largest power failure left more than 50 million people in the U.S. and Canada in the dark, a Toronto organization is asking that a coordinated city-wide disaster recovery exercise be launched.
Figures from the 2005 audit of security management of Internet security in Australian government agencies conducted by the Australian National Audit Office (ANAO) was released yesterday and found 31 specific risks as defined by the Defence Signals Directorate (DSD) in agency Web servers.
Mention disaster recovery to most businesses and they automatically start to think about power failures, earthquakes or some kind of nationwide catastrophe. It's because of that attitude, says Plan-B Ltd. founder and director Martin Wellesley, that disaster recovery plans tend to be vague and ultimately not worth the paper they're printed on.