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 - Hardware & Software Remarks<br />

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

S 4.34 Using encryption, checksums or digital<br />

signatures<br />

Initiation responsibility: <strong>IT</strong> Security Management<br />

Implementation responsibility: <strong>IT</strong>-users<br />

If confidential information or information with high demands for integrity is<br />

transmitted and if there is a possibility of this data being disclosed,<br />

manipulated by unauthorised parties or changed due to technical failure, a<br />

cryptographic procedure for the protection of the data intended for transfer<br />

should be considered.<br />

<strong>Protection</strong> of confidentiality by means of encryption<br />

Confidential information should be encrypted before transmission. <strong>The</strong><br />

decisive features of any encryption procedure are the quality of the algorithm<br />

and the selected key. An algorithm which has proven adequate for mediumlevel<br />

protection is the Triple DES, which is based on the Data Encryption<br />

Standard (DES). It is easy to implement, as example source code using the<br />

programming language C is provided in many books. For use on stationary<br />

and portable PCs, BSI can, under certain basic prerequisites, provide public<br />

agencies with an offline encryption program (Chiasmus for Windows)<br />

meeting medium-level protection requirements. An order form can be found<br />

on the CD-ROM of this manual (see appendix: Auxiliary Materials).<br />

In order to comply with confidentiality requirements of the information to be<br />

transmitted, the recipient's and sender's <strong>IT</strong> system must provide sufficient<br />

access protection for the encryption program. Where necessary, it should be<br />

stored on an exchangeable data medium, kept under lock and key and only<br />

used/imported when the need arises.<br />

Integrity protection using checksums, encryption or digital signatures<br />

If only the integrity of data intended for transfer is to be protected, it should be<br />

clarified whether the protection should only be sufficient for incidental<br />

alterations, i.e. due to transmission errors, or also for manipulation. If only<br />

incidental alterations are to be detected, checksum procedures (e.g. Cyclic<br />

Redundancy Checks) or error correction codes can be used. <strong>Protection</strong> against<br />

manipulation is also offered by processes which create a so-called Message<br />

Authentication Code (MAC) using a symmetric encryption algorithm (e.g.<br />

DES) from the information to be transmitted. Other processes use an<br />

asymmetric encryption algorithm (e.g. RSA) in combination with a hash<br />

function and create a "digital signature". <strong>The</strong> resulting "fingerprints"<br />

(checksum, error correction codes, MAC, digital signature) are transferred<br />

together with the data to the recipient, who can then check them.<br />

See S 2.46 Appropriate key management for the transmission or exchange of<br />

any necessary keys. Further information on the use of cryptographic<br />

procedures and products can be found in chapter 3.7 Crypto-concept.<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!