Information Services

Disaster Response and Recovery Plan

Central Washington University400 East University Way

Ellensburg, Washington 98926-7436509.963.2333

Updated by

Networks & OperationsUpdated October 2013

Revision History Page

Rev # Change Date1 Initial Release DRP - Networks & Operations 1-Jun-19932 Update DRP - Networks & Operations 1-Nov-1996

2.1 Reviewed DRP - Networks & Operations 2-Aug-20082.2 Reviewed DRP - Networks & Operations 3-Aug-20083 Rewrite of DRRP - Networks & Operations 6-Mar-2008

3.1 Minor Updates DRRP - Networks & Operations 6-Aug-2008

 3.2Updated Personnel Names DRRP – Networks & Operations 7-Apr-2008

3.3 Minor Updates DRRP – Networks & Operations 7-Aug-2008 3.4 Personnel Updates – Networks & Operations 8-Feb-20083.5 New Recovery Team -- Networks & Operations 14-Apr-20083.6  Staffing, Building Updates – Networks & Operations August-2009 3.7 Staffing Updates – Networks & Operations January-2012 3.8 Staffing Updates – Networks & Operations August-2013 3.9 Department Renamed – Networks & Operations September-2013

Official copies of this document are located at the following locations:

- Information Services Department Office- Computer Support Services Managers Office- Central Computer Facility Operations Office- Hebeler Tape Vault- Office and Home of AVP for Information Technology- Network and Operations Directors Office- IT Security Administrators Office

NAMES Dept. NUMBER Cell Phone NAMES Dept. NUMBER Cell Phone

2

Alviso, Jose N&O 1743   Velasquez, Charles EAS 3048  

Andrin, Marion Aux 1891   Varga, Steve EAS 2953  

Anderson, Lidia EAS 3046   Vincent, Kathy CSS 2544 859-3986Ashbrooks, Steve Telecom 3442 899-1865 Wang, Crystal EAS 2643  Beintema, Jami IS 2333   Wang, Xinbao EAS 2945  

Beintema, Larry N&O 2905 899-0347 Webber, Maury CaTS 3752425-471-

1227Breckon, Ron N&O 3694   Wixson, Heidi EAS 2969  Brower, Doug EAS 2356   Young, Ken CaTS 3491  Brown, Rock EAS 2999          Burk, Nicole EAS 3046      Carlson, Barry EAS 2904   OTHER IMPORTANT NUMBERS  Case, Felicia Aux 2903   ISD Main Directory   2924

Cathcart, Jason N&O 1223   ISD Help Desk(Direct 1102) 2001/3491

Cusumano, Pete CaTS 3834 425-471-1593ISD - Main Office Front Desk MS 7436 2333

DeLuca, Greg N&O 2970 859-2884 ResNet Help Desk   2200Dohrman, Gayle EAS 3054   Aux. Services MS 7589 2936Douglas, Steven N&O 1232 856-6581 Computer Center MS 7444 3694Firman, Marla CSS 1250 859-1112 Telecommunications MS 7437 3425Gerdes, Jason N&O 2995 431-5030 Telephone Repair Line   2007Germain, Dave CSS 2996   Conference Room   1645Germain, Terilee N&O 2946 899-1696 IT Project Room   1477Gladen, Jeff CSS 1606   ISD Auto Attendant   2924Glessner, Bill N&O 3694 899-0999 Blackboard   2001Haberman, Susie EAS 2944   TDD   3323Halvorson, Colleen CaTS 3499

206-218-6541 (P) PPP Dial-in Modem   8000

Hart, David N&O 2932 509-306-2128 VAX Dial-in Modem   3998/3999Hendrickson, Teri Telecom 3422      Hernandez, Uriel EAS 2967   FAX NUMBERS  Hernandez, Jill EAS 1268   ISD 1385Hill, Nathan Aux 2942   CSS & CaTS 2445Herrera, Steven EAS 1209   Telecommunications 1241Hunt, Debbie EAS 3015      Hutchins, Lynn EAS 2288   BUILDING MONITORS  Jackson, Nancy Telecom 3333 899-0136 BB Sandy Sperline (Bouillon Hall - 2nd floor) 2989Jakeman, Jared EAS 1615   Ron Breckon (Computer Center) 3694Jones, Frank CaTS 2856      

Jones, KeithProj.

Mgmt. 2191 856-6219 BB 112/128 STUDENTS/TEMPS  Klampher, Tina CSS 2778 899-4818 CSS Student 3376Knackstedt, Jeff CSS 2352   Student (Help Desk ) 3043Lei, Vera EAS 2972      Lunstrum, Lucinda EAS 2626      McGuire, Tim EAS 2329   202 STUDENTS/TEMPS  Miller, Bill CSS 3490   Student (Front Office) 2769Osguthorpe, Jared EAS 2954      Patterson, Randy Telecom 3653/3649 899-2827    Pierce, Tad Aux 2997 899-0092    Pratz, Chris CS 1581 899-3220    Pruitt, Jim CSS 3472 899-0145 ResNet  

Shoda, GeneAVP-

IS/CIO 2777   ResNet Help 2200Richardson, Wade Telecom 3424 856-6867    Ringer, Jason EAS 2394      

3

Rodriguez, Noah N&O 2934 626-393-4069  Shelton, Debby Telecom 3428      Smith, Zachary N&O 2864 607-4756    Sperline, Sandy CSS 2989 607-1618    Swayze, Stacy CSS 1572      Thomas, Jamie EAS 1205      Timmons, Chris N&O 2947 856-7894    Tran, Kim EAS 2994      

4

Information Services (IS Department)Disaster Response and Recovery Plan

TABLE OF CONTENTS

Section Title Page1 Introduction 52 Scope 63 Assumptions 74 Definitions 85 Team Members and Contact Information 10

5.1 Aux Services Recovery Team 115.2 Data Center Recovery Team 125.3 Desktop Recovery Team 135.4 Messaging/Networks & Web Recovery Team 145.5 PeopleSoft Recovery Team 155.6 ResNet Recovery Team 165.7 Telecommunications Recovery Team 175.8 CWU Critical Support Contacts 18

6 Disaster Preparedness 196.1 Data Recovery Information 196.2 Central Data Center and Server Recovery Information 206.3 Network and Telecommunication Recovery Information 206.4 Application Recovery Information 206.5 Desktop Equipment Recovery Information 207 Disaster Recovery Processes & Procedures 21

7.1 Emergency Response 217.2 Incident Command Team 217.3 Disaster Recovery Teams 227.4 General System Application Recovery 258 Network and Telecommunication Guidelines 27

AppendicesA IT Directory and Contact List 28B CWU Critical Contacts 30C Asset Management Information 31D Backup Tape Retention Periods 32E Recovery Priority List 35F Vendor Information 39G Network Diagrams 47H Excerpt from Emergency Preparedness Plan 48J Business Impact Matrix 50K Threat and Vulnerability Matrix 51L Tape Inventory 53

5

1.0 INTRODUCTION

Central Washington University is a four year institute of higher education. Faculty, staff and students all rely heavily on the Information Technology (IT) infrastructure and services to accomplish their jobs, and as an integral part of the learning environment/curriculum at the university.

As a result of this reliance, IT services are considered a critical component in the daily operations at Central Washington University, requiring a comprehensive Disaster Response and Recovery Plan (DRRP) to assure that these services can be re-established quickly and completely in the event of a disaster of any magnitude.

Response to and recovery from a disaster at Central Washington University is managed by the Emergency Council Members, named in section 2 of the Emergency Preparedness Plan. Their actions are governed by the Central Washington University Safety and Emergency Preparedness plan located at http://www.cwu.edu/police/sites/cts.cwu.edu.police/files/documents/safetyatcwubrief.pdf.

This IT DRRP presents the requirements and the steps that will be taken in response to and for the recovery from any disaster affecting IT services at Central Washington University, with the fundamental goal of allowing basic business functions to resume and continue until such time as all systems can be restored to pre-disaster functionality.

At this time Central Washington University does not run on redundant servers which would minimize potential business disruption in the event of a disaster, nor does the university possess a redundant “warm-site” or “hot-site” for quick recovery of the Data Center. Should more resources become available this plan will be re-evaluated and updated accordingly.

This plan is reviewed and updated yearly by August by IS/Networks & Operations staff and approved by the Assistant VP for Information Technology.

A hard copy of this plan is stored in the following areas: - Hebeler vault - IS/Networks & Operations (Terilee Germain’s Office) - Bouillon 218 Comm Room - Computer Center - Auxiliary Wall Safe

6

2.0 SCOPE

Due to the uncertainty regarding the magnitude of any potential disaster on the campus, this plan will only address the recovery of systems under the direct control of the Department of Information Technology Services and that are critical for business continuity. This includes the following major areas:

PeopleSoft Systems (payroll, AP/AR, financial aid, finance, safari) Central Computer Facility (Wildcat Shop) Electronic Mail and Web Services Desktop Equipment, Labs, Classrooms Data Networks and Telecommunications (networks, file services, telephony) Auxiliary Computing (Conference Center, Facilities, Parking, University Store, CBORD Dining

Services, Housing, Health, ResNet, Student Recreation)

This plan covers all phases of any IT related disaster occurring at Central Washington University. These phases include:

Incident Response Assessment and Disaster Declaration Incident Planning and Recovery Post incident Review

At this time Central Washington University does not run on redundant servers nor possess a redundant “warm-site” or “hot-site” for training or testing purposes. Should these resources become available this plan will be updated to fully detail training and testing of this plan.

7

3.0 ASSUMPTIONS

This disaster response and recovery plan is based on the following assumptions:

Once an incident covered by this plan has been declared a disaster, the appropriate priority will be given to the recovery effort and the resources and support required as outlined in the IT DRRP will be available.

The safety of students, staff and faculty are of prime importance and the safeguard of such will supersede concerns specific to hardware, software and other recovery needs.

Depending on the severity of the disaster, other departments/divisions on campus may be required to modify their operations to accommodate any changes in system performance, computer availability and physical location until a full recovery has been completed. Information Technology Services will encourage all other departments to have contingency plans and Business Continuity Plans for their operations, which include operating without IT systems for an extended period of time.

The content of this plan may be modified and substantial deviation may be required in the event of unusual or unforeseen circumstances. These circumstances are to be determined by the specific Disaster Response and Recovery Teams under the guidance and approval of the Incident Director and Incident Command Team.

8

4.0 DEFINITIONS: The following definitions pertain to their use in this IT Disaster Recovery Plan.

   Auxiliary Services Recovery Team:

Individuals responsible for the recovery and testing of Auxiliary Computing technology. Team lead is the Manager of Auxiliary Computing. (Nathan Hill)

Backup/Recovery Tapes: Copies of all software and data located on the central servers, which are used to return the servers to a state of readiness and operation that existed shortly prior to the incident/disaster.

Catastrophic Disaster: A catastrophic disaster will be characterized by expected downtime of greater than 7 days. Damage to the system hardware, software, and/or operating environment requires total replacement / renovation of all impacted systems.

