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 - Organisation Remarks<br />

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

-<br />

For medium-sized systems, in particular, it makes sense to divide the<br />

system into management domains in accordance with the actual<br />

network topology (especially if there are no differences in areas of<br />

responsibility, for example).<br />

Organisational responsibilities within the company or agency<br />

<strong>The</strong> organisational structure can be emulated by the management<br />

system, giving rise to domains such as "Accounting",<br />

-<br />

"Programming", "Production Division" or "Software Development<br />

Division", for example.<br />

Security-related factors which have an effect on management policy<br />

can also result in the creation of multiple management regions. This<br />

is the case in particular when management tasks for certain<br />

organisational units need to be delegated, without the local<br />

administrator being given access rights to the management functions<br />

for the components outside his or her sphere of responsibility.<br />

Existing infrastructure<br />

Examples of factors to be examined include the geographical<br />

distribution of branches or the spatial distribution of work teams<br />

across the storeys of a building.<br />

- Safety considerations<br />

- Multiple management regions may be necessary if the<br />

management product supports different encryption<br />

-<br />

mechanisms for each region but normally only one<br />

mechanism can actually be used per region. If different<br />

mechanisms are indeed used between individual management<br />

components, multiple management regions are necessary.<br />

Example: <strong>The</strong> system being administered comprises several<br />

database servers with sensitive data and the associated clients,<br />

which do not store data themselves. <strong>The</strong> management console<br />

should always communicate with the servers using strong<br />

encryption, because the databases are also administered via<br />

the management system. Communication with the clients, on<br />

the other hand, should be only weakly encrypted, for<br />

performance reasons. In this case it is normally necessary to<br />

create two management regions: one region containing the<br />

servers and a second region containing the clients.<br />

Multiple management regions increase reliability, because for<br />

example in the event of the failure of one management region<br />

the other regions can continue to be administered<br />

independently of the failed region.<br />

- <strong>The</strong> number of computers to be administered per management<br />

region also has an influence. Most products give<br />

recommendations as to the number of computers that can be<br />

administered by the management server of one region. A<br />

figure of 200 computers per server is not unusual, however.<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!