Title: DISASTER RECOVERY/ MAJOR OUTAGE COMMUNICATION PLAN



Similar documents
Incident Manager. Notified. Major Incident? YES. Major Incident Declared. Initial Communication Drafted. MIH At A Glance. Major Incident Ended

Title: DESKTOP TICKET MANAGEMENT PROCEDURE

Title: SLA INTRANET/EXTRANET

How To Manage Change Management At Uni

Disaster Recovery Plan Documentation for Agencies Instructions

Technology Recovery Plan Instructions

The University of Iowa. Enterprise Information Technology Disaster Plan. Version 3.1

Organization. Project Name. Project Overview Plan Version # Date

Technology Event Notification and Escalation Procedures. Procedure: Technology Event Notification and Escalation. Procedure Date: 10/27/2009

[name of project] Service Level Agreement

Fermilab Computing Division Service Level Management Process & Procedures Document

Policies of the University of North Texas Health Science Center

DOCUMENT HISTORY LOG. Description

White Paper: BMC Service Management Process Model 7.6 BMC Best Practice Flows

Annex E 24/7 EMERGENCY CONTACT PROTOCOL

DIRECTIVE NUMBER: v2.0. SUBJECT: Correctional Integration Systems Change Management Plan

Systems Support - Standard

Business Continuity Plan. Components and sequencing description

CITY UNIVERSITY OF HONG KONG Information Security Incident Management Standard

IT Security Incident Management Policies and Practices

Attachment N CPIC Vendor Resiliency Business Continuity Planning Questionnaire

Cyber Security Incident Handling Policy. Information Technology Services Center (ITSC) of The Hong Kong University of Science and Technology

Attachment E. RFP Requirements: Mandatory Requirements: Vendor must respond with Yes or No. A No response will render the vendor nonresponsive.

SERVICE LEVEL AGREEMENT. CUIT Converged Infrastructure: Infrastructure Services for VM Hosting

Creating a Business Continuity Plan. What We ll Cover... What is a BCP? Micky Hogue, CRM

BUSINESS CONTINUITY MANAGEMENT REQUIREMENTS FOR SGX MEMBERS NEW RULES FOR INCLUSION IN SGX-ST RULES

Enterprise UNIX Services - Systems Support - Extended

Internal Help Desk. Bizagi Suite

Hospital Authority. Enhanced Contingency Planning for IT System Failures

Analytics Reporting Service

Manage IT Service Continuity and Availability

Critical Systems Guidelines

IT SERVICE CONTINUITY AS RELATED TO THE MANAGEMENT OF ELECTRONIC RECORDS POLICY

SapphireIMS Service Desk Feature Specification

State of Ohio Private Cloud Managing Severity 1 Tickets

IT Disaster Recovery and Business Resumption Planning Standards

Continuity of Operations Planning. A step by step guide for business

Service Desk Management Process

Service Level Management

INSIDE. Preventing Data Loss. > Disaster Recovery Types and Categories. > Disaster Recovery Site Types. > Disaster Recovery Procedure Lists

Patent Public Advisory Committee Meeting. OCIO Update

Improving. Summary. gathered from. research, and. Burnout of. Whitepaper

Best Practices in Disaster Recovery Planning and Testing

OFFICE OF THE STATE AUDITOR General Controls Review Questionnaire

Position Description

Incident Management Policy

CISM Certified Information Security Manager

Disaster Recovery and Business Continuity

State Data Center. VMAX Data Migration Guide

RSA SecurID Tokens Service Level Agreement (SLA)

Contracting Guidelines with EHR Vendors

Institute for Business Continuity Training 1623 Military Road, # 377 Niagara Falls, NY

Client Security Risk Assessment Questionnaire

Mohawk DI-r: Privacy Breach Management Procedure Version 2.0. April 2011

Recovery Management. Release Data: March 18, Prepared by: Thomas Bronack

Attachment to Data Center Services Multisourcing Service Integrator Master Services Agreement

Template K Implementation Requirements Instructions for RFP Response RFP #

8 Best Practices for IT Incident Management

Offsite Disaster Recovery Plan

Attachment M Explore IRP Change Control Process

How to Plan for Disaster Recovery and Business Continuity

SERVICE LEVEL AGREEMENT

DETAILED RISK ASSESSMENT REPORT

Agenda. Creating a Robust Testing Program. Notification Tests. Overview of Testing. Beverly Schulz, CBCP

HP Service Manager. Software Version: 9.40 For the supported Windows and Linux operating systems. Processes and Best Practices Guide (Codeless Mode)

NEEDS BASED PLANNING FOR IT DISASTER RECOVERY

N e t w o r k E n g i n e e r Position Description

Six sigma project management

STATE OF NEVADA Department of Administration Division of Human Resource Management CLASS SPECIFICATION

Data Center Assistance Group, Inc. DCAG Contact: Tom Bronack Phone: (718) Fax: (718)

MANAGED SECURITY SERVICES RESPONSIBILITIES GUIDE July 2013

HP Service Manager. Software Version: 9.34 For the supported Windows and UNIX operating systems. Incident Management help topics for printing

Networx Training Q+As Repairs / Trouble Tickets

Blackboard Managed Hosting SM Disaster Recovery Planning Document

Support and Service Management Service Description

Overview of Service Support & Service