Cold Recovery Site: Alternate Data Center which has adequate power and networking infrastructure to support the critical IT systems used by the university. A cold site does not have backup servers and other IT equipment and software already in place. CWU does not have a designated Cold Recovery Site at this time.

Database Recovery Team Individuals responsible for the recovery and testing of CWU Databases. Team lead is DBA Admin. (Vacant)

Data Center Recovery Team: Individuals responsible for the establishment of an operational data center, either by returning the primary center to operational status or by bringing a Cold Site online for use. Team lead is the Director of Networks and Operations. (Jason Cathcart)

Desktop Recovery Team: Individuals responsible for the recovery and testing of desktop computers and services, classrooms and labs in the affected areas at Central Washington University. Team lead is the Manager of Computer Support Services. (Chris Pratz)

Disaster Recovery Team (DRT):

The DRT is a team of individuals with the knowledge and training to recover from a disaster. For IS, there are 6 teams for specific IT areas to be addressed.

Disaster: Any IT incident which is determined to have potential impacts on the business continuity and ongoing operations of Central Washington University.

Emergency Response Team (ERT):

The ERT is the first to respond to an incident, to secure and contain the situation. The ERT may consist of firemen, police, security, and other specialized individuals.

Equipment Configuration Database:

A database (either soft or hardcopy) which documents the configuration information necessary to return any IT hardware (server, network, desktop) to pre-disaster configurations. This includes hardware revisions, Operating System revisions, and patch levels.

Incident Command Headquarters

Location where the ICTs meet and coordinate all activities with regard to assessment and recovery. For the CWU IS Department, the headquarters are located at:

Primary: IS Conference Room (Bou-202)Secondary: Barge Conference Room (Barge 412)Backup 1: Library Classroom Lab (Lib 154)Backup 2: Shaw Smyser Lab (SS214)

Incident Command Team (ICT):

The ICT is a group of IT individuals with combined knowledge and expertise in all aspects of the IT organization. It is the responsibility of the ICT to perform the initial assessment of the damage, to determine if a formal “disaster” declaration is required and to coordinate activities of the various

9

IT DRTs. Incident Director (ID): The Incident Director leads all efforts during the initial assessment of the

incident, in conjunction with the Incident Command Team (ICT). If a disaster is declared, the ID is responsible for overall coordination of all IT related recovery activities. For Central Washington University, the Incident Director is the Assistant VP of Information Technology. (Gene Shoda)

Incident: Any non-routine event which has the potential of disrupting IT services to Central Washington University. An incident can be a fire, earthquake, significant hardware failure, flood, volcano ash, virus, Trojan horse, etc.

Major Disaster: A major disaster will be characterized by an expected downtime of more than 48 hours but less than 7 days. A major disaster will normally have extensive damage to system hardware, software, networks, and/or operating environment.

Messaging/Networks & Web Recovery Team:

Individuals responsible for the recovery and testing of messaging systems at CWU including email, calendaring, and Web technologies. Responsible for the recovery and testing of the data networks and file servers. Team lead is the Director of Network and Operations. (Jason Cathcart)

Minor Disaster: A minor disaster will be characterized by an expected downtime of no more than 48 hours, and minor damage to hardware, software, and/or operating environment from sources such as fire, water, chemical, sewer or power etc.

PeopleSoft Recovery Team: Individuals responsible for the recovery and testing of the PeopleSoft systems. Team lead is Director of Application Services. (Vacant)

Resnet Recovery Team: Individuals responsible for the recovery and testing of the Resnet Services. Team lead is the Director of Networks and Operations. (Jason Cathcart)

Routine Incident: A routine incident is an IT situation/failure that is limited in scope and is able to be addressed and resolved by a specific team or individual as part of their normal daily operations and procedures. Incidents which are not of magnitude to be classified as formal disasters and considered “routine” incidents and are handled accordingly.

Telecommunications Recovery Team:

Individuals responsible for the recovery and testing of voice networks. Team lead is the Supervisor of Telecommunications. (Nancy Jackson)

Web Services: All services related to Central Washington University’s Internet and Intranet Web activities and presence. The primary Web Service provided by CWU is the homepage at www.cwu.edu.

10

5.0 TEAM MEMBERS & CONTACT INFORMATION:

5.0.1 Incident Director:

Name: Gene ShodaHome Phone:Cell Phone:Home Email:

5.0.2 Incident Command Team: All Contact Information is located in Appendix A

Name: Gene Shoda, Assistant VP for Information Technology

 Jason Cathcart, Director Networks & Operations (Alternate Incident Director)

  Vacant, Director Enterprise Application Services  Chris Pratz, Manager of Computer Support Services  Nancy Jackson, Manager of Telecommunications  Nathan Hill, Manager of Auxiliary Computing  

5.0.3 CWU Management Team: All Contact Information is located in Appendix B

Name: James Gaudino, President CWU  Marilyn Levine, Provost/VP for Academic and Student Life  George Clark, VP for Business and Financial Affairs  John Swiney, VP for Student Affairs and Enrollment Management  Linda Schactler, VP for University Relations

11

5.1 AUXILIARY SERVICES RECOVERY TEAM: All Contact Information is located in Appendix A

The Auxiliary Services Recovery Team is composed of the IT Specialists within Information Technology Services that support the Auxiliary systems. The primary function of this small working group is the restoration of the Auxiliary applications to the most recent pre-disaster configuration in cases where data or operational loss is significant. In less severe circumstances the team is responsible for restoring the systems to an operational status as necessitated by any hardware failures, network outages or other circumstances that could result in diminished system performance.

The team should be mobilized in the event that the Auxiliary systems experiences a significant interruption in service that has resulted from unexpected/unforeseen circumstances and requires recovery efforts in excess of what is experienced on a normal day-to-day basis.

The Manager of Auxiliary Services has the responsibility to keep the IT Incident Director up to date regarding the nature of the disaster and the steps being taken to address the situation. The coordination of the Auxiliary Services recovery effort will be accomplished with other recovery efforts on campus by the IT Incident Director.

System Name: Nathan Hill (Recovery Team Lead)Housing Marion AndrinDining (Kronos) Nathan HillComputrition Larry BeintemaCBORD Tad PierceFacilities Ed CastanedaHealth Nathan HillResnet Nathan Hill, Felicia CaseStudent Recreation Nathan HillStore-POS Tad Pierce, Nathan HillConference Center Felicia CaseWork Order System Aux Nathan HillTrade Book Nathan HillQuasar.cts.cwu.edu DBA Team

12

5.2 DATA CENTER Recovery Team: All Contact Information is located in Appendix A

The Data Center Recovery Team is composed of personnel within Information Technology Services that support Central Washington University’s central computing environment and the primary data center where all central IT services, the Networks Operations Center (NOC) and other central computing resources are located. The primary function of this small working group is the restoration of the existing data center or the activation of the secondary data center depending on the severity of the disaster. This team’s role is to restore the data center to a condition where individual recovery teams can accomplish their responsibilities with regard to server installation and application restoration.

The team should be mobilized only in the event that a disaster occurs which impacts the ability of the existing central computing facility to support the servers and applications running there.

The Director of Network and Operations has the responsibility to keep the IT Incident Director up to date regarding the nature of the disaster and the steps being taken to address the situation. The coordination of this recovery effort will normally be accomplished prior to most other recovery efforts on campus as having a central computing facility is a prerequisite for the recovery of most applications and IT services to the campus.

System Name:Jason Cathcart (Recovery Team Lead)

Operations Coordinator Ron BreckonNetworks Chris Timmons (Alternate Team Lead)Networks David HartOperations Support Bill GlessnerWeb Management Larry BeintemaNetware Servers Greg DelucaBlackboard Larry BeintemaCommunications Infrastructure Steve Ashbrooks

13

5.3 DESKTOP Recovery Team: All Contact Information is located in Appendix A

The Desktop Recovery Team is composed of personnel within the Information Technology Department that support Central Washington University’s desktop hardware, client applications, classrooms, labs and academic development systems. The primary function of this small working group is the restoration of Central Washington University’s desktop systems, classrooms and labs to usable condition. During the initial recovery effort, the team is not responsible for restoration of any data the user may have on their desktop computer. Central Washington University recommends all users store data files on the file servers, which are backed up nightly, to support data recovery.

The team should be mobilized in the event that any component of the network or telecommunication infrastructure experiences a significant interruption in service that has resulted from unexpected/unforeseen circumstances and requires recovery efforts in excess of what is experienced on a normal day-to-day basis.

The Manager of Computer Support Services has the responsibility to keep the IT Incident Director up to date regarding the nature of the disaster and the steps being taken to address the situation. The coordination of this recovery effort will be accomplished with other recovery efforts on campus by the IT Incident Director.

System Name: Chris Pratz (Recovery Team Lead)

IT SpecialistDave Germain (Alternate Team Lead)

IT Specialist/Primary Bill MillerPCs Tina KlampherMACs Jeff KnackstedtLabs Jim Pruitt, Jeff KnackstedtClassroom Technology Sandy SperlineAlternates Stacy Swayze

14

5.4 MESSAGING/NETWORKS AND WEB Recovery Team: All Contact Information is located in Appendix A

The Messaging/Networks and Web Recovery Team is composed of personnel within Information Technology Services that support Central Washington University’s network infrastructure including all cable plants, switches, routers, network applications, file servers, electronic email servers and web services. The primary function of this small working group is the restoration of Central Washington University’s LAN and servers to the most recent pre-disaster configuration in cases where data and network loss is significant. In less severe circumstances, the team is responsible for restoring the system to an operational status as necessitated by any network hardware failures or other circumstances that could result in diminished performance.

The team should be mobilized in the event that any component of the network infrastructure experiences a significant interruption in service that has resulted from unexpected/unforeseen circumstances and requires recovery efforts in excess of what is experienced on a normal day-to-day basis.

The Director of Network and Operations has the responsibility to keep the IT Incident Director up to date regarding the nature of the disaster and the steps being taken to address the situation. The coordination of this recovery effort will be accomplished with other recovery efforts on campus by the IT Incident Director.

System Name: Jason Cathcart (Recovery Team Lead)Networks Chris Timmons (Alternate Team Lead)Web Services Larry BeintemaEmail Services Bill GlessnerNetworks David HartServers Greg DelucaAlternates Terilee GermainCable Plants Steve Ashbrooks

15

5.5 PEOPLESOFT Recovery Team: All Contact Information is located in Appendix A/B

The PeopleSoft Recovery Team is composed of the IT Specialists within Information Technology Services that support the PeopleSoft system as well as the User Application Specialists and a Network Specialist. The primary function of this small working group is the restoration of all modules of the PeopleSoft application to the most recent pre-disaster configuration in cases where data loss is significant. In less severe circumstances the team is responsible for restoring the system to an operational status as necessitated by any hardware failures, network outages or other circumstances that could result in diminished system performance.

The team should be mobilized in the event that the PeopleSoft HRSA and/or FM systems experience a significant interruption in service that has resulted from unexpected/unforeseen circumstances and requires recovery efforts in excess of what is experienced on a normal day-to-day basis.

