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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Safeguard Catalogue - Organisation Remarks<br />

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

depth of the various features should be based on the confidence factor, i.e. the<br />

amount of confidence placed in the correct operation of this feature. <strong>The</strong><br />

proneness to error and frequency of use of the feature must also be taken into<br />

consideration. More detailed information is to be found in ISO 12119.<br />

Notes:<br />

- For requirements relevant to security, the test depth can also be adapted to<br />

the mechanism strength required.<br />

- <strong>The</strong> testing time for the initial tests should be kept to a minimum in regard<br />

to the other tests.<br />

<strong>The</strong> total testing time should then be distributed to the individual test sections<br />

in accordance with the relative testing time of the feature.<br />

Determining persons-in-charge of testing<br />

It should be determined for each test which tasks are to be carried out and who<br />

is responsible for these. In particular, it should be ensured that the staff /<br />

works council, the Data Privacy Officer and the <strong>IT</strong> Security Officer are<br />

involved in some tests.<br />

Test environment<br />

Testing is always destructive as errors are being looked for. Tests should thus<br />

always be conducted in an isolated test environment.<br />

If possible, the test environment should be a precise functional copy of the<br />

production environment. It is generally not viable to completely recreate the<br />

production environment.<br />

So that the same conditions are present for the selected products, a reference<br />

test environment should be defined. This can be further adjusted or limited for<br />

individual tests.<br />

<strong>The</strong> resources required for the various tests (equipment, <strong>IT</strong> infrastructure)<br />

should be specified. It should be described in detail when, and to what extent,<br />

these must be available.<br />

It is important that all operating systems in all versions used in production are<br />

available in the test environment. <strong>The</strong> intention is to determine system-based<br />

weaknesses of components of the production environment in connection with<br />

the standard software production to be installed. In exceptional cases, if<br />

aspects can be generalised, individual components can be omitted.<br />

<strong>The</strong> following aspects should be observed and help to set up a reliable and<br />

suitable test environment:<br />

- An up-to-date virus scan program should ensure that the test environment<br />

is free of viruses.<br />

- <strong>The</strong> test environment must be free of side effects on the actual operation. In<br />

order to avoid interaction from the outset, the installation of dedicated <strong>IT</strong><br />

systems is recommended.<br />

- <strong>The</strong> access rights must be configured in the test environment in the same<br />

way as in the production area.<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!