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

Step 4: Determine implementation sequence<br />

If the existing budget or staffing resources are not sufficient to be able to implement all the missing<br />

safeguards immediately, the sequence in which these measures will be implemented must be<br />

determined. When determining the sequence, the following aspects should be considered:<br />

- <strong>The</strong> priority of a safeguard should be viewed as a guide to the order in which it should be<br />

implemented. Safeguards which have been assigned a priority 1 should be implemented first.<br />

- With some safeguards a time sequence is suggested naturally by the logical inter-relationship of the<br />

measures concerned. Thus, for example, safeguards S 2.25 Documentation of the System<br />

Configuration and S 2.26 Appointment of an Administrator and his Deputy are both important, but<br />

without an Administrator it is not practical to implement S 2.25.<br />

- Many of the safeguards have a significant effect in broad areas, whereas others have only a limited,<br />

local effect. Often it is advisable to start with the safeguards which have a broad effect.<br />

- Some modules have a bigger impact on the aspired-to security level than others. Safeguards<br />

contained in such modules should be given preference, especially where their implementation will<br />

result in the elimination of weaknesses in areas having a high protection requirement. Thus, for<br />

example, the server should always be protected first (e.g. through implementation of module 6.2<br />

UNIX Server) and only then the clients that are connected to it.<br />

- Modules in respect of which there is a particularly large number of missing safeguards represent<br />

areas in which security is particularly weak. Preference should likewise be given to these.<br />

Step 5: Assign responsibilities<br />

Once the sequence in which the safeguards will be implemented has been determined, it is then<br />

necessary to specify who is responsible for implementing which safeguards and by when. Unless this<br />

is done, experience indicates that implementation of safeguards tends to be delayed and in some cases<br />

never takes place. Care must be taken here to ensure that the person to whom responsibility is assigned<br />

possesses the skills and authority necessary to implement the safeguards and that the resources he<br />

needs are made available to him.<br />

Similarly, someone must be allocated responsibility for overseeing implementation. This person must<br />

also be notified when implementation of individual safeguards has been completed. Typically it is the<br />

<strong>IT</strong> Security Officer who is notified. Progress in the matter of implementation should be checked at<br />

regular intervals to ensure that the implementation work does not drag on.<br />

<strong>The</strong> implementation plan which should now be complete should contain the following information as a<br />

minimum:<br />

- description of the target operational environment<br />

- number of module to be considered<br />

- names and description of the safeguards<br />

- implementation schedule<br />

- budgetary framework<br />

- person responsible for implementation<br />

- person responsible for overseeing implementation<br />

Step 6: Measures to accompany implementation<br />

It is also important to specify any measures which need to take place in parallel to implementation and<br />

to plan them into the implementation. In particular, such measures include measures designed to<br />

inform members of staff who will be affected by the new <strong>IT</strong> security measures of their necessity and<br />

consequences and to make them aware of the importance of <strong>IT</strong> security.<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!