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

that concern the network and system administrators and finally Tier 5 with matters that concern<br />

those responsible for or who will run the <strong>IT</strong> applications.<br />

- Breaking down the security aspects into tiers enables individual subject areas within the ensuing <strong>IT</strong><br />

security concepts to be updated and expanded more easily, without having a significant effect on<br />

other tiers.<br />

<strong>IT</strong> baseline protection modelling entails determining for the modules of a given tier whether and how<br />

they can be used to map the <strong>IT</strong> assets. Depending on the module considered, the objects which are<br />

mapped in this way may be of different kinds: individual components, groups of components,<br />

buildings, property, organisational units etc. If the target object is a group, then representative samples<br />

should be selected from it, and the relevant module should then be applied to those samples.<br />

<strong>The</strong> <strong>IT</strong> baseline protection model, i.e. the assignment of modules to target objects, should be<br />

documented in the form of a table containing the following columns:<br />

- Number and title of the module.<br />

- Target object or target group. For example, this could be the identification number of a component<br />

or a group or the name of a building or organisational unit.<br />

- Sample. If the target object is a group, then the number and names of the samples taken from this<br />

group should be noted.<br />

- Contact person. This column serves initially only as a place holder. <strong>The</strong> contact person is not<br />

determined at the modelling stage, but only at the point when the target versus actual comparison in<br />

the basic security check is being planned.<br />

- NB incidental information and the reasoning behind the modelling can be documented in this<br />

column.<br />

<strong>The</strong> procedure for modelling a set of <strong>IT</strong> assets is described in detail in Section 2.3.1 below. Particular<br />

importance here is attached to any constraints which apply, when it is appropriate to use a given<br />

module and to which target objects it should be applied. Section 2.3.2 presents a shortened modelling<br />

procedure for the special case of a single <strong>IT</strong> system or a single group.<br />

_________________________________________________________________________________________<br />

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

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

Saved successfully!

Ooh no, something went wrong!