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 - Organisation Remarks<br />

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

S 2.87 Installation and configuration of standard<br />

software<br />

Initiation responsibility: Head of <strong>IT</strong> section<br />

Implementation responsibility: Head of <strong>IT</strong> Section, Administrator<br />

<strong>The</strong> approved software is installed on the <strong>IT</strong> systems intended for it in<br />

accordance with the installation instructions. In addition to the programs to be<br />

installed, the installation instructions also contain configuration parameters<br />

and the set-up of the hardware- and software environment.<br />

Deviations from the installation instructions require the consent of the<br />

Approval Authority.<br />

If the users are to install the software themselves, they must be provided with<br />

installation instructions which enable installation to be carried out<br />

independently. At the very least, pilot installation by a typical user should be<br />

overseen by the <strong>IT</strong> Department, in order to check the comprehensibility of the<br />

installation instructions.<br />

As standard software is developed for a wide variety of application fields, it<br />

often contains more functions than are required to perform the specialist task.<br />

So that less problems and errors arise when working with the software, only<br />

the functions actually required should be installed. Functions which can lead<br />

to security problems must not be approved.<br />

Both before and after the installation of software, a complete backup should<br />

be made. If there are subsequent problems during installation, the first backup<br />

can be used to recreate a consolidated re-run point. Following successful<br />

installation, a complete backup should be made again, so that if there are<br />

problems later, the situation, following the successful installation of the<br />

product, can be restored.<br />

Successful installation is reported in writing to the office responsible for the<br />

acceptance of actual operation.<br />

As an option, installation can be accompanied by the use of a so-called ”delta<br />

tool” which documents all changes in an <strong>IT</strong> environment between two<br />

definable points in time. This documentation of changes is particularly helpful<br />

when it comes to the de-installation of software.<br />

When a new product is used, any databases which were produced with a<br />

previous product must be taken over. If it has become apparent from the tests<br />

that difficulties may arise in this respect, help positions must be created for the<br />

user or acceptance of the old databases must be carried out centrally by trained<br />

personnel.<br />

Additional controls:<br />

- Which provisions are in force?<br />

- What provisions exist with respect to possible deviations from the<br />

installation instructions?<br />

- How is the success of an installation reviewed?<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!