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

go beyond <strong>IT</strong> baseline protection and can not normally be carried out for<br />

standard software as the source code is not disclosed by the manufacturer.<br />

Functionality tests are intended to prove that the test is in accordance with the<br />

specification. Using penetration tests, it is intended to determine whether<br />

known or assumed weaknesses can be exploited in practical operation, for<br />

example by attempts to manipulate the security mechanisms or by bypassing<br />

security mechanisms by manipulation at the operating system level.<br />

<strong>The</strong> way the results are to be secured and evaluated should be stipulated,<br />

particularly as regards repeating tests. It should be clarified which data should<br />

be kept during and after the test.<br />

Creating test data and test cases<br />

<strong>The</strong> preparation of tests also includes the creation of test data. Methods and<br />

procedures should be stipulated and described in advance.<br />

A number of test cases in accordance with the testing time must be created for<br />

each test. Each of the following categories should be taken into consideration.<br />

Standard cases are cases which are used to test whether the defined functions<br />

are implemented correctly. <strong>The</strong> incoming data are called normal values or<br />

limit values. Normal values are data within the valid input area, limit values<br />

are threshold data.<br />

Error cases are cases where attempts are made to provoke possible program<br />

error messages. <strong>The</strong> input values which should cause a predetermined error<br />

message to occur in the program are called false values.<br />

Exceptional cases are cases where the program has to react differently than to<br />

standard cases. It must therefore be checked whether the program recognises<br />

these as such and then processes them correctly.<br />

Examples:<br />

- If the input parameters can be between 1 and 365, tests are to be carried out<br />

with false values (e.g. 0 or 1000), the limit values 1 and 365 and with<br />

normal values between 1 and 365.<br />

- An appointment planning program should take national holidays into<br />

consideration. A special case is when a certain day is a holiday in all states<br />

except one. <strong>The</strong> program must then react appropriately for this state and<br />

this day.<br />

In the event that it is too time-consuming or difficult to create test data,<br />

anonymous actual values can be used for the test. For reasons of<br />

confidentiality, actual data must be made anonymous. It should be ensured<br />

that these anonymous data do not cover all limit values and exceptional cases,<br />

these having to be created separately.<br />

Beyond the test data, all types of possible user errors should be taken into<br />

consideration. Particularly difficult are all user reactions which are not<br />

planned in the program sequence and which are thus not correctly rejected.<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!