Customer Care Center Details

EMERGENCY PREPAREDNESS PLAN Business Continuity Plan

HIPAA RISK ASSESSMENT

SECURITY THROUGH PROCESS MANAGEMENT

Oregon Public Employees Retirement System

Annex 9: Technical proposal template. Table of contents

Business Continuity. Client Briefing

MEASURING FOR PROBLEM MANAGEMENT

Data Center Colocation - SLA

HP Service Manager. Software Version: 9.34 For the supported Windows and UNIX operating systems. Service Desk help topics for printing

For more information, please visit the IST Service Catalog at

IT Help Desk Call Priorities

Transcription:

POLICY: This policy is intended to address organizational wide communication executed during a or major IS service outage. When a disaster occurs or when any critical system/infrastructure component is unavailable for more than two hours the following procedure should be followed to ensure the appropriate contact occurs with management and end users. Examples of events or Major Outage are but not limited to Catastrophic loss of a Data Center Enterprise wide intrusion by hackers or a Computer virus/worm/trojan Horse Any complete outage of a critical system for more than 2 hours SCOPE: This policy applies without exception to all, and OCIO staff s. DEFINITIONS: I. Critical System Any application listed in the attached Critical Application List PROCEDURE: This section describes the detailed steps to be executed when this policy is activated ACTION 1. When any staff suspects may be experiencing a or Major Outage event follow the Identification. 2. Does the Identification indicate a or Major Outage a) If yes, refer to Policy # X.X.X: Problem Management Call Referral and Escalation / Notification b) If no, call the Help Desk to ensure the issue has been logged and assigned appropriately. End RESPONSIBLE PARTY DR-006 Recovery Communication Plan 9/8/2015 Page 1 of 5

ACTION 3. Is this a full scale expected to last more than 24 hours ( to be confirmed )? If yes, refer to Policy # X.X.X: DR Team Activation and go to step 4 If no, continue to step 6 4. Initiate Damage Assessment to determine the extent of the refer to Policy # X.X.X: Damage Assessment RESPONSIBLE PARTY 5. Does the DR Hot Site need to activated? Notify Executive Leadership of intent to declare. Contact Hot Site Vendor to activate the DR Hot Site. If yes, refer to Policy # X.X.X: Recovery Declaration If no, continue to 6 6. Is the / Major outage expected to last more than 8 hours (to be confirmed)? If yes, refer to Policy # X.X.X: Command Center Activation If no, continue to step 7 7. Ensure accurate and timely notifications and updates are distributed throughout management and user community. Refer to Policy # X.X.X Recovery / Major Outage Communication OCIO/ / Management Team 8. Refer to Policy # X.X.X / Major Outage Recovery Steps 9. Refer to Policy # X.X.X Post / Major Outage Analysis RELATED PROCEDURES: Identification. Problem Management Call Referral and Escalation / Notification DR Team Activation Damage Assessment Recovery Declaration Command Center Activation Recovery / Major Outage Communication / Major Outage Recovery Steps DR-006 Recovery Communication Plan 9/8/2015 Page 2 of 5

Post / Major outage Analysis ATTACHMENTS: A. Critical Application List B. Communication Scripts C. Management Notification Sheet D. Root Cause Analysis Report Template E. End User Contact Listings POLICY EXCEPTIONS: Date # Description Justification Signature None at this time DR-006 Recovery Communication Plan 9/8/2015 Page 3 of 5

PROCEDURAL PROCESS FLOW DIAGRAM: This Process flow represents the major steps to be taken in the event of a or Major Outage Staff Member identifies a or Major Outage / Major Outage Event Step1: Qualify / Quantify the extent of the Outage / 1 / Major Outage Identification No Notify Help Desk to ensure event has been resolved End Step 2: Ensure all, and staff are alerted to the severity of the situation 2 Call Escalation / Notification Step 4: Mobilize Damage Assessment Team to determine the full extent of the outage. Step3: Is the Outage / expected to last more than 24 hours. Initial Assessment Estimate Outage Duration < > 24 24 hours Damage Assessment Declaration? < 24 hours Step 6: If the Outage / Is expected to last more than 8 hours the Command Center should be established Outage Duration to last more than 8 hours > 8 hours Command Center Activation Recovery Declaration procedure Step 5: Notify hot site vendor of intent to declare. Notify senior management of intent to declare disaster No Step 7: Ensure Management and users are fully informed during the Outage to facilitate patient safety and business continuity. Recovery Major OutageCommunication Step 8: This step outlines some guiding principles that should be observed throughout the recovery process. / Major Outage Recovery Post Major Outage Analysis Recovery / Outage Report and Action Plan Step 9: This procedure describes the analysis required to determine the root cause of the event and creation of a future avoidance plan DR-006 Recovery Communication Plan 9/8/2015 Page 4 of 5

POLICY IDENTIFICATION: Policy Title: Recovery/ Major Outage Communication Plan Category: Recovery Original Date: Author: Approved By: Title Signature Stakeholder Representatives Executive Executive REVIEW/REVISION HISTORY: Version Review Date Next Review Date Changes (Y or N) Description of Change (section and description) Review/Revision by Revision(s) approved by Title Signature Title Signature 1.0 Original Initial draft DR-006 Recovery Communication Plan 9/8/2015 Page 5 of 5