The Director of Application Services has the responsibility to keep the IT Incident Director up to date regarding the nature of the disaster and the steps being taken to address the situation. The coordination of the PeopleSoft recovery effort will be accomplished with other recovery efforts on campus by the IT Incident Director.

System Name: Vacant (Recovery Team Lead)DBA Jason Ringer (Alternate Team Lead)DBAPSApps Jason OsguthorpeSecurity Jamie SchademanWeb Services Larry BeintemaPayrollHR Susan HabermanSA Crystal WangFMS   Data Validation:  Admissions Kathy GaerHR/Payroll

SAAdrian NaranjoJillian Hernandez, Tami Morrill

FMS Tim McGuire

16

5.6 RESNET SERVICES RECOVERY TEAM: All Contact Information is located in Appendix A

The Resnet Services Recovery Team is composed of the IT Specialists within Information Technology Services that support the Resnet services. The primary function of this small working group is the restoration of the Resnet services to the most recent pre-disaster configuration in cases where data loss is significant. In less severe circumstances the team is responsible for restoring the networks to an operational status as necessitated by any hardware failures, network outages or other circumstances that could result in diminished system performance.

The team should be mobilized in the event that the Resnet services experiences a significant interruption in service that has resulted from unexpected/unforeseen circumstances and requires recovery efforts in excess of what is experienced on a normal day-to-day basis.

The Director of Networks and Operations has the responsibility to keep the IT Incident Director up to date regarding the nature of the disaster and the steps being taken to address the situation. The coordination of the Resnet Services recovery effort will be accomplished with other recovery efforts on campus by the IT Incident Director.

System Name: Nathan Hill (Recovery Team Lead)Networks Chris Timmons, Jason GerdesAuxiliary Services Nathan Hill, Jose AlvisoTelecom Nancy Jackson, Randy Patterson

17

5.7 TELECOMMUNICATIONS Recovery Team: All Contact Information is located in Appendix A

The Telecommunications Recovery Team is composed of personnel within the Information Technology Department that support Central Washington University’s voice networks. The primary function of this small working group is the restoration of Central Washington University’s voice networks to the most recent pre-disaster configuration in cases where voice network loss is significant. In less severe circumstances, the team is responsible for restoring the voice network to an operational status as necessitated by any failures or other circumstances that could result in diminished performance.

The team should be mobilized in the event that any component of the network infrastructure experiences a significant interruption in service that has resulted from unexpected/unforeseen circumstances and requires recovery efforts in excess of what is experienced on a normal day-to-day basis.

The Manager of Telecommunications has the responsibility to keep the IT Incident Director up to date regarding the nature of the disaster and the steps being taken to address the situation. The coordination of this recovery effort will be accomplished with other recovery efforts on campus by the IT Incident Director.

System Name: Nancy Jackson (Recovery Team Lead)PBX Randy Patterson (Alternate Team Lead)Networks Wade RichardsonNetworks Steve Ashbrooks

18

5.8 CWU CRITICAL SUPPORT CONTACTS: All Contact Information is located in Appendix B

On Campus Contacts:  President's Office James Gaudino, PresidentProvost Marilyn Levine, VPBusiness and Financial Affairs George Clark, VPStudent Affairs and Enrollment Management John Swiney, VPUniversity Relations Linda Schactler, VPFacilities Management Bill Yarwood, Bob Tosch, Public Safety and Police Services Michael Luvera, DirectorHealth Center Jackson Horsley, Medical DirectorUniversity Housing Richard DeShields, Director            Off Campus Contacts:  Fairpoint Communications Bill Malasich, Patrick MurphyK20 Administrative Contact Steve PaulsonCity of Ellensburg (Inet) Bob JohnsonK20 Internet Circuit noc@wa-k20.netCharter Communications Ron GraaffK20 Point-To-Point Circuits Washington State DIS Helpdesk

19

6.0 DISASTER PREPAREDNESS

A critical requirement for disaster recovery is ensuring that all necessary information is available to assure that hardware, software, and data can be returned to a state as close to “pre-disaster” as possible. Specifically, this section addresses the backup and storage policies as well as documentation related to hardware configurations, applications, operating systems, support packages, and operating procedures.

6.1 Data Recovery Information:

Backup/Recovery disks and tapes are required to return systems to a state where they contain the information and data that was resident on the system shortly prior to the disaster. At Central Washington University full backups of all servers are performed weekly. Those servers not in the full backup list have an incremental done. Backup/Recovery tapes are stored in the locations and for the retention periods outlined in Appendix D, and are summarized in the table below:

Backup Period Storage Location Authorized PersonnelDaily Backup Backup Unit

Wildcat ShopCentral Washington University

Networks and Operations Personnel

Weekly Backup Backup UnitWildcat ShopCentral Washington University

Networks and Operations Personnel

Monthly Backup CWU VaultHebeler HallCentral Washington University

Operations Personnel

Yearly Backup CWU VaultHebeler HallCentral Washington University

Operations Personnel

NOTE: Central Washington University does not have systems in place to backup and restore information/data located on individual desktop systems throughout the campus. Only the servers located in the Data Center and auxiliary Data Centers are backed up, as such only data resident on these systems will be able to be recovered. In the event that a disaster occurs on the campus which destroys personal computers, the information located on these computers will be extremely difficult or impossible to recover. If recovery is possible, it will require outside vendor involvement at great expense to the user.

The Information Technology Services recommends and will encourage the use of network drives (on servers) to store all important files. The recovery of data not backed up to a network drive and/or full system backups are not covered under this plan.

A cloned disaster recovery backup unit is in place in Bouillon 218 in a secured and alarmed communications room. This unit is for the purpose of off-site cloning of tapes. Networks & Operations Staff is responsible for the daily cloning of tapes for the purpose of disaster recovery.

20

6.2 Central Data Center and Server Recovery Information:

In the event of any disaster which disrupts the operations in the Data Center, reestablishing the Data Center will be the highest priority and a prerequisite for any IT recovery. As such, Information Technology Services is required to have detailed information and records on the configuration of the Data Center and all servers and ancillary equipment located in the Data Center and auxiliary Data Center located in the SURC building. Detailed information is documented in the online database located at http://www.cwu.edu/~its/security/hardware.php. This database is updated and copied monthly to CD and stored in the Hebeler vault with the backup tapes. The operations staff is responsible for keeping the hardware inventory up to date.

6.3 Network & Telecommunication Recovery Information:

In the event of any disaster which disrupts the network and/or telecommunications, reestablishing the connectivity and telephony will be a high priority and a prerequisite for any IT recovery. Recovery of these services will be accomplished in parallel or immediately following recovery of the Data Center. As such, Information Technology Services is required to have detailed information and records on the configuration of the networking equipment. Detailed information of switches and routers is documented in the online database located at http://www.cwu.edu/~its/security/hardware.php. This database is updated and copied monthly to CD and stored in the Hebeler vault with the backup tapes. The networking staff is responsible for keeping the networking inventory up to date.

6.4 Application Recovery Information:

Information necessary for the recovery and proper configuration of all application software located on the central servers is critical to assure that applications are recovered in the identical configuration as they existed prior to the disaster. Detailed information on critical central applications will be documented in the online database located at http://www.cwu.edu/~its/security/hardware.php. This database is updated and copied monthly to CD and stored in the Hebeler vault with the backup tapes. Server administrators are responsible for keeping the application inventory up to date.

6.5 Desktop Equipment Recovery Information:

Information necessary for the recovery and proper configuration of all desktop computers and printers supported by Computer Support Services is critical to assure that client systems can be restored to a configuration equivalent to pre-disaster status. Detailed information on client systems (both PC and MAC) is documented at http://www.cwu.edu/~its/security. This web site is backed up nightly.

21

7.0 DISASTER RECOVERY PROCESSES AND PROCEDURES:

7.1 Emergency Response: The requirement for an Emergency Response Team (ERT) involvement and the membership of the ERT will be dependent on the size and type of the incident. In addition, the actions of the ERT will be accomplished prior to the execution of this plan. Examples of situations which will normally result in the involvement of the ERT include:

Severe structural damage to the facility where personal safety is in question, and where analysis must be completed to assure the building is acceptable for access. This would include, but is not limited to, damage from an earthquake or tornado.

Environmentally hazardous situations such as fires, explosions, or possible chemical or biological contaminations where the situation must be contained prior to building occupancy.

Flooding or other situations which may pose the risk of electrical shock or other life-threatening situations.

Examples of situations which will normally not result in the involvement of the ERT include:

Major system/hardware failures that do not pose a hazard to personnel or property. Utility outages (electrical, etc.) which are remote to the Data Center being affected.

NOTE: For any situation/incident which requires the involvement of an ERT; the IT Incident Director, Incident Command Team, nor any Recovery Team member will access the facility until the ERT leader has authorized access. The Emergency Preparedness Plan is located at: http://www.cwu.edu/~police/docs/emergency-preparedness-plan.pdf.

7.2 Incident Command Team: The role of the IT Incident Command Team (under the direction of the Incident Director) is to coordinate activities from initial notification to recovery completion. Primary initial activities of the team are:

Incident Occurrence: Upon the occurrence of an incident affecting the IT services at Central Washington University, the President & Assistant Vice President of Information Technology will be notified by campus security and/or other individuals. Personnel reporting the incident will provide a high-level assessment as to the size and extent of the damage. Based on this information, the AVP of IT will assume his/her responsibilities as the Incident Director, and will contact the other members of the ICT, and provide them with the following basic information:

Brief overview of the incident, buildings affected, etc. Which Incident Command Headquarters (ICH) will be used Scheduled time to meet at the ICH for initial briefing Any additional information beneficial at this point. No other staff members are to be contacted at

this point, unless directed by the Incident Director.

Incident Command Headquarters (ICH) locations are:

Primary ICH: IS Department Conference Room (Bouillon 202) Secondary ICH: Barge Conference Room (Barge 412) Backup ICH 1: Library Classroom Lab (Library 154) Backup ICH 2: Shaw Smyser Lab (SS214)

Should all of these facilities be rendered unusable, it is assumed that the disaster was “catastrophic” in nature and that the technology recovery effort will be secondary to other concerns. At this point, the IT Incident Director will work closely with overall CWU Disaster Recovery Management to determine the appropriate course of action. The ID is responsible for locating an alternate site for the team and re-evaluating the best strategy for recovery.

22

Incident Assessment: The Incident Command Team (ICT) will receive an initial briefing from the Incident Director (ID) and any other personnel invited to the meeting (ERT personnel, etc.) The ICT will assess the situation, perform a walk-through of affected areas as allowed, and make a joint determination as to the extent of the damage and required recovery effort. Based on this assessment, the team will make a determination as to whether the situation can be classified as “routine” and handled expeditiously via normal processes, or if a formal IT disaster needs to be declared.

ROUTINE: Area(s) affected by the incident are identified and the appropriate personnel are contacted to report to work to evaluate and resolve the situation.

