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

carefully. During the review all relevant information captured should be<br />

documented and evaluated.<br />

<strong>The</strong> results should be documented in an <strong>IT</strong> security report. This should<br />

contain a technical description of the corrective actions proposed. <strong>The</strong> <strong>IT</strong><br />

security report, which may contain confidential information and therefore<br />

need to be protected, should be presented to the <strong>IT</strong> Security Officer (assuming<br />

that he did not perform the review himself) and be notified to the manager of<br />

the division or department reviewed as well as to the <strong>IT</strong> Security Management<br />

Team. Where serious problems exist, Management should be involved so that<br />

any far-reaching decisions can be made promptly. For this purpose, a<br />

management report on <strong>IT</strong> security should be prepared, as described in S 2.200<br />

Preparation of management reports on <strong>IT</strong> security.<br />

On the basis of the results of the review, decisions must be made as to where<br />

to proceed from here; in particular all the corrective actions which are<br />

necessary must be determined and specified in the form of an implementation<br />

plan. Responsibilities for implementation of the corrective actions, which are<br />

carried out in a similar fashion to the procedure described in S 2.196<br />

Implementation of the <strong>IT</strong> security concept in accordance with an<br />

implementation plan, must be assigned and the persons concerned provided<br />

with the necessary resources.<br />

In summary, it may be said that a given level of <strong>IT</strong> security can only be<br />

maintained if<br />

- maintenance of <strong>IT</strong> security in ongoing operations is facilitated by<br />

appropriate organisational rules;<br />

- responsibility for maintenance of <strong>IT</strong> security has been clearly assigned;<br />

- measures are implemented in their entirety as described;<br />

- measures are checked regularly to see if they are functioning as intended;<br />

- measures are properly applied and adhered to and are accepted;<br />

- measures are adapted if any new vulnerabilities come to light;<br />

- measures are adjusted in line with changes in personnel, organisation,<br />

hardware or software.<br />

- changes in tasks or the importance of tasks to the organisation are taken<br />

into account;<br />

- changes to buildings, e.g. after moving premises, are taken into account;<br />

- modifications are implemented in response to changes in threats and/or<br />

vulnerabilities.<br />

All these changes have a significant effect on the security risks. New security<br />

risks should be identified at the earliest possible opportunity in order to permit<br />

a timely response. Should it transpire that the actual risk differs from the<br />

actual risk accepted in the <strong>IT</strong> security concept, resources should be made<br />

available to change this situation.<br />

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

<strong>IT</strong>-<strong>Baseline</strong> <strong>Protection</strong> <strong>Manual</strong>: Oktober 2000<br />

<strong>IT</strong> security report<br />

Corrective actions<br />

New security risks

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

Saved successfully!

Ooh no, something went wrong!