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.

<strong>IT</strong> <strong>Baseline</strong> <strong>Protection</strong> of Generic Components<br />

_________________________________________________________________________________________<br />

1 Finding Your Way Around the<br />

<strong>IT</strong> <strong>Baseline</strong> <strong>Protection</strong> <strong>Manual</strong><br />

1.1 <strong>IT</strong> <strong>Baseline</strong> <strong>Protection</strong>: the Aim, Concept and Central Idea<br />

<strong>The</strong> <strong>IT</strong> <strong>Baseline</strong> <strong>Protection</strong> <strong>Manual</strong> presents a set of recommended standard security measures or<br />

"safeguards", as they are referred to in the manual, for typical <strong>IT</strong> systems. <strong>The</strong> aim of these <strong>IT</strong> baseline<br />

protection recommendations is to achieve a security level for <strong>IT</strong> systems that is reasonable and<br />

adequate to satisfy normal protection requirements and can also serve as the basis for <strong>IT</strong> systems and<br />

applications requiring a high degree of protection. This is achieved through the appropriate application<br />

of organisational, personnel, infrastructural and technical standard security safeguards.<br />

To facilitate structuring and processing of the highly heterogeneous area of <strong>IT</strong>, including the<br />

operational environment, the <strong>IT</strong> <strong>Baseline</strong> <strong>Protection</strong> <strong>Manual</strong> is structured in a modular fashion. <strong>The</strong><br />

individual modules reflect typical areas in which <strong>IT</strong> assets are employed, for example client/server<br />

networks, buildings, communications and application components Every module begins with a<br />

description of the typical threats which may be expected in the given area together with their assumed<br />

probability of occurrence. This "threat scenario" provides the basis for generating a specific package<br />

of measures from the areas of infrastructure, personnel, organisation, hardware, software,<br />

communications and contingency planning. <strong>The</strong> threat scenarios are presented in order to create<br />

awareness, and are not required any further for the creation of a security concept which affords <strong>IT</strong><br />

baseline protection. It is not necessary for users to perform the analysis work mentioned above, which<br />

requires considerable effort, in order to attain the security level that is needed for an average<br />

protection requirement. On the contrary, it is sufficient to identify the modules which are relevant to<br />

the <strong>IT</strong> system or <strong>IT</strong> assets under consideration and to implement all the safeguards recommended in<br />

those modules in a consistent manner.<br />

Using the <strong>IT</strong> <strong>Baseline</strong> <strong>Protection</strong> <strong>Manual</strong>, it is possible to implement <strong>IT</strong> security concepts simply and<br />

economically in terms of the resources required. Under the traditional risk analysis approach, first of<br />

all the threats are identified and assigned a likelihood of occurrence, and the results of this analysis are<br />

then used to select the appropriate <strong>IT</strong> security measures, following which the remaining residual risk<br />

can be assessed. <strong>The</strong> approach adopted in the <strong>IT</strong> <strong>Baseline</strong> <strong>Protection</strong> <strong>Manual</strong> on the other hand<br />

requires only that a target versus actual comparison is performed between the recommended measures<br />

and those already implemented. <strong>The</strong> security shortcomings which need to be eliminated through<br />

adoption of the recommended measures are defined in terms of those security measures identified<br />

which are lacking and not yet implemented. Only where the protection requirement is significantly<br />

higher is it necessary to also carry out a supplementary security analysis, weighing up the costeffectiveness<br />

of implementing additional measures. However, it is generally sufficient here to<br />

supplement the recommendations made in the <strong>IT</strong> <strong>Baseline</strong> <strong>Protection</strong> <strong>Manual</strong> with appropriate tailored<br />

and more stringent measures.<br />

_________________________________________________________________________________________<br />

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

Info / Contacts<br />

Objectives / Concepts<br />

Application<br />

Structure / Interpretation

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

Saved successfully!

Ooh no, something went wrong!