DISASTER: The Incident Director contacts the CWU Management Team Lead (CWU President or designee) and notifies him/her of the situation, and that an IT Disaster has been declared. The ICT identifies which areas of the IT infrastructure is affected, and contacts the members of the specific Disaster Recovery Teams. Team members are provided with the following information:

o Brief overview of what occurredo Location and time for teams to meeto Additional information as required. Team members are not to discuss any information

provided with other personnel employed or not employed at CWU.

Once an IT disaster has been declared, and the preceding steps to notify the CWU Management Team and the Recovery Teams have been accomplished, ongoing responsibilities of the Incident Command Team and Director include:

Securing all IT facilities involved in the incident to prevent personnel injury and minimize additional hardware/software damage.

Supervise, coordinate, communicate, and prioritize all recovery activities with all other internal / external agencies. Oversee the consolidated IT Disaster Recovery plan and monitor execution.

Hold regular Disaster Recovery Team meetings/briefings with team leads and designees. Appointing and replacing members of the individual recovery teams who are absent, disabled, ill or

otherwise unable to participate in the process. Provide regular updates to the CWU Management Team on the status of the recovery effort. Only

the CWU Management Team and/or their designees will provide updates to other campus and external agencies (media, etc.)

Approve and acquire recovery resources identified by individual recovery teams. Interface with other activities and authorities directly involved in the Disaster Recovery (Police,

Fire, Department of Public Works, CWU Teams, etc.) Identify and acquire additional resources necessary to support the overall Disaster Recovery effort.

These can include 1) acquiring backup generators and utilities, 2) arranging for food/refreshments for recovery teams, etc.

Make final determination and assessment as to recovery status, and determine when IT services can resume at a sufficient level.

7.3 Disaster Recovery Teams: Seven Disaster Recovery Teams are organized to respond to disasters of various type, size, and location. Any or all of these teams may be mobilized depending on the parameters of the disaster. It is the responsibility of the ICT to determine which Disaster Recover Teams to mobilize, following the declaration of a disaster and notification of the Central Washington University Management Team.

Each team will utilize their respective procedures, disaster recovery information, technical expertise, and recovery tools to expeditiously and accurately return their systems to operational status. While recovery by multiple teams may be able to occur in parallel, the Data Center and Network/Telecommunications

23

infrastructure will normally be assigned the highest priority, as full operational recovery of most other systems can not occur until these areas are operational.

7.3.1 Auxiliary Services Recovery Team:

1. Take appropriate steps to safeguard personnel and minimize damage to any related equipment and/or software.

2. Assess damage and make recommendations for recovery to Auxiliary Services.3. Identify other individuals required to assist in recovery of these applications, and report this information

to the ID for action.4. Restore degraded system functions at backup site and inform user community of the restrictions on

usage and/or availability.5. Coordinate software replacement with vendor as required. (See Appendix F for vendor and contact

information)6. Coordinate Auxiliary Services recovery with other recovery efforts.7. Execute plan to the Auxiliary Services to full function.8. Provide scheduled recovery status updates to the Incident Director to ensure full understanding of the

situation and the recovery effort.9. Verify and certify restoration of the Auxiliary Services to pre-disaster functionality.

7.3.2 Database Recovery Team:

1. Take appropriate steps to safeguard personnel and minimize damage to any related equipment and/or software.

2. Assess damage and make recommendations for recovery to Database services.3. Identify other individuals required to assist in recovery of these applications, and report this information

to the ID for action.4. Restore degraded system function at backup site and inform user community of the restrictions on

usage and/or availability.5. Coordinate software replacement with vendor as required. (See Appendix F for vendor and contact

information)6. Coordinate Database services recovery with other recovery efforts.7. Execute plan to restore Database services to full function.8. Provide scheduled recovery status updates to the Incident Director to ensure full understanding of the

situation and the recovery effort.9. Verify and certify restoration of the Database services to pre-disaster functionality.

7.3.3 Data Center Recovery Team:

1. Take appropriate steps to safeguard personnel and minimize damage to any related equipment and/or software.

2. Assess damage and make recommendations for recovery of Central Data Facility. Determine if use of alternate/cold site is required.

3. If the alternate data center site is required, execute all necessary steps to notify appropriate personnel and secure backup facility.

4. Identify other individuals required to assist in recovery of data center, and report this information to the ID for action.

5. Develop overall recovery plan and schedule, focusing on highest priority servers for specific applications first. (Appendix E documents the priority areas of the campus for IT service recovery)

6. Coordinate hardware and software replacements with vendors. (See Appendix F for vendor and contact information)

7. Recall backup/recovery tapes from on campus or off-campus storage, as required to return damaged systems to full performance.

24

8. Oversee recovery of data center based on established priorities.9. Coordinate data center recovery with other recovery efforts on campus.10. Provide scheduled recovery status updates to the Incident Director to ensure full understanding of the

situation and the recovery effort.11. Verify and certify restoration of the data center to pre-disaster functionality.

7.3.4 Desktop Recovery Team:

1. Take appropriate steps to safeguard personnel and minimize damage to any related equipment and/or software.

2. Assess damage at all areas affected, and make recommendations for recovery.3. Identify other individuals required to assist in recovery of desktop services, and report this information

to the ID for action. 4. Develop overall recovery plan and schedule, focusing on highest priority areas of the campus

infrastructure/desktop services first. (Appendix E documents the priority areas of the campus for IT service recovery)

5. Coordinate hardware and software replacement with vendors. (See Appendix F for vendor and contact information)

6. Oversee recovery of desktop computing services (workstations, printers, etc.) based on established priorities.

7. Coordinate recovery with other recovery efforts on campus.8. Provide scheduled recovery status updates to the Incident Director to ensure full understanding of the

situation and the recovery effort.9. Verify and certify restoration of the desktops to pre-disaster functionality.

7.3.5 Messaging Recovery/Network and Telecommunications Recovery Team:

1. Take appropriate steps to safeguard personnel and minimize damage to any related equipment and/or software.

2. Assess damage and make recommendations for recovery.3. Identify other individuals required to assist in recovery of services, and report this information to the ID

for action. 4. Develop overall recovery plan and schedule, focusing on highest priority areas of the campus

infrastructure first. (Appendix E documents the priority areas of the campus for IT service recovery) 5. Coordinate hardware and software replacement with vendors. (See Appendix F for vendor and

contact information) 6. Oversee recovery of messaging, telecommunications and network services based on established

priorities.7. Coordinate messaging, network and telecommunications recovery with other recovery efforts on

campus.8. Provide scheduled recovery status updates to the Incident Director to ensure full understanding of the

situation and the recovery effort.9. Verify and certify restoration of the Messaging, Network and Telecommunications infrastructure to pre-

disaster functionality.

7.3.6 PeopleSoft Recovery Team:

1. Take appropriate steps to safeguard personnel and minimize damage to any related equipment and/or software.

2. Assess damage and make recommendations for recovery to PeopleSoft services.3. Identify other individuals required to assist in recovery of these applications, and report this information

to the ID for action.4. Restore degraded system function at backup site and inform user community of the restrictions on

usage and/or availability.

25

5. Coordinate software replacement with vendor as required. (See Appendix F for vendor and contact information)

6. Coordinate PeopleSoft services recovery with other recovery efforts.7. Execute plan to restore PeopleSoft services to full function.8. Provide scheduled recovery status updates to the Incident Director to ensure full understanding of the

situation and the recovery effort.9. Verify and certify restoration of the PeopleSoft services to pre-disaster functionality.

7.3.7 Resnet Services Recovery Team:

1. Take appropriate steps to safeguard personnel and minimize damage to any related equipment and/or software.

2. Assess damage and make recommendations for recovery.3. Identify other individuals required to assist in recovery of services, and report this information to the ID

for action. 4. Develop overall recovery plan and schedule, focusing on highest priority areas of the campus

infrastructure first. (Appendix E documents the priority areas of the campus for IT service recovery) 5. Coordinate hardware and software replacement with vendors. (See Appendix F for vendor and

contact information) 6. Oversee recovery of resnet services based on established priorities.7. Coordinate resnet recovery with other recovery efforts on campus.8. Provide scheduled recovery status updates to the Incident Director to ensure full understanding of the

situation and the recovery effort.9. Verify and certify restoration of the Messaging, Network and Telecommunications infrastructure to pre-

disaster functionality.

7.3.8 Telecommunications Recovery Team:

1. Take appropriate steps to safeguard personnel and minimize damage to any related equipment and/or software.

2. Assess damage and make recommendations for recovery.3. Identify other individuals required to assist in recovery of these services, and report this information to

the ID for action.4. Develop overall recovery plan and schedule, focusing on highest priority areas of the campus

infrastructure first. (Appendix E documents the priority areas of the campus for service recovery.)5. Coordinate hardware/software replacement with vendor as required. (See Appendix F for vendor and

contact information)6. Oversee recovery of voice network services based on established priorities.7. Coordinate the voice network recovery with other recovery efforts.8. Provide scheduled recovery status updates to the Incident Director to ensure full understanding of the

situation and the recovery effort.9. Verify and certify restoration of the voice network to pre-disaster functionality.

7.4 General System/Application Recovery Procedures/Outline: The following steps are guidelines to be followed for the overall restoration of systems located at Central Washington University. While each Recovery Team has specific duties and responsibilities as outlined in Section 7.3, coordination between the various teams is required to restore operations to the users. While the coordination and extent of personnel involved will depend on the type and severity of the disaster, the following steps may be required:

NOTE: It is implied in the procedure/outline below that steps are simply provided as a guideline. The magnitude and type of disaster, and the number of systems affected will require that certain steps be augmented (at the discretion of the Disaster Team Lead and Incident Command Team), and that other steps will not be applicable to the situation at hand.

26

1. Determine extent of damage and make determination as to the following:a. Primary Data Center operational/recoverable?

i. YES: Remain in primary data center and initiate DRP accordingly.ii. NO: Contact personnel responsible for Backup Data Center and take necessary

steps to ready the facility.b. Network Operations Center operational/recoverable?

i. YES: Utilize existing NOC for recovery.ii. NO: Contact personnel responsible for Backup NOC and take necessary steps to

redirect network routes and ready the backup facility.c. Determine extent of applications affected

i. Peoplesoft System ii. Messaging (Email, Scheduling)iii. Web Services (cwu.edu)

d. Determine extent of desktop/client systems affected throughout the campus2. Secure facility as necessary to prevent personnel injury and further damage to IT systems.

a. Shutdown any active components.b. Physically secure facilities (Data Center, Communication Rooms, etc.) as necessary to

prevent unauthorized access.3. Retrieve most recent on-site or off-site back-up media for previous three back-ups. Prepare back-

up media for transfer to primary or secondary data center, as determined during the initial assessment.

4. Verify operational ability of all equipment on-site in the affected area (servers, network equipment, ancillary equipment, etc.). If equipment is not operational initiate actions to repair or replace as needed.

5. Test systems, and communication equipment as required to validate physical operation and performance.

