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

- It is possible to backup instantaneous data at specified intervals while an<br />

application is being run.<br />

In the event that the product is to have encryption components, the following<br />

requirements are recommended:<br />

- Encrypted algorithms used by government agencies should be approved by<br />

the BSI. Individual consultation by the BSI is recommended in this case. If<br />

not in agencies, the DES is suitable for moderate protection requirements.<br />

- <strong>The</strong> key management must be in line with the functionality of the product.<br />

In particular, fundamental differences between algorithms must be<br />

considered here:<br />

- symmetric algorithms use a key for encrypting and decrypting which<br />

is to be kept secret,<br />

- asymmetric algorithms use a public key for encrypting and a private<br />

key (to be kept secret) for decrypting.<br />

- <strong>The</strong> product must correctly manage security-critical parameters, such as the<br />

key. Keys should thus never be stored unprotected (even expired keys), i.e.<br />

readable.<br />

In the event that the product is to have an integrity test feature, the following<br />

requirements are recommended:<br />

- <strong>The</strong> product carries out an integrity check every time a program is called<br />

up.<br />

- Mechanisms should be used which can detect intentional manipulation of<br />

address fields and payload data during data transmission. Knowledge of the<br />

algorithms alone, without other special knowledge, should not be sufficient<br />

to manipulate the above data without detection.<br />

In the event that person-related data are to be processed with the product, the<br />

following requirements concerning data privacy are placed, for example:<br />

- <strong>The</strong> product may not permit general requests for data analyses. <strong>The</strong>se<br />

analyses of data must be limited to certain criteria.<br />

- It must be possible to parameterise the system in such a way that changes,<br />

deletions or print-outs for certain files are only possible according to the<br />

two-person principle.<br />

- It must be possible to parameterise the logging feature in such a way that<br />

records can be kept of who made which changes to person-related data.<br />

- <strong>The</strong> transfer of person-related data must be determined and checked with<br />

suitable random tests (BDSG, § 10). <strong>The</strong> type of random test must be<br />

individually programmable.<br />

- <strong>The</strong> product must enable person-related data to be deleted. Alternatively, it<br />

must be possible to block person-related data in order to limit or prevent<br />

these being processed or used.<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!