Spring World 2018

Conference & Exhibit

Attend The #1 BC/DR Event!

Winter Journal

Volume 30, Issue 4

Full Contents Now Available!

Wednesday, 15 November 2017 22:02

Aim for Effective Incident Response, Not Just Disaster Recovery

Written by  RAMESH WARRIER

Business disruptions that cannot be contained using standard operating procedures (SOPs) can be classified as incidents. An incident may cause disaster recovery and/or business continuity plans to be invoked. Those invoked activities are an incident response. Think of incident response in three distinct parts:Activation. Knowing which plans to invoke requires an assessment of what assets (hardware, applications, interfaces, etc.) and services have been impacted. Assessments focus the scope of the incident response. Intelligent assessments, combined with situational awareness information, allow incident managers to invoke the appropriate plans, recovery teams, and resources. Plans based on scenarios (failover to an alternate data center, or reconstruction at a DR site, restore Tier 0 and Tier 1 apps) can be a quick-start incident response without conducting a detailed assessment. Recovery. After plan activation, monitoring of execution is critical to the effectiveness and success of the response. Plans constructed as a series of tasks (rather than broad instructions)