19.12.2012 Views

IT Baseline Protection Manual - The Information Warfare Site

IT Baseline Protection Manual - The Information Warfare Site

IT Baseline Protection Manual - The Information Warfare Site

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Safeguard Catalogue - Communications Remarks<br />

____________________________________________________________________ .........................................<br />

S 6.11 Development of a post-incident recovery plan<br />

Initiation responsibility: Head of <strong>IT</strong> Section; <strong>IT</strong> Security Management;<br />

staff responsible for the individual <strong>IT</strong><br />

applications<br />

Implementation responsibility: Head of <strong>IT</strong> Section; staff responsible for<br />

emergency preparedness (contingency<br />

planning); administrator<br />

In order to ensure correct restart after failure of an <strong>IT</strong> system, the following<br />

information should be documented (see example in S 6.3 Development of an<br />

Emergency Procedure <strong>Manual</strong>, Part C).<br />

- Repurchase opportunities, e.g. the use of a test computer for interactive<br />

communication or replacement procurement (c.f. S 6.14 Replacement<br />

procurement plan),<br />

- internal/external alternatives for <strong>IT</strong> applications should be listed (c.f. S 6.6<br />

Study of internally and externally available alternatives);<br />

- data transmission supply (c.f. S 6.10 Contingency plans for breakdown of<br />

data transmission) for emergency operation in order to guarantee the<br />

minimum data transmission required,<br />

- <strong>IT</strong> applications in reduced <strong>IT</strong> operations (c.f. S 6.5 Definition of "restricted<br />

<strong>IT</strong> operation"),<br />

- system start-up of the <strong>IT</strong> components and inclusion into the <strong>IT</strong> system,<br />

- In order to meet the availability requirements (cf. S 6.1 Development of a<br />

survey of availability requirements) of the various <strong>IT</strong> applications, a<br />

sequence for restart of the <strong>IT</strong> applications must be laid down.<br />

<strong>The</strong> steps required for restarting an <strong>IT</strong> application should be shown in the<br />

Contingency <strong>Manual</strong> (c.f. example in S 6.3 Development of an Emerngency<br />

Procedure <strong>Manual</strong>, Part D). Such steps include, for example:<br />

- set-up and installation of the required hardware components;<br />

- Loading of the system software<br />

- installation of the application software;<br />

- provision of the necessary data, including configuration files;<br />

- Restarting<br />

Auditable logging of the restart must be ensured.<br />

<strong>The</strong> feasibility of the post-incident recovery plan is to be checked by<br />

emergency preparedness exercises (for both internally and externally available<br />

alternatives). When carrying out such tests, particular attention must be given<br />

to the exclusive use of the software and data held in internal or external<br />

backup archives.<br />

Depending on the size of the used <strong>IT</strong> applications, restart can be very timeconsuming.<br />

<strong>The</strong> times required by the restarting steps can be ascertained with<br />

____________________________________________________________________ .........................................<br />

<strong>IT</strong>-<strong>Baseline</strong> <strong>Protection</strong> <strong>Manual</strong>: Oktober 2000

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

Saved successfully!

Ooh no, something went wrong!