a. Server testingb. Network testingc. Desktop/Client testing

6. Upon restoration of the Data Center and servers to operational state:a. Load Operating System and test/validateb. Load Application Software and test/validatec. Load Data and verify integrity

7. Verify overall performance of specific system(s) and report readiness to Incident Command Team, Management Team, and user community.

27

8.0 Network & Telecommunication Recovery Guidelines:

Servers and central application software are located in a central facility which can easily be assessed and secured for damage. Data networking and telecommunications, however, has equipment located in every facility on Central Washington University as well as in the Data Center. Remote equipment is located in Communication Closets, often in multiple sites in a single building. In addition, data and telecommunication cabling runs throughout the campus and buildings, making it susceptible to varying levels of damage.

Depending on the type and scope of the disaster, the IT Network and Telecommunication Recovery Team will be involved in the following activities to adequately assess the overall damage and impact to the campus, and to assure a comprehensive plan for recovery:

1) Earthquakea) Perform comprehensive cable, fiber, and communications line testingb) Assess all communication closets and racks/equipment for damage

2) Firea) Evaluate all cable and fiber in the vicinity of the fire for potential destruction or deterioration b) Test primary copper data feeds for destruction of deteriorationc) Evaluate and test/assess all electronic equipment (hubs, switches, routers, etc.) that have been

exposed to water or other agents.d) Assess all equipment with air filtration systems to assure adequate ventilation remains.

3) Water/Flooda) Evaluate all cable and fiber in the vicinity of the water/flood for potential destruction or

deterioration b) Test primary copper data feeds for destruction of deteriorationc) Evaluate and test/assess all electronic equipment (hubs, switches, routers, etc.) that have been

exposed to water or other agents.d) Assess all equipment with air filtration systems to assure adequate ventilation remains.

Central Washington University network diagrams are included in Appendix G.

28

APPENDIX A: Central Washington University: Information Technology Services Directory/Contact List.

Last Name First Name

CWU Phone CWU Email CWU Cell Home

Phone Home Email Home Cell

Ahmad Max 2939 max.ahmad@cwu.edu        

Allen Don 2393 don.allen@cwu.edu   925-9092 dadeodon@gmail.com 607-1495

Alviso Jose 1743 alvisoj@cwu.edu        

Andrin Marion 1891 andrinm@cwu.edu   962-3188 marionpich@yahoo.com  

Ashbrooks Steve 3442 ashbroos@cwu.edu 899-1865 965-4219   961-8878

Beintema Larry 2905 beintema@cwu.edu 899-0347 968-9320    

Beintema Jami 2333 beintemj@cwu.edu        

Breckon Ron 3694 breckonr@cwu.edu   933-1010 breckons@elltel.net 859-2301

Brower Doug 2356 brower@cwu.edu        

Brown Rock 2999 brownroc@cwu.edu        

Carlson Barry 2904 bcarlson@cwu.edu        

Case Felicia 2903 felicia@cwu.edu        

Cathcart Jason 1223 cathcarj@cwu.edu     johann@bach.net 312-9732

Cusumano Pete 3834 cusumanp@cwu.edu        

DeLuca Greg 2970 gdeluca@cwu.edu 201-6144 933-4606   859-2884

Douglas Steve 1232 dougr@cwu.edu 856-6581      

Firman Marla 1250 firmanm@cwu.edu        

Gerdes Jason 2995 jgerdes@cwu.edu   932-5361   431-5030

Germain Dave 2996 germaind@cwu.edu   962-5241 citizengermain@gmail.com  899-0055

Germain Terilee 2946 terilee@cwu.edu   962-5241 terilee@fairpoint.net 899-1696

Gladen Jeff 1606 gladenj@cwu.edu   925-2473 jgladen@elltel.net  

Gladen Kristi 2392 gladenk@cwu.edu 899-0044 925-2473 kgladen@elltel.net  

Glessner Bill 3694 beegee@cwu.edu 899-0999 962-6566    

Haberman Susan 2944 haberman@cwu.edu   925-1713 bobhaberman@elltel.net 899-5015

Halvorson Colleen 3499 halvorsc@cwu.edu        

Hart David 2932 hartd@cwu.edu 306-2128 925-6961 galtj@elltel.net  

Hendrickson Teri 3422 hendricksont@cwu.edu        

Hernandez Uriel 2967 hernandu@cwu.edu        

Hill Nathan 2942 hillna@cwu.edu   962-5339   899-5063

Jackson Nancy 3333 jacksonn@cwu.edu 899-0136 925-3835 njj706@gmail.com 899-4617

Jones Frank 2856 jonesfr@cwu.edu        

Jones Keith 2191 jonesk@cwu.edu 856-6219 962-5707 jonesk@elltel.net 856-5333

Klampher Tina 2778 klamphtl@cwu.edu 899-3836 925-2013   899-4818

Knackstedt Jeff 2352 knackstj@cwu.edu 899-2768 962-8165   306-9637

Lei Vera 2972 leiv@cwu.edu        

Lonowski Dale 2407 lonowsda@cwu.edu   933-4002 dalerainy@yahoo.com 859-2903

Miller Bill 3490 millerwd@cwu.edu   n/a   899-0243

Osguthorpe Jared 2954 osguthorpej@cwu.edu        

Patterson Randy 3653/3649 pattersr@cwu.edu 856-7116 925-4391   899-2527

Pierce Tad 2997 piercel@cwu.edu   674-9632    

29

Pratz Chris 1581 cpratz@cwu.edu 899-3220 n/a    

Pruitt Jim 3472 pruittj@cwu.edu 899-0145 962-8342    

Rahm Carmen 2925 rahmc@cwu.edu 899-0038 962-1547 foreacres@elltel.net 360-271-2992

Richardson Wade 3424 richardw@cwu.edu 856-6867 697-3370   930-7823

Ringer Jason 2394 ringerj@cwu.edu   698-5033   949-5056

Rodriguez Noah 2934 rodriguezn@cwu.edu        

Shelton Debby 3428 sheltond@cwu.edu   925-4115 shelton56@hotmail.com 899-1479

Sperline Sandy 2989 sperlins@cwu.edu   968-9825 ssperline@hotmail.com 929-0552

Swayze Stacy 3466 swayzes@cwu.edu        Timmons Chris 2947 cwt@networks.cwu.edu 899-2101 925-7897 cwt@elltel.net 856-7884

Varga Steve 2953 shv@cwu.edu   963-9073 vargahenry@netscape.net  Vincent Kathy 2544 vincentk@cwu.edu        

Wang Xinbao 2945 wangx@cwu.edu        

Wang Crystal 2643 wangc@cwu.edu   925-4374    

Webber Maury 3752 webberm@cwu.edu        

Wixson Heidi 2969 wixsonh@cwu.edu   962-6107   607-0347

Young Ken 3491 youngke@cwu.edu   933-1773 kgyoung@charter.net 899-1035

30

APPENDIX B: Central Washington University Critical Support Contacts List.

Last NameFirst Name

CWU Phone CWU Email CWU Cell

Home Phone Home Email Home Cell

Gaudino James 2150 gaudino@cwu.edu330-554-6528

Clark George 2323 clarkg@cwu.eduLevine Marilyn 1400 levinem@cwu.eduHorsley Jackson 1874 horsleyj@cwu.edu 925-1877Swiney John 3031 swineyj@cwu.edu DeShields Richard 2785 deshielr@cwu.edu  201-0459      Schactler Linda 1384 schactler@cwu.edu      

     McGuire Tim 2329 mcguiret@cwu.edu 962-9022 tim@gowestmail.com  312-0405

Gaer Kathy 2201 gaerk@cwu.edu 859-4919 962-9876  

Morrill Tami 3016 morrillt@cwu.edu   962-6667    

 Tosch Robert 2916 toschr@cwu.edu 899-0635 962-4581  

The Central Washington University Personnel Directory (2006-2007) and contact information is included with the hardcopy version of this plan. Copies of the plan are located in the ITS Office (Bouillon 202), the Computer Center and the Vault (Hebeler).

Name Contact Phone Fax Email

Charter Communications Ron Graaff509 962-4801 509 728-2662   Rgraaff@chartercom.com

City of Ellensburg (Inet) Bob Johnson 509 925-8537   johnson@kittcom.orgFairpoint Communications Patrick Murphy

509 962-0331 509 929-3881   pmurphy@fairpoint.com

K20 Administrative Contact Steve Paulson 206 221-3221   spaulson@cac.washington.edu

K20 Internet Circuit

Washington K20 Network Operations Center 888 934-5551 888 934-5557 noc@wa-k20.net

K20 Point-to-Point Circuits (Data/Video to Campus Centers)

Washinton State DIS Helpdesk (DIS DL Helpdesk) 888 241-7597   Helpdesk.DIS.WA.GOV

31

APPENDIX C: Central Washington University – Asset Management Information

The following printouts, asset management information, and documents are included with the hardcopy version of this plan. Detailed information is documented in the online database located at http://www.cwu.edu/~its/security/hardware.php.

Server Asset Management Information Network Active Hardware Asset Management Information Application Software Configuration Information Desktop Equipment Asset Management Information

32

APPENDIX D: Central Washington University – System Backup/Tape Retention Periods

All servers in the Computer Center are backed up on this schedule: http://beintema.cts.cwu.edu/~beintema/networker_schedule.htmlRetention information is located in section 6.1 of this document.

Schedule of Legato networker host saves

S - skip I - incremental F - full Full saves start at 12:10 a.m., usually done by 8am Incrementals start at 2:00 a.m., usually done by 5am===================================================Hostname Sun Mon Tue Wed Thu Fri Sat aeolus.lab.cwu.edu F I I I I I I alecto I I I I I I F alipes2.cts.cwu.edu S F I I I S I ananke F I I I I I S anat.cts.cwu.edu S F I I I I I aphrodite S I I I I I F apollo.saffrs.cwu.edu I S F I I I I apps-01.aux.cwu.edu F I I I I I S arges.cts.cwu.edu I I I I S F I aries.cts.cwu.edu S S S S S S S aris S S S I S S F aristotle.lab.cwu.edu I I I I I F S asherah.cts.cwu.edu S I I I I I F athena.cwu.edu S I I F I I I atlas.cts.cwu.edu I S F I I I I azure.cts.cwu.edu S I I I F I I barchetta.lib.cwu.edu S S S S S S S bbdata.cts.cwu.edu I I I I I F S bbweb.cts.cwu.edu I S I I I F S beintema.cts.cwu.edu S I I I I F I blackbaud.unadv.cwu.edu I I I I I F S bonsai.cts.cwu.edu F I I I I I S boreas F I I I S S I bruker05.chemistry.cwu.edu S I I I I F I capricorn.cts.cwu.edu S S S S S S S ccs.aux.cwu.edu F I I I I I S ccstst.aux.cwu.edu F I I I I I S cerise.aux.cwu.edu S I I I I I F chinstrap.lib.cwu.edu S S S S S S S clmdb.cts.cwu.edu S F I I I I I clmtest.cts.cwu.edu S F I I I I I clmweb.cts.cwu.edu S F I I I I I clotho I I I I I F I columba.cts.cwu.edu S S S S S S S courses2.cwu.edu S S S S S S F crimson.cts.cwu.edu S S F I I S I cyan.cts.cwu.edu I S I F I I I cygnus.cwu.edu I S F I I I I daffy.cts.cwu.edu S I I I I I F dbackup0.cts.cwu.edu S I S F S I S dbackup1.cts.cwu.edu S S F S I S I dbtest.cts.cwu.edu S S S S S S S demeter I S F I I I I diana F I I I I I S diebolddb.aux.cwu.edu I S F I I I I

