IT Security Risk Management (ITSRM)
Contingency Planning
The development of the contingency plan is base on the below assumptions.  However, these assumptions should be updated and/or modified to reflect the organization's "real world" environment.

Contingency Plan is based on the following assumptions:
  • The organization, business process, and/or asset is inoperable at the primary site (e.g., computer center) and cannot be recovered within an acceptable period - the Recovery Time Objective (RTO).

  • Key personnel have been identified and trained in their emergency response and recovery roles; they are available to activate the Contingency Plan.

  • Preventive controls (e.g., generators, environmental controls, waterproof tarps, sprinkler systems, fire extinguishers, and fire department assistance) are fully operational at the time of the incident.

  • Computer center equipment, including components supporting mission critical and/or major applications, are connected to an uninterruptible power supply (UPS) that provides 45 minutes to 1 hour of electricity during a power failure.

  • The safety of the initial emergency response teams can be assured during the damage-assessment period.

  • The contingency period may exist for a long as circumstances require.

  • The designated alternate facility is a <hot OR warm OR cold> alternate site for redundant system network capabilities.

  • The designated alternate site is not affected by the incident, is operational, and is accessible to designated and/or appropriate personnel. 

  • If relocation to the alternate site is unnecessary, the Primary Damaged Facility is adequately secure, the building manager and security staff can guarantee the safety of all authorized staff re-entering the building after the incident.

  • The levels of protection are maintained in accordance with the guidance provided by the Security Office.

  • Designated and approved system and application backups have been tested and will run on duplicate servers.

  • Simultaneous or concurrent incidents at the primary location and the alternate facility have not occurred.

  • External organizations have the capability to transmit/receive data to/from primary or designated alternate facility.

  • If an alternative work site is required, workspace will be furnished with desks, tables, and chairs within a reasonable period.

  • Data backup tapes are undamaged and accessible.

  • Additional office space for the remaining business operations not included in this plan will be identified at time of the incident.

  • The designated and appropriate CP teams have the resources necessary to complete their tasks.

  • The executive level management will guarantee the resources for the recovery and restoration efforts.

  • Vendor based service level agreements (SLA’s) have been executed with sections to include the necessary support the system and/or agency will require during a post-disaster event or continuity of operations scenario (i.e. Hardware/software, service technicians, space, equipment, distributed work centers for employees, etc.).

  • This contingency plan is designed for use under pre-defined disaster conditions

  • This contingency plan is not designed for minor, daily operational problems, but for a prolonged service interruption over a defined period of time.

  • The contingency plan will be a living document and reviewed on a recurring schedule and updated as necessary. Review period will be every 90 days or more frequently, as required.

Contingency Planning