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.163 Determining the factors influencing<br />

cryptographic procedures and products<br />

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

Implementation responsibility: Administrators; staff responsible for the<br />

individual <strong>IT</strong> applications<br />

Before a decision can be taken as to which cryptographic procedures and<br />

products are to be used, details of a number of influencing factors need to be<br />

ascertained. <strong>The</strong> system administrators and staff responsible for the various <strong>IT</strong><br />

systems and <strong>IT</strong> applications can be interviewed for this purpose. <strong>The</strong> results<br />

are to be comprehensibly documented.<br />

<strong>The</strong> following influencing factors must be determined for all storage locations<br />

and transmission links specified in S 2.162 Determining the need to use<br />

cryptographic procedures and products:<br />

Security aspects<br />

- What are the protection requirements or what security level is it considered<br />

necessary to achieve?<br />

- Which cryptographic functions are necessary for this (encryption,<br />

protection of integrity, authenticity and/or non-repudiation)?<br />

- Potential of intruders: what type of intruders are to be expected (time<br />

available, financial resources, technical skills)?<br />

<strong>The</strong> answers to these questions are derived from S 2.162 Determining the need<br />

to use cryptographic procedures and products.<br />

Technical aspects<br />

Operating heavily branched <strong>IT</strong> infrastructures with their large numbers of<br />

individual components and special equipment (network nodes, servers,<br />

databases, etc.) means that security systems must also be heavily branched,<br />

with several functional units (security management, security servers, security<br />

application components, etc.). Generally speaking the systems have to be<br />

examined with a view to not only the functionalities per se but also structural<br />

and organisational aspects. It is also necessary to differentiate in respect of the<br />

specific technical placement of security components and their integration into<br />

non-security components, because this has a direct influence on the<br />

implementation of the security functions, on the support required from the<br />

operating systems, on expenditure and the cost factor, and not least on the<br />

attainable level of security. <strong>The</strong> geographical localities and the levels of the<br />

protocol stack at which the respective security services are implemented and<br />

the way in which they are incorporated in the processes of the <strong>IT</strong> system being<br />

protected are quite crucial for the security evaluation. <strong>The</strong> following questions<br />

thus arise:<br />

- <strong>Protection</strong> offered by the environment: what protection does the<br />

environment offer (in terms of infrastructure (access), organisation, staff,<br />

technical facilities (protection by operating system, ...))?<br />

- <strong>IT</strong> system environment: what technology is used, which operating systems,<br />

etc.?<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!