Policy 7230A - Department of Administration

Policy 7230A - Department of Administration Policy 7230A - Department of Administration

10.10.2014 Views

Mandatory Baselines 9. Contingency Planning These Contingency Planning Mandatory Baselines support the Enterprise Security Policy (ITEC 7230 Rev 1), the Business Contingency Planning Policy (ITEC 5300) and the Business Contingency Implementation Policy (ITEC 5310). Mandatory Non-Mandatory Procedures Baselines Procedures Baselines 9. Contingency Planning 9.1. Contingency Plans 9.1.1. Build a Plan (5 sets) (3 sets) 9.1.2. Test the Plan (3 sets) (2 sets) 9.2. Contingency Infrastructure 9.2.1. Required Contingency Infrastructure (1 set) 9.3. Contingency Operations 9.3.1. Build a Team and Provide Training (4 sets) (3 sets) 9.3.2. Backup Scheduling and Frequency (1 sets) (1 sets) 9.1. Contingency Plans The following are the Mandatory Baselines that support the Contingency Plans section of the Default Security Requirements: 9.1.1. Build a Plan Contingency planning requires the identification of assets to be protected by the plan, determination of the strategies applicable to the execution of the plan and the documentation of the plan itself: 9.1.1.a Critical Resources and Recovery Time Objectives • By default systems will be categorized into four groupings for recovery purposes: o Systems deemed critical upon which the operation of other critical systems depends. These systems shall have a 120 minute (2 hour) Recovery Time Objective. o Systems deemed critical upon which the operation of no other critical systems depends. These systems shall have a 480 minute (8hour) Recovery Time Objective. o Systems deemed non-critical upon which the operations of critical systems depends. These systems shall have an 8 hour (1 business day) Recovery Time Objective. o Systems deemed non-critical upon which the operation of no critical systems depends. These systems shall have a 24 hour (1 day) Recovery Time Objective. 9.1.1.b Recovery Prioritization Schedule • Systems recovery prioritization shall be in accordance with established criticality and Recovery Time Objectives. Page 16 of 25

9.1.1.c Contingency Plan Update Frequency and Scheduling • Contingency plans will be reviewed and updated on an at least annual basis or at such time as contingency testing or contingency operations indicates a deficiency in the contingency plan. 9.1.2. Test the Plan To ensure the applicability of the plan and to verify that the plan can be acted upon as created, periodic testing is required: 9.1.2.a Mandatory Contingency Testing Methodologies • The following capabilities must be included in the contingency testing program: o System recovery to a primary platform from backup. o System recovery to a secondary platform from backup. o System failover from a primary system to a redundant system. o System failover from a primary facility to a redundant facility. o System performance in all circumstances. o Restoration of normal operations in all circumstances. o Co-ordination and communications. • Contingency testing can be conducted in one of two ways: o Classroom or tabletop exercises walkthrough contingency operations without any contingency operations occurring. o Functional or simulation exercises recreate actual disruptions and require the execution of contingency operations. 9.1.2.b Contingency Testing Frequency and Scheduling • Classroom or tabletop exercises shall be performed on at least an annual basis. • Functional or simulation exercises shall be performed on at least a triennial basis. 9.2. Contingency Infrastructure The following are the Mandatory Baselines that support the Contingency Infrastructure section of the Default Security Requirements: 9.2.1. Required Contingency Infrastructure Appropriate infrastructure must be put in place to provide for appropriate ongoing operations in the event of a business impacting event: Mandatory Baselines Page 17 of 25

9.1.1.c Contingency Plan Update Frequency and Scheduling<br />

• Contingency plans will be reviewed and updated on an at least<br />

annual basis or at such time as contingency testing or<br />

contingency operations indicates a deficiency in the<br />

contingency plan.<br />

9.1.2. Test the Plan<br />

To ensure the applicability <strong>of</strong> the plan and to verify that the plan can be acted<br />

upon as created, periodic testing is required:<br />

9.1.2.a Mandatory Contingency Testing Methodologies<br />

• The following capabilities must be included in the contingency<br />

testing program:<br />

o System recovery to a primary platform from backup.<br />

o System recovery to a secondary platform from backup.<br />

o System failover from a primary system to a redundant<br />

system.<br />

o System failover from a primary facility to a redundant<br />

facility.<br />

o System performance in all circumstances.<br />

o Restoration <strong>of</strong> normal operations in all circumstances.<br />

o Co-ordination and communications.<br />

• Contingency testing can be conducted in one <strong>of</strong> two ways:<br />

o Classroom or tabletop exercises walkthrough<br />

contingency operations without any contingency<br />

operations occurring.<br />

o Functional or simulation exercises recreate actual<br />

disruptions and require the execution <strong>of</strong> contingency<br />

operations.<br />

9.1.2.b Contingency Testing Frequency and Scheduling<br />

• Classroom or tabletop exercises shall be performed on at least<br />

an annual basis.<br />

• Functional or simulation exercises shall be performed on at<br />

least a triennial basis.<br />

9.2. Contingency Infrastructure<br />

The following are the Mandatory Baselines that support the Contingency<br />

Infrastructure section <strong>of</strong> the Default Security Requirements:<br />

9.2.1. Required Contingency Infrastructure<br />

Appropriate infrastructure must be put in place to provide for appropriate<br />

ongoing operations in the event <strong>of</strong> a business impacting event:<br />

Mandatory Baselines<br />

Page 17 <strong>of</strong> 25

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!