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

S 2.138 Structured data storage<br />

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

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

Poorly structured data storage can lead to a wide variety of problems. For this<br />

reason, all <strong>IT</strong> users should be instructed on how to store data in clear, wellstructured<br />

manner. Appropriate structures should be specified by the<br />

Administrators on all servers. This is also a prerequisite for achieving a<br />

differentiated allocation of access rights.<br />

Program and work files should always be stored in separate sectors. This<br />

makes it easier to obtain an overview, simplifies data backups and ensures<br />

correct access protection. In the case of most application programs, very few<br />

or no configuration files are modified following installation. If possible, all<br />

files which are modified regularly should be stored in separate directories, so<br />

that only those directories need to be included in the regular data backups.<br />

Where programs and data are kept properly separated, it is sufficient to only<br />

include the data in the regular data backups. It is important to have working<br />

files carefully backed up so that, if necessary, the backups can also be worked<br />

on on other systems.<br />

In the case of networked systems, it is also necessary to determine which<br />

programs and files should be stored on local hard disks or on a network server.<br />

Both options have advantages as well as disadvantages, and must be evaluated<br />

in accordance with the existing organisational structure as well as the<br />

hardware and software in use. For example, files with high availability<br />

requirements and the related application programs should be stored on<br />

workstation computers rather than on the network server. In this case,<br />

appropriate contingency measures also need to be implemented for these<br />

workstation computers.<br />

Task-specific or project-specific directories should be created in order to<br />

facilitate the allocation of files. As few files as possible should be stored in<br />

personal directories.<br />

To prevent the existence of different versions of basic files required for<br />

ongoing activities, such as letter templates, forms, project plans etc., such files<br />

should be managed centrally. For example, these files should be stored on a<br />

server so that all users have read access to them, but only one person is<br />

authorised to modify each individual file.<br />

<strong>The</strong> following example shows how data can be structured on a server by<br />

specifying directory paths:<br />

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

<strong>IT</strong>-<strong>Baseline</strong> <strong>Protection</strong> <strong>Manual</strong>: Oktober 2000<br />

Keep programs and<br />

application files separate<br />

Task-or project-specific<br />

directories

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!