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.

Threats Catalogue Deliberate Acts Remarks<br />

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

T 2.60 Strategy for the network system and<br />

management system is not laid down or<br />

insufficient<br />

If no general organisational management strategies are laid down for the areas<br />

of network management and system management, mistakes in the<br />

coordination of individual subdomains can cause serious problems through<br />

errors in the configuration, which can cause the system to completely collapse<br />

at network level. This is particularly the case in medium and large networks<br />

with several management domains.<br />

For this reason, it is imperative that you lay down and enforce a management<br />

strategy. <strong>The</strong> following gives several examples of problems caused when the<br />

strategy for the network management and system management has not been<br />

laid down or is insufficient.<br />

Requirements are not analysed before the management strategy is laid down<br />

In order to determine a strategy for the network management and the system<br />

management, you must first analyse the requirements. Without determining<br />

the requirements of the management (for example: Which manageable<br />

network switching elements exist? How often is the software to be updated?),<br />

it is not possible to formulate demands of the management strategy. As the<br />

management strategy also has an impact on the software to be purchased, this<br />

can lead to wrong decisions.<br />

If, for example, a management product is introduced whose range of functions<br />

is too restricted, this can also cause problems in security, as the necessary<br />

function has to be provided "manually". In large systems, this can easily lead<br />

to errors in the configuration.<br />

Purchasing unmanageable components<br />

If a computer network is administered with the help of a network management<br />

system and/or a system management system, you must ensure that new<br />

components can be integrated into the relevant management system so that<br />

they can be included in the management. If this is not the case, you will need<br />

additional time for administration, if nothing else, as the management strategy<br />

that was laid down must be enforced for the components which are not<br />

administered with the management system. However, as these components are<br />

in particular not integrated in the automatic administrative processes of the<br />

management systems, errors can occur in the configuration . This can lead to a<br />

security risk through uncoordinated configurations.<br />

Uncoordinated management of related areas (communities, domains)<br />

If a computer network administered by a management system contains several<br />

administrative areas which are each looked after by their own system manager,<br />

then the management strategy must define their competence unambiguously.<br />

Otherwise, uncoordinated management of individual components can cause<br />

security problems.<br />

On the one hand, for example, if individual components such as network<br />

switching elements are wrongly managed by two administrative areas (this can<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!