FAA30200842: (30200842) Incidents to Crisis - How It Can All Go Wrong
| FAA30200842 | Cancelled | ||
| (30200842) Incidents to Crisis - How It Can All Go Wrong | |||
| COURSE | 2012-11-01 | ||
| In March 2012, a Washington DC Federal Agency experienced an electrical fire causing a power loss in the data center. Problems encountered due to an incomplete, but approved, COOP Plan included: Inability to enter the facility to conduct a damage assessment resulted in never implementing COOP and causing a functional/work stoppage for 2 days. Loss of access to the network caused loss of access to IS Contingency Plans resulting in inability to fail over critical systems to the alternate data center. Facilities Management kept control of all recovery efforts, freezing out CIOs office from assisting in damage assessment and recovery efforts when those activities were finally initiated. After approximately 12 hours, IT system owners and functional managers were trying to respond to an inordinate number of status requests and impact assessments. Result was 75 people were engaged in redundant and independent tasking. This presentation will provide a time line and the subsequent recommendations for integrating and enhancing incident response and keeping a minor incident from escalating into a disaster. | |||
| NA | AIO | ||
| ILT | 1.0 | ||
| Prerequisites | |||