33

donald.cts.cwu.edu S I I I I I F dynobites.aux.cwu.edu S I F S I I I eldorado.chemistry.cwu.edu S S S S S S S etclib.ed.cwu.edu I F S I S I S eunomia.cts.cwu.edu I I I I I I F ezp.lib.cwu.edu S F I I I I I fileproxy.cwu.edu F S I S I S I flex.aux.cwu.edu F I I I I I S fmail.cts.cwu.edu S I I I I I F fuschia.cts.cwu.edu S I F I I I I galileo.phyplt.cwu.edu F I I I I I S gizmonic.cts.cwu.edu S F I I I I S gridiron.cts.cwu.edu F I I I I I S gridlock.cts.cwu.edu I S F I I I I gw-gate2.cwu.edu S I I I I I F gw-stu1.cwu.edu S I I I I I F gw-stu2.cwu.edu S I I I F I I gw-stu3.cwu.edu F I I I I I S gw-stu4.cwu.edu I I I F I I S gw-stu5.cwu.edu I S F I I I I gw-stu6.cwu.edu S I I I F I I hcc.aux.cwu.edu F I I I I I S hccaud.aux.cwu.edu F I I I I I S hermes I S S F S I S horizon.cts.cwu.edu F I I I I I S housing.aux.cwu.edu S S S S S S S hubris.cts.cwu.edu S I I I I F S hypnos S F I I I I I indigo.cts.cwu.edu I S I I F I I keybox.cts.cwu.edu S F I I I I I kronos.aux.cwu.edu S F I I I I I kryten.cts.cwu.edu S I I I I I F labstats.cts.cwu.edu F I I I I I S lavender.cts.cwu.edu S I F I I I I library I F I I I I S lister.cts.cwu.edu S I I I I I F localhost6.localdomain6 S S S S S S S logopolis.hpc.cwu.edu S I I I I I F magenta.cts.cwu.edu I I I F S I I maroon.aux.cwu.edu I I I S I S F mauve.cts.cwu.edu F I I I I I S megaera.cts.cwu.edu S I F I I I I mercury2.cts.cwu.edu I I I S I S F microsapp.aux.cwu.edu S I F I I I I microsdb.aux.cwu.edu S I F I I I I midas.adm.cwu.edu S F I I I I I min.cts.cwu.edu F I I I I S I mingo.lib.cwu.edu S S S S S S S mira.cts.cwu.edu I I I S F I I mot.resnet.cwu.edu F I I I I I S mtrainier.cts.cwu.edu S F I I I I S mysql.cts.cwu.edu S I I I I I F n.cwu.edu S F I I I I I nergal.cts.cwu.edu S I S I I I F nsc0.cwu.edu I S F I I I I nsc0.resnet.cwu.edu F I I I I I S nsc1-831.cwu.edu I F I I I I S nsc1.resnet.cwu.edu S F I I I I I nyx F I I I I I S ochre.cts.cwu.edu S I I I I I F

34

otm.cts.cwu.edu S F I I I I I pa.cts.cwu.edu S F I I I I I panteknicon.cts.cwu.edu S I I I I I F pc78221.d.cwu.edu S S S S S S S plato.lab.cwu.edu S I I I I I F pollux.cts.cwu.edu S S S S S S S poseidon I S F I I I I prometheus.cts.cwu.edu F I I I I I S qadesh.cts.cwu.edu F I I I I S I r25.cts.cwu.edu S F I I I I I resheph.cts.cwu.edu F I I I I S I resnet.cwu.edu F I I I I I S rima.cts.cwu.edu F S S I S S S rimmer.cts.cwu.edu S I I I I I F ronald.cts.cwu.edu S I I I I I F scarlet.cts.cwu.edu I S I I F I I screencast.clt.cwu.edu S S I F I S I sheena.cts.cwu.edu F I I I I I I smail.cts.cwu.edu S I I I I I F socrates S I I I I F I spectrum.ed.cwu.edu S S F I I I I streamer0.cts.cwu.edu S S I S S F S studentmedia.cwu.edu S I I I I I F telemgr.cts.cwu.edu S I I I I I F telos.cts.cwu.edu S S F S S I S telsrv.cts.cwu.edu S I I I I I F tethys I S F I I I I themis.cwu.edu I S F I I I I tiamat.cts.cwu.edu F I I I I S I tisiphone S I I I I I F trix.aux.cwu.edu I S F I I I I uhnsp.aux.cwu.edu S F I I I I I uhnsptst.aux.cwu.edu F I I I I I S umber.cts.cwu.edu S I I I I I F vmail.cts.cwu.edu S I I I I I F w3cache0.cts.cwu.edu F I I I I I S wmail.cts.cwu.edu S I I I I I F worf.cts.cwu.edu S I I F I I I zephyrus S I I F I I I zeus.cwu.edu I I S I F I I

Servers:

Server information is documented in the online database located at http://www.cwu.edu/~its/security/hardware.php.

Hardware Database:

The hardware database is updated/reviewed every month by the Networks & Operations staff. The database is copied to CD monthly and stored in the vault located Hebeler.

When major configuration changes take place, new CDs will be created upon its completion.

35

APPENDIX E: Central Washington University: IT Recovery Priority List

The following priorities have been established by the Director of Information Technology Services and by CWU Senior Management for the recovery of IT Services to the university.

IT Infrastructure Priorities: This establishes the internal priorities for recovering the major infrastructure components for IT services. These priorities are based on the relationship between these systems, and the pre-requisite nature of many of the items in order to be able to return full services to the campus.

1. Data Center2. Network Services (as prioritized below)3. Messaging Services (email/calendaring)4. Web Services5. Peoplesoft Applications6. Online Course Delivery and Classroom Technology

36

Central Washington University Functional Priorities for IT Recovery: This establishes the priorities for recovering IT services for specific customers and facilities across the campus. While the Data Center, Peoplesoft, Web, and Messaging Services are centrally located, and will normally be recovered for all users simultaneously, recovery of network and desktop services will be accomplished based on the following priorities, in order to return critical campus systems and facilities to operational status at the earliest possible time.

Priority Administrative System Primary Staff L Alumni Jim Armstrong M Blackboard Delayna Breckon L/M Conference Center (CCS) M Course Management R25 Xinbao Wang L Daycare Management Janie Charlton C Diebold/CBORD Tad Pierce H Dining Services (DINE,Computrition) Dan Layman H/C Electronic Mail Bill Glessner, Greg DeLuca M Facilities Planning (Facility MAX) Jason Cathcart,

 M File ServicesGreg DeLuca, Terilee Germain

 H Finance (FMD) Shirley Pruitt

 H Financial Aid (HRSA)Jillian Hernandez, Tami Morrill

 L Health Services Jackson Horsley H Housing Richard DeShields L Institutional Research Mark LundgrenL/M Instructional Computing (MTIS) Jane Chinn L/M Library Ping Fu L Parking (CPAS) Trish Swanson H Payroll (Safari) Darcy HansenH/C ResNet Jason Gerdes H Safari / HR L Student Recreation (Class) Bob Ford C Telecommunications Nancy Jackson L/M University Store (Sequoia,IBIDie) Steve Wenger C Web Services Linda Schactler

Classifying computer application systems:

Critical – Must be processed in normal mode; no degradation is acceptable.High – Only high priority; e.g., high dollar item transactions or critical reports will be processed.Medium – Processing will be carried out on a “time available” only basis.Low – Processing will be suspended, but data collection will continue.Full – No processing or data collection will be carried out until normal computer capacity is restablished.

37

38

Facility Priorities:

Priority Building Name Priority Building Name M 1800 Building  L Lyon (Yakima) L Archives  L Mail and Duplicating H Barge  C Manastash H Barto  L/M McConnell H Beck (Resnet Sector Building)  H Meisner M Black  M Michaelsen C Boiler Plant  H/C Mitchell (Sector Building) C/H Bouillon (Sector Building)  M Moses Lake H Brooklane  H Munson H Button  M Music H Carmody-Munro  L Naneum M CHCI  M Nicholson C Computer Center  H Old Boiler Plant M Dean  M Olympic (Pierce) M Deccio (Yakima)  M Dorothy Purser (PE) M Des Moines  M Peterson (ROTC) M Farrell  H Wendell Hill (SVS) M Flight  L Pool H Green (Resnet Sector Building)  M Power Tech L Grounds  M PresRes C Health Center  M Psychology M Hebeler  M Randall L Hertz  H Residential Housing

 MHigher Education Center(Highline)  C/H Science (Sector building)

 M Hogue  M Shaw-Smyser L/M International  C Student Union & Recreation Center H Jansen  L SUB (OLD) C Jongeward  M Sue Lombard H Kamola  L Surplus H Kennedy  H Tunstall M L and L  L Warming Hut C/H Library (Sector Building)  M Wenatchee M Lind  H Wilson M Lynnwood

Classifying buildings:

Critical, needed for maintenance of public health and safety, communications.High, needed for income maintenance for students, employees; payments to vendors; requirements for compliance or regulation; effect on state government cash flow; effect on production and delivery of services (housing, dining, student services).Medium, needed for mission of university, delivery of classes.Low, everything else.

APPENDIX F: Central Washington University: Vendor InformationVENDORS Mgr Contact Info. Term Description Cont

City of Ellensburg #621420 N. Pearl St.Ellensburg, WA 98926

Noah phone 9627203

2666.34

quarterly

I-Net O&M Expenses (Quarterly) 5240

Comstor #6912219 N. Dickey RoadSpokane, WA 99212

Gene

phone 800-776-2451, fax 916-924-1398 cell 916-785-6048 Marty Skognes marty@comstorinc.com

7/1/09 –

6/30/10

Provide Computer output to microfilm services & courier(Microfiche Agreement)

1584

Connx Solutions Inc #39331800 112th Ave NE Suite 150Bellevue, WA 98004

Gene Jennifer Van Dijik 425-512-6622

7/17/2009-

7/16/2010

Annual Support Maintenance*Gene does not want to Encumber

6164

Cascade Copiers #1629801 W. Yakima Ave.Yakima, WA 98902

Marlaphone 509-575-0734fax 509-575-3080curtis.bell.jr@imagistics.com

1/05 - 12/09

Imagistics im3510 digital copier/printer system (Networked)

 

Dimension Systems (Cisco) #1417317311 135th Ave NE Suite B500Woodinville, WA 98072

