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 6.56 Data backup when using cryptographic<br />

procedures<br />

Initiation responsibility: Head of <strong>IT</strong> Section, <strong>IT</strong> Security Management<br />

Implementation responsibility: <strong>IT</strong> Security Officer<br />

When a company or agency is using cryptographic procedures, it is important<br />

not to neglect the subject of data backup. Apart from the question of how a<br />

backup of the encrypted data should best be performed, it is also necessary to<br />

consider whether the cryptographic keys should be backed up, and if so, how.<br />

It also makes sense to back up the configuration data relating to the crypto<br />

products that are used.<br />

Backing up the keys<br />

Very careful thought must be given to the question of whether and how to<br />

back up the cryptographic keys, because every copy of a key is a potential<br />

weak point.<br />

Nevertheless, there may be various reasons why it is necessary to store<br />

cryptographic keys. A variety of methods can be used for storing keys:<br />

- Storage on a transportable data medium, such as a floppy disk or chip card<br />

(mainly used for distributing or exchanging keys, see S 2.46 Appropriate<br />

key management), for transport purposes<br />

- Storage in <strong>IT</strong> components which have to have permanent access to<br />

cryptographic keys, for example for communication encryption<br />

- <strong>The</strong> safekeeping of keys as a precaution against key loss, or as part of<br />

arrangements for substitution<br />

<strong>The</strong> following points always have to be observed in this connection:<br />

- Cryptographic keys should be stored or kept in safekeeping in such a way<br />

that unauthorised users cannot read them out without this being noticed.<br />

For example, keys could be stored in special security hardware which<br />

automatically deletes the keys in the event of an attack. If they are stored in<br />

software, they should always be protected by a second encryption. It<br />

should be borne in mind that most standard applications which involve<br />

storing keys or passwords in the application generally do this using<br />

techniques that are easy to break. Another possible variant is to use the two<br />

person rule in the storage of keys, in other words dividing a key into two<br />

halves or different parts for storage purposes.<br />

- No copies should be made of communication keys or other short-lived<br />

keys. To rule out the possibility of unauthorised use, there should generally<br />

not be any copies made of private signature keys either. If it is decided to<br />

opt for a key storage solution in software only, i.e. without using a chip<br />

card or similar device, the risk of key loss is increased, for example as a<br />

result of bit errors or a hard disk defect. In this case it may be less costly to<br />

provide a sufficiently secure means of key storage than to inform every<br />

communications partner every time that a key is lost.<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!