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.64 Verification of data before transmission /<br />

elimination of residual information<br />

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

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

Before a file is dispatched via e-mail or placed on a WWW-server, or before a<br />

data medium is transferred to another party, a check must be made as to<br />

whether the file/data medium holds residual information not intended for<br />

public attention. Such residual information can have a variety of origins<br />

entailing a corresponding variety of measures which need to be taken. <strong>The</strong><br />

most common sources of such residual information are described in the<br />

following.<br />

In general, files generated with standard software such as word processing and<br />

spread-sheet programs should be checked for residual information. Some of<br />

this information is stored with, and some without the user being aware of this.<br />

Before files are forwarded, they should at least be spot-checked for the<br />

presence of undesired additional information. For this purpose, a different<br />

editor should be used than the one with which the file was originally created.<br />

In this process, it must be noted that not all residual information can be<br />

deleted directly without disrupting the file format. If, for example, certain<br />

bytes are deleted from a file generated with a particular word processor, the<br />

software might no longer recognise the file format. To eliminate residual<br />

information:<br />

- <strong>The</strong> file can be stored in a different format, e.g. “Text only“ or HTML<br />

- <strong>The</strong> useful data can be copied to another instance of the same standard<br />

software on an <strong>IT</strong> system which does not run any other applications. This is<br />

particularly advisable in the case of files with a long history of<br />

modifications.<br />

To prevent the forwarding of information which was originally added on<br />

purpose by the creator of the document - such as text in “hidden“ format - but<br />

whose presence was later forgotten, it might prove useful to print out the file.<br />

For this purpose, all printer options for outputting hidden formats should be<br />

activated.<br />

Residual information / slack bytes<br />

Every operating system has a smallest possible physical memory unit of a<br />

specified size. Under DOS, this unit is termed sector and has a size of 512<br />

bytes. Under UNIX, this unit is termed block, and its size depends on the type<br />

of UNIX system in use. Under DOS, the individual sectors of a partition are<br />

grouped logically into clusters. <strong>The</strong> number of sectors in a cluster depends on<br />

the size of the partition. When a file is opened, one or more clusters are<br />

allocated to it. <strong>The</strong> last cluster is not occupied fully, unless the size of the<br />

stored file happens to be an exact multiple of the cluster size.<br />

This takes up memory. <strong>The</strong> average storage space required increases with the<br />

cluster size. As the cluster size, in turn, increases with the partition size, the<br />

latter should not be allowed to exceed a certain limit. Example: Given a<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!