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 />

- <strong>The</strong> access to the test environment must be controlled.<br />

- When taken over into production, it must be ensured that the product is<br />

configured in the same way as in the test environment. A suitable integrity<br />

protection system (digital signatures, checksums) should thus be used in<br />

the test environment.<br />

- <strong>The</strong> costs for setting up the test environment must be acceptable.<br />

After all planned tests have been concluded, it should be decided whether the<br />

test environment is to be dismantled. It may be necessary for more tests to be<br />

carried out, i.e. it might be viable to retain the test environment. Before the<br />

test environment is dismantled, the test data should be deleted if no longer<br />

required (e.g. for installation at a later date). Printer products should be<br />

disposed of correctly, programs should be deinstalled. <strong>The</strong> test licences of the<br />

products which were not selected should be returned.<br />

Contents of the test documentation<br />

<strong>The</strong> test plan should state how detailed the test documentation should be. <strong>The</strong><br />

aspects of comprehensibility, reproducibility and completeness should be<br />

taken into consideration.<br />

<strong>The</strong> test documentation must contain test plans, targets, processes and results.<br />

It must also describe the correspondence between the tests and the specified<br />

requirements. All test activities and the test evaluation (including reasons for<br />

decisions) should be set down in writing. <strong>The</strong>se include:<br />

- product name and description<br />

- test begin, end, and time<br />

- persons-in-charge<br />

- configuration of the test environment<br />

- description of the test cases<br />

- criteria for decisions, test results and argumentation<br />

- unfulfilled requirements of the Requirement Catalogue<br />

<strong>The</strong> test group should be able to have access to clear documentation and<br />

records of the test activities and results (e.g. recording tool, forms etc.).<br />

In the event that an automatic tool is used for testing, the test documentation<br />

must contain sufficient information about this tool and its usage so that the<br />

decision can be understood.<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!