Noahphone 425-502-0258fax 425-402-0633Lana Greene

9/4/04 - 9/3/05

SMARTNET 8x5 NBD Support Renewal 3467

Dimension Sys (Sun Microsystems) #1417317311 135th Ave NE Suite B500Woodinville, WA 98072

Noah Ramona Estay 425-402-0258

5/1/04 -4/30/05

Sun Spectrum Silver Renewal (Software support)

3530

41

Graymatter Software #1198100 South King Street Suite 570Seattle, WA 98104-2885

Noah

Doug Parsons #303051800-477-0348 X120, 206-329-8800fax 206-860-9441

7/1/04 - 6/30/05

Script Server Annual Maintenance for the Large Mixed VAX & Alpha Cluster License with Network Module Enabled

3067

HP (Digital EquipmentCorp. or Compaq) #6831124 Tower RoadSchaumburg, IL 60173

Noah/ P&M

phone 916-785-6485916-785-6048fax 916-924-1398jerry.piepmeier@hp.com

7/1/04 - 6/30/05

VAX Software Maint. Renewal 1276

JRB Software Noah/ David H 643-332-5996  

renewal for JRButils software registration

None

Mail Abuse Prevention System (MAPS) #11873950 Charter StreetRedwood City, CA 94063

Noah Heather Bryning phone 650-779-7084

3/1/05 -2/28/06

Renewal of Subscription to RBL + Master Service and Peb-Plus.Mailabuse.org zone

6301

Mini Tab #19531829 Pine Hall RoadState College, PA 16801-3008

Sandy Sperline

Lu Ann Mann phone 814-238-3280fax 814-238-4291

7/1/09 - 6/30/10

Renew Licence Agreement 1438

Netvision #124911500 N Technology WayBuilding D, Suite 3300Orem, UT 84097

NoahHeather Andersonphone 801-764-0400 x145fax 801-764-0600

5/1/04 - 4/30/05

Renew Licence Agreement/Annual Maintenance Renewal for Directory Alert Software

5222

Novell Inc. #21561800 South Novell PlaceProvo, UT 84606

Noah/ Tech Fee

phone 800-453-1267 x15235fax 801-861-5235

10/1/04 -

9/30/05

Academic Licensing renewal. Netware NFS Services 3.0 Maintenance

4811

Oracle #21981910 Oracle WayReston, VA 20190

Noah/ ASSP

Gavin Ostrom916-315-6582fax 781-238-9895

5/23/04 -

5/22/05

Product Support Fee Limited Site Licenses (10 Systems)

4435

Process Software (PMDF, Multinet) #2392959 Concord StFramingham, MA 01701

Noah

Michelle Haley800-722-7770, 508-879-6994fax 508-879-0042haley@process.com

7/1/04 - 6/30/05

Multinet Univ. Alliance Annual Maint. 25 CPU'sPMDF Access & LAN Tru 64/UNIX Maint.

3312

42

Process Software (Precise Mail) #2392959 Concord StFramingham, MA 01701

Noah

Michele Haley800-722-7770, 508-879-6994fax 508-879-0042haley@process.com

10/20/04-

10/19/05

Anti-Span Gateway annual softwware subscription

3312

Process Software (SOPHOS) #130726 Limball LaneLynnfield, MA 01940

Noahphone 888-767-4679fax 781-245-8620Craig McKeown

7/1/04 - 6/30/06

Sophos Antivirus 2000 User SAVI License. For Use with PMDF

 

Quest #2428PO BOX 51739Los Angeles, CA 90051

Genephone 614-726-4823fax 614-726-3884Joann Sizemore

3/31/09-

3/31/10

Toad Formerly (Lecco SQLab Expert Pro Edition for Oracle) per seat (12)

6663

R&D Performance Group (Support) #133981180 Patricia St Ste 102Simi Valley, CA 93065

Noah Katie Nielsen 800-521-9966fax 805-520-4169

9/10/04 - 9/9/05

Networker Open VMS Client Support Renewal None

Right Systems Inc. (Packeteer) #10698PO BOX 11036Olympia, WA 98508-1036

Noah/ Chris T.

Mark Westling3609560414x8200

7/1/04 - 6/30/05

Renewal of Packeteer Cust. Support Program None

HP #2825715 N Glenville Dr #450Richardson, TX 75081

Noah

phone 214-210-6222214-210-6246fax 214-210-6211David Evett/Don Genton

1/29/05 -

1/31/06

Legato Updates for NetWorker Server 6082

SPSS-PC #2770233 S Wacker 11th FloorChicago, IL 60606-6307

Dave S.Tech Fee

Steve Prior 800-543-2185 x3943fax 312-264-3943

 SPSS Base, Advanced Models, Trends, Answer Tree

3576

University of WA #3123PO BOX 355870Seattle, WA 98195

Noah phone 814-238-3280fax 814-238-4383

7/1/04 - 6/30/05

PNW IGAPOP K20 Utilization None

Verisign, INC.75 Remittance Dr. Suite 1689Chicago, IL 60675-1689

Noah Brenda Mofford 877-438-8776

Multiple Times Yearly

Multiple Contracts for Secure Site Service (SSL Certificate)

None

Visual Numerics #3193PO BOX 297852Houston, TX 77297-0852

NoahPamela Seymour phone 816-753-0848fax 816-753-5454

1/4/05 - 1/3/06

Annual Unlimited Usage Campus Site License for IMSL Fortran 90 & C

1616

HP #89633145 Porter Dr Bldg FPalo Alto, CA 94304

Noah/Larry

phone 650-475-5019fax 650-475-5001

8/31/04 -

9/1/05

GSX3-L-U-AE License for Linux 2 cpu

None

XIOTech #103436455 Flying Cloud DrEden Prarie, MN 55344

Noah   3/1/05 -2/28/06 Magnitude base 110V 6258

43

T2 Systems7835 Woodland Drive Suite 250Indianapolis, IN 46278

Steve B/Nate Hill

Deborah Eugene Sales 317-524-7445

support 800-434-1501support@t2systems.com

  Parking: T2 Systems Flex System  

Adirondack Solutions, Inc.P.O.Box 8102Bridgewater,NJ 08807www.adirondacksolutions.com

Marion Andrion

phone: 908-725-8869fax: 908-725-9396Tech Contact: 908-725-8869Charlie Boone ext 205Josh Prokrasov ext 206support@adirondacksolutions.com

  Housing  

Kronos Incorporated18200 NE Union Hill Rd Ste 100Redmond, WA 98052

Nate Hill

Tech Contact: Kronos Global Support 800-394-4357Solution nbr: 6051679 support@kronos.com

 Dining [Kronos Employee Timekeeping& Payroll System]

5287

Computrition Inc19808 Nordhoff PlaceChatsworth, CA 91311

Larry Beintem

a/Judy

McNeil/Tad

Pierce

Tech Contact: Beth 800-222-4458 cust # 1593

 

Dining [Computrition Food Management System] Windows fat client w/ Oracle

 

The CBORD Group61 Brown RoadIthaca, NY 14850www.cbord.com

Tad Pierce

Support 866-789-2977 cs_support@cbord.com

Sales: Don Raeoffice:509-628-2315cell 509-539-0159efax 413.653.3860

 

CBORD Campus Card System and Micros Cash Register System[formerly Diebold]

4726

Inland Business Products111 N. Vista, Bldg 4DSpokane, WA 99212www.ibpspokane.com

Tad Pierce

phone 800-825-5703Tech Contact: Tod Curtistcurtis@ibpspokane.com  

Connection Card: IDworks Card Production Sys

6299

Asset Solutions Division33330 Oakwell CourtSuite 200San Antonio, TX 78218

Ed Castane

da

Tech Support 800-268-0325facilitysupport@assetworks.com www.assetworks.com/facilitysupport

 

FMD & Auxiliary: FMAX Work Order Management http://www.assetworks.com/page/facilities-management-support

44

Nuesoft Technologies1685 Terrell Mill RoadMarietta, GA 30067www.nuesoft.com

Steve B/Nate Hill

phone: 800-401-7422 ext 210 Tech Support: 800-401-0785 NueMDsupport@nuesoft.com

 Expires

7/13/09 and will not be

renewwed

Health Center: Nuesoft Medicat Xpress 7137

Active Networks6400 Roberts Road Suite 30Burnaby, BCCanada V5G 4C9

Nate HillTech Support: 800-663-4991 classsupport@active.com

  Student Recreation: Class Software 7659

Resnet Server Applications Nate Hill 509-963-2942

HillNa@cwu.edu  

Locally written Resnet ApplicationsCall TrackerCopyCat Inventory

 

Sequoia Retail Systems1927 Landings DriveMountain View, CA 94043www.sequoiars.com

Tad Pierce/Nate Hill

phone 650-237-9000fax 650-237-0428Tech Support: POS 800-536-5644 ePos 800-818-5018 support@sequoiars.com

  Wildcat Shop: Sequoia Retail Systems 6418

Information Resource Technology, Inc9825 Perry HwyWexford, PA 15090www.ibid.com

Marion Andrin

509-963-1891 AndrinMa@cwu.edu  

Custom Developed Online Applications: Housing Re-Application, Residence hall Programs, Hall incident Reporting, Orientation Registration, Student Conduct Report, Parent Family Program

 

           Software Licenses          Campus Agreement   CSS 9/30/04 1122 FTE None

Office Professional   CSS 9/30/04$21.92 ea includes Word, Excel, Power Point, Access None

Windows Professional   CSS 9/30/04 $16.04 ea NoneFrontpage   CSS 9/30/04 $4.21 ea NoneSelect Agreement with Microsoft          

Ofice Family Subscription   CSSMonthly / July 04 $4.16 ea None

Macintosh Apps Subscription   CSS

Monthly / July 04 $2.49 ea None

Windows Servers Subscription   CSS

Monthly / July 04 $4.16 ea None

Server Apps Subscription   CSSMonthly / July 04 $4.98 ea None

Windows Client Business Subscription   CSS

Monthly / July 04 $2.49 ea None

45

Windows 2003 Server Std. Subscription   CSS

Monthly / July 04

(not sure on cost, this was added at last minute) None

Windows 2003 Server Ent. Subscription   CSS

Monthly / July 04

(not sure on cost, this was added at last minute) None

Vendor Mgr Contact InfoACCOUNT NUMBER

Service Address Contract

Service Type

Curcuit Numbers

Qwest

Telecom 800-777-9594509-453-8664 283B YVCC   Modem

509-453-8664

P.O.Box 12480Seattle, WA

     206-T31-5605 682B

Ellensburg - 911    

206-T31-5605

     206-T31-5687 673B

Ellensburg - 911    

206-T31-5687

     509-762-2135 974BG Moses Lake   Modem

509-762-2135

     206-824-8800 718B Des Moines    

206-824-8800

               Qwest

Telecom 888-429-0977QIA14001-WA1109

Lynnoood Maintenance 6441    

Department 047Denver, CO 80271

     QIA15266-WA0908

