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.

Safeguard Catalogue - Organisation Remarks<br />

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

- seeking decisions from the responsible line manager (up to Management<br />

level).<br />

In every case of a discrepancy between actual practice and what was planned a<br />

corrective action should be suggested. <strong>The</strong> person who will be responsible for<br />

implementing the control measure and the date by which it is to be<br />

implemented should also be established.<br />

<strong>The</strong> <strong>IT</strong> security audit also includes a check as to whether log files and filter<br />

settings have been evaluated and monitored where necessary.<br />

<strong>The</strong> purpose of an update check is to establish<br />

- whether the <strong>IT</strong> security measures are still adequate to achieve the <strong>IT</strong><br />

security objectives,<br />

- whether the <strong>IT</strong> security measures are still sufficient to reduce the risk,<br />

- whether the <strong>IT</strong> security objectives are still relevant.<br />

It could transpire as a result of this update check, for example, that so many<br />

changes have taken place that the <strong>IT</strong> security measures no longer provide<br />

protection against current risks, the <strong>IT</strong> security process does not run in an<br />

optimal fashion or mistakes are being made in <strong>IT</strong> security management. In all<br />

three cases the reasons for the security loopholes should be established.<br />

Depending on the cause, possible corrective actions could include:<br />

- changes in <strong>IT</strong> security management,<br />

- adaptation of the <strong>IT</strong> security process<br />

- identification of new threats,<br />

- use of new technology (<strong>IT</strong> systems and applications),<br />

- use of new <strong>IT</strong> security technologies,<br />

- changes in the <strong>IT</strong> security measures<br />

- action in response to new laws and statutory instruments or amendments to<br />

these, and<br />

- action in response to changes in the latest version of the <strong>IT</strong> <strong>Baseline</strong><br />

<strong>Protection</strong> <strong>Manual</strong>.<br />

A corrective action should be suggested for every instance of a security<br />

weakness. Moreover, the person responsible for directing and monitoring the<br />

corrective measures should be established or, if appropriate, the additional risk<br />

could be considered to be acceptable.<br />

<strong>The</strong> update check also includes examining whether changes of every kind<br />

have - where necessary - met with an adequate response<br />

<strong>The</strong> points listed below regarding performance of the review apply to both<br />

types of review, both the <strong>IT</strong> security audit and the update check.<br />

<strong>The</strong> scope and depth of the review should be determined with reference to the<br />

purpose of the review. <strong>The</strong> <strong>IT</strong> security concept and the existing documentation<br />

of the <strong>IT</strong> security process serve as the basis for the review. <strong>The</strong> review, which<br />

can be performed either in-house or by external consultants, must be planned<br />

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

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

Procedure<br />

Planning

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

Saved successfully!

Ooh no, something went wrong!