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 - Communications Remarks<br />

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

S 5.63 Use of PGP<br />

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

Implementation responsibility: <strong>IT</strong> users, Administrator<br />

PGP (Pretty Good Privacy) is an encryption program that is in widespread use.<br />

PGP can be used to encrypt and decrypt messages and files, and to attach a<br />

digital signature (also referred to as an electronic signature) in order to be able<br />

to prove that unauthorised changes have been made to a message or file. Keymanagement<br />

tasks, such as adding and removing keys, can also be carried out<br />

with the aid of PGP.<br />

Encryption and digital signatures<br />

PGP makes use of symmetric and asymmetric cryptographic procedures.<br />

Symmetric procedures such as IDEA are used for data encryption, while<br />

asymmetric procedures such as Diffie-Hellmann are used for the exchange of<br />

keys and RSA or DSS for signature generation.<br />

PGP creates and uses public and private keys in pairs of keys. For every<br />

private key, there is exactly one public key. It is practically impossible to<br />

determine the private key simply on the basis of the public one. A message<br />

that has been encrypted with a public key or signed with the private key can<br />

only be decrypted with the corresponding private key or verified with the<br />

originator's public key. <strong>The</strong> public key can be revealed to anyone. Its purpose<br />

is to encrypt messages to the owner of the private key.<br />

In order to provide proof of unauthorised manipulation and therefore to<br />

protect messages against modifications, PGP uses the originator's private key<br />

to calculate a cryptographic checksum for the message - the digital signature.<br />

Using the public key belonging to the sender of a message, every<br />

communication partner can determine whether the cryptographic checksum at<br />

the end of the message is valid or whether the message has been modified<br />

without authorisation.<br />

When using PGP it is advisable to use a combination of the two functionalities<br />

described above. <strong>The</strong> standard procedure should be for messages and files to<br />

be encrypted with the recipient's public key first and then to be signed with the<br />

sender's private key, in order to obtain the greatest possible protection.<br />

Versions<br />

PGP is available for a wide variety of computer platforms (Unix systems,<br />

DOS, Windows NT/9x etc.). <strong>The</strong> most commonly used versions are 2.6.3i, 5.x<br />

and 6.x. Versions 5.x and 6.x are equipped with a graphical user interface, but<br />

they are not downward-compatible with the preceding versions. Especially<br />

when these versions of PGP are used in conjunction with operating systems<br />

from the Windows family it should be borne in mind that it may be possible to<br />

circumvent the security mechanisms of PGP by exploiting security<br />

deficiencies in the operating system.<br />

In view of the lack of downward compatibility, it is advisable to make<br />

inquiries as to which version of PGP will be used by the communication<br />

partners before exchanging encrypted messages. Version 2.6.3i is still in<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!