YVCC Maintenance 6704    

     QIA15387-WA0108

81C Maintenance 6538    

     QIA13998-WA1109 Voice Mail 5935    

     QIA14002-WA1109 DesMoines None yet    

     QIA14003-WA1109 Wenatchee None yet    

                              Global/Matrix

Telecom 888-411-01115203171199-0000 Admissions   800 Line

(866)298-4968

Greg Meyers

P.O. Box 742501

    800-236-2233 - Ext 2266  CWU Foundation   800 Line

(877)649-8707

    Greg Meyers   Development   800 Line(800)752-4378

        Library   800 Line(800)290-3327

        Aerospace   800 Line(800)298-7682

        Alumni   800 Line(877)846-2287

        Bookstore   800 Line(800)280-1186

       Conference Center   800 Line

(800)752-4379

       

Res Life & New Student Services   800 Line

(877)880-3583

        Wenatchee   800 Line(800)540-6537

46

       

University Emergency Information   800 Line

(866)419-8512 

        Army ROTC   800 Line(877)276-9298

       Anthropology   800 Line

(877)837-2915

       Career Technology   800 Line

(877)424-3989

       Conference Bridge   800 Line

(877)667-7535

                              Telewaves

Telecom 800-662-4077 10114223 Facilities   Pager509-925-0660

P.O.Box 2909Yakima, WA 98907

      10105460 Housing   Pagers

509-856-0357 & 509-856-0438

                                                            Verizon

Telecom 800-483-6000

03 0260 1000902293 04

Edmonds Campus  

Access Line

425-712-0183

POBox 1003MS: WA0102MJEverett, WA 98206    800-483-2000 Repair          

     

 03 0487 1084445493 03

Wenatchee Campus   

Access Line

509-667-0579

               AT&T Mobility

Telecom Bruce Erickson 990151123     Cellular  Redmond    206-245-7568 FAN 49040            800-999-5445-support              Chris McLeod              425-580-5565              Cell 425-495-9118                         Fairpoint

Telecom 509-925-1425

0100223045 - Main Account    

Main Trunking  

CommunicationsP.O.Box 308Ellensburg, WA 98926P.O.Box 70821Charlotte, NC

    509-933-7419

0100223070 - Housing Account        

    Bill Malesich

300-0042 - KCWU Circuit        

47

     

100-8911 - 911 Transport        

               DIS

Telecom 360-902-3528 3750A    Long Distance  

P.O.Box 42439Olympia, WA98504-2439

   (360) 902-3527 Mary Jackson          

                              AT&T

Telecom 800-847-3595056 578 3032 001 Yakima  

Access Line

509-453-8664

P.O.Box 78225Phoenix, AZ 85062-8225    800-822-3000 Repair                                        AT&T

Telecom 800-524-2333131 180-5838 799

Continuing Ed   800 Line

(800)720-4503

P.O.Box 78522Phoenix, AZ85062-8522

    800-222-3000 Service   Housing   800 Line(888)298-4663

    800-222-0400 Orders                                        Nextel

Telecom 888-404-8830 586518425     Cellular  

1620 North Mamer RoadSuite C-400Spokane, WA 99216

   509-879-0406 Jennifer Workman          

                              

Verizon Wireless Telecom 800-922-0204771411921-0001     Cellular  

P O Box 96082   Paul Cox          Bellevue, WA 98009   509-670-6006          

48

APPENDIX G: Central Washington University: Network Diagrams

Printouts of the Central Washington University network architecture diagrams are included with the hardcopy version of this plan.

49

APPENDIX H: Excerpt from the Emergency Preparedness Plan

SECTION 2Emergency Preparedness Organizational Chart

Board of Trustees*

President*

Emergency Coordinator(Executive Assistant to the President)

*Emergency Council

Council Members

Response Coordinator (Director of Public Safety and Police Services)Emergency operations center/communications systems (Radios)Field operations (Police Services)Coordination with responding agenciesSecurity/access for restricted and sensitive areasShort and advanced warning notice/call listSearch and rescue

Facilities Coordinator (Director of Facilities Management)Building/grounds assessment, inspection, and operationsUtility assessment, inspection, and operationsField operations (Facilities Management Services)Coordination to Telco, Data, and Video SystemsEmergency sanitation facilitiesArrange for temporary classroom facilitiesCoordination of utilities with outside agencies

Finance Coordinator (VP for Business and Financial Affairs)Registration of emergency workersCash and negotiables safeguardingRecord keepingEmergency purchases and leasingData safeguarding

Academic Coordinator (Provost)Coordinate on-going teaching/classroom operationsArrange for temporary classroom equipmentArrange for temporary faculty resources

Student Affairs (VP for Student Affairs and Enrollment Management)Student support and counselingEmergency ShelterEmergency feedingSign-up and organize emergency workers/message runnersMass casualty/medical services center/liaisonDisabled people

50

Community Relations (VP for University Relations)Media LiaisonPublic relationsEmergency message/contact centerOrganize video documentation of damage

Business Services (Director of Business Services and Contracts)Emergency proclamationsEmergency contractsRisk ManagementSupply and procurement

CWU IT System

Business Impact Matrix

Maintenance of Public

health and safety

Income maintenance for citizens

Income maint. for

gov. employees

Payments to

vendors for G&S

Requirements for

compliance or

regulation

Effect of state

government cash flow

Recovery Costs

Effect on product and delivery of services

Volume of

activity

Effect on

public image

Inter-system dependency

Alumni* L L L L L L L L L L LBlackboard L L L L L L L L L L LCampus Security (CAMPSA)* H L L L H L L H H H HCentral Stores L L M L L H L H H H MConference Center (CCS)* L L L L L L L H M M LCourse Management (R25) L L L L L L L L L L LDaycare Management* L L L L L L L L L L LDiebold/CBord* H L H L L L M H H H HDining Services (DINE,Computrition)* M L H L L H H H H H HElectronic Mail L L L L L L L L H L LFacilities Planning (WOS)* L L L L L L M H H H MFile Services L L L M M L M H H M HFinance (FMD) L L L M H L H H H H HFinancial Aid (HRSA) L L L L H L H H H H HHealth Services H L L L H L M H H H MHousing/Resnet H L L L L L H H H H MInstitutional Research* L L L L L L L L L L LInstructional Computing (MTIS) L L L L L L L L L L LLibrary* L L L L L L L L L L LParking (CPAS)* M L L L L L L L L L LSafari (Payroll/AP/AR) L L L L H L H H H H HTelecommunications H L L L L L H H H H HUniversity Store (POSS/Cen

L L M L L L L L L L L

51

store)*Web Services H L L L L M L H H H LWeb Services L L L L L L L L H H L                                                                 

Appendix J – Business Impact Matrix

52

Appendix K - Threat and Vulnerability Matrix - PhysicalTHREAT VULNERABLE

AREASRESULT PROTECTIVE

MEASURESRISK

Electrical outages Fluctuations

Computer CenterNetworksLANsTelephone Service

-Equipment Damage-Denial of Service-Data Destruction-Data Corruption

UPS SystemSystem BackupsGeneratorStaff Training

High

Telecommunication Network Failure

Main ComputingNetworks LANsTelephone Service

-Denial of Service Alternate routingUPS SystemGeneratorStaff Training

High

Hardware Failure Computer CenterNetworksLANsTelephone Service

-Denial of Service-Data Destruction-Data Corruption-Equipment Loss

On-Site EngineerHardware contracts24-hour support by Networks & OperationsSystem BackupsStaff Training

High

System Software FailureAlteration of Software

Main ComputingNetworks

-Denial of Service-Data Destruction-Data Corruption

Software support by vendorSystem BackupsStaff Training

Low

Application Software Failure

Applications -Denial of Service-Data Destruction-Data Corruption

24-hour support by applicationsSystem BackupsStaff Training

Medium

Fire Computer CenterNetworksLANsTelephone Service

-Denial of Service-Data Destruction-Equipment Loss-Facility Loss

Fire alarm systemsHalon systemsEmployee trainingAccess controlStructural DesignOff-site backupsContingency Plan

High

Water Damage Computer CenterNetworksLANsTelephone Service

-Denial of Service-Data Destruction-Equipment Loss-Facility Loss

Structural DesignOff-site backupsContingency PlanOff-Site backups

High

File Alteration -(Accidental or Intentional)DisclosureSystem user errorEmployee SabotageUnauthorized UseViruses

DatabasesSoftwareSystem integrity

-Data Corruption-Data Destruction-Denial of Service-Confidentiality breach

Security auditingLogin authenticationAudit trailsAccess controlSecurity monitoringSystem BackupsStaff Training

High

Physical SecurityUnauthorized UseFraudExternal SabotageHackers

Computer CenterNetworksLANsTelephone Service

-Denial of Service-Equipment Loss-Facility Loss-Data Destruction-Data Corruption

Access controlStructural designEmployee trainingSystem BackupsLogin authentication

Medium

53

THREAT VULNERABLE AREAS

RESULT PROTECTIVE MEASURES

RISK

-Theft Staff TrainingCivil DisturbancesDam CollapseEarthquakeFloodLighteningSmoke, dirt, dustSnow/Ice StormVolcanoWindstorm

Computer CenterNetworksLANsTelephone Service

-Denial of Service-Equipment Loss-Facility Loss-Data Destruction

Structural designSystem BackupsContingency Plan

Medium

Bomb ThreatsBuilding CollapseEpidemicsExplosionsHostage TakingHurricanesLandslidesLiquid leakageNuclear Reactor AccidentPanic CrushesSandstormsStrikeTerrorismThermo-Nuclear DisasterTidal WavesTornadoToxic SpillsTsunami

Computer CenterNetworksLANsTelephone Service

-Denial of Service-Equipment Loss-Facility Loss-Destruction of data

Structural designSystem BackupsContingency Plan

Low

Theft Computer CenterDatabases

-Confidentiality breach-Equipment Loss

Access controlLogin authenticationSeparation of dutiesStaff Training

High

54

Appendix L – Tape Inventory

Here are the current inventory procedures for backup tapes.

Operations staff take tapes over daily and bring back the ones that are being replaced. (These are the LMS nightly processing backups). Operations takes the weekly VMS cumulative backup tape over on Mondays. It dismounts Sunday and a new, prestaged backup initiates Monday morning at 6:30 am. Again, Operations returns the tape being replaced. weekly backups are retained for 30 days and the monthly backups for 365 days. Only the most current monthly backup is stored in the vault, older monthlies are stored in the on site tape repository. Networks & Operations staff (Larry Beintema) uses the oldest monthly backups (created 1 year earlier) from Legato as scratch tapes for the current monthly backup. Operations brings them over the Monday after the first weekend of the month and returns the newly created backups the following morning. Operations takes backup tapes from the email machines and the VCS console to the vault on Monday and brings the tapes being replaced back. There are currently old tapes that were created with 5 and 10 year retentions stored in the vault and they are returned and scratched as they expire. Each of the above backups has their own space in the vault so they are easily identified and retrieved when necessary.

55