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

organisational processes or undermine other security measures. In such cases it could be necessary to<br />

replace certain <strong>IT</strong> baseline protection safeguards by adequate alternative <strong>IT</strong> security safeguards.<br />

In order subsequently to be able to trace the procedure followed in drawing up and refining the list of<br />

specific measures, this should be suitably documented.<br />

Examples:<br />

- It was established during a supplementary security analysis that in addition to the <strong>IT</strong> baseline<br />

protection safeguards it is also necessary to implement smart card-supported authentication and<br />

local encryption of hard disks on NT clients used for processing HR data. <strong>The</strong>se additional<br />

measures would replace safeguard S 4.48 Password <strong>Protection</strong> under Windows NT.<br />

- It has been established in the basic security check that safeguard S 1.24 Avoidance of Water Pipes<br />

has not been implemented and due to structural considerations would not be cost-effective to<br />

implement. As an alternative, metal sheets allowing water to be deflected are to be installed under<br />

the water-bearing pipes, and these will also be monitored by a water alarming device. An alarm<br />

will be sent to the porter so that in case of damage any leakage of water can be detected and<br />

contained quickly.<br />

Step 3: Prepare an estimate of the costs and effort required<br />

As the budget for implementing <strong>IT</strong> security measures is in practice always limited, it is necessary for<br />

every measure to be implemented to identify how much will need to be invested and how much labour<br />

this will entail. A distinction should be made here between one-off and recurring investment/labour<br />

costs. At this point it should be mentioned that experience shows that savings on technology often<br />

result in high ongoing labour costs.<br />

In this connection it is necessary to ascertain whether all the measures identified can be afforded. If<br />

there are any safeguards which cannot be funded, consideration should be given as to what alternative<br />

measures could be taken instead or whether the residual risk resulting from failure to implement a<br />

given measure is acceptable. This decision must likewise be documented.<br />

If the financial and staffing resources estimated as being necessary are available, then one can proceed<br />

to the next step. However, in many cases it is necessary to take a further decision as to the extent of<br />

the resources to be used to implement the <strong>IT</strong> security measures. It is recommended here that a<br />

presentation on the results of the security study should be given to the person(s) responsible for<br />

making such decisions (Management, <strong>IT</strong> Manager, <strong>IT</strong> Security Officer etc.). To make those<br />

responsible aware of the security issues involved, the security weaknesses identified (i.e. missing or<br />

only partially implemented <strong>IT</strong> security safeguards) should be presented by protection requirement. It is<br />

also recommended that the cost and effort associated with implementing the missing priority 1, 2 and<br />

3 safeguards should be presented. A decision regarding the budget should then be made following this<br />

presentation.<br />

If it proves to be not possible to make available a sufficient budget to cover implementation of all the<br />

missing safeguards, then the residual risk resulting from failure to implement or delay in implementing<br />

certain measures should be pointed out. To assist with this, the Safeguard-Threat Tables (see CD-<br />

ROM: word20\tabellen) can be used to ascertain which threats are no longer adequately covered. <strong>The</strong><br />

residual risk relating to any chance or wilful threats should be described clearly and presented to<br />

Management for decision. <strong>The</strong> remaining steps can only take place after Management has decided that<br />

the residual risk is acceptable, as Management must bear the responsibility for the consequences.<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!