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

S 2.199 Maintenance of <strong>IT</strong> security<br />

Initiation responsibility: <strong>IT</strong> Security Management Team<br />

Implementation responsibility: <strong>IT</strong> Security Officer<br />

In the <strong>IT</strong> security process what is important is not simply to achieve the<br />

aspired-to level of <strong>IT</strong> security, but to ensure that it is maintained in the long<br />

term. To maintain and continuously improve the existing level of <strong>IT</strong> security,<br />

all <strong>IT</strong> security measures should be regularly reviewed.<br />

<strong>The</strong>se reviews should be performed at predetermined times (at least every two<br />

years) and, if warranted by particular events, they can also be held in the<br />

interim. In particular, information gained from security-relevant incidents,<br />

changes in the technical or organisational environment, changes in security<br />

requirements or threats require that existing <strong>IT</strong> security measures are adapted.<br />

<strong>The</strong> outcomes of individual reviews should be documented and the question of<br />

how to proceed with the results of the review must be determined. It should be<br />

stressed here that reviews can only maintain <strong>IT</strong> security effectively if the<br />

results of these reviews are also translated into the necessary corrective<br />

actions.<br />

It should be determined in advance in the agency/company how the activities<br />

relating to these reviews are to be co-ordinated. Which <strong>IT</strong> security measures<br />

are to be reviewed, when and by whom must be determined. This will avoid<br />

duplication of effort and also ensure that all parts of the organisation are<br />

covered.<br />

A review can establish firstly whether the <strong>IT</strong> security measures are working<br />

properly at all levels on a day-to-day basis. At the same time, the extent to<br />

which the <strong>IT</strong> security measures are suited to the security requirements and are<br />

effective at protecting the organisation from threats can also be established<br />

from a review. Two types of review should be distinguished here, the <strong>IT</strong><br />

security audit and the update check.<br />

<strong>The</strong> purpose of an <strong>IT</strong> security audit is to establish<br />

- whether the <strong>IT</strong> security measures implemented agree with those<br />

documented and<br />

- whether the <strong>IT</strong> security measures function in the manner intended.<br />

This comparison of the actual versus planned situation might reveal, for<br />

example, that some <strong>IT</strong> security measures have not been implemented or that<br />

they are not producing the results intended in practice. In both cases the<br />

reasons for the discrepancy should be established. Depending on the cause,<br />

possible corrective actions could include:<br />

- adapting organisational measures,<br />

- taking staff-related measures, e.g. further training or measures aimed at<br />

promoting <strong>IT</strong> security awareness, or instituting disciplinary measures,<br />

- infrastructure measures, e.g. initiating structural changes in the building,<br />

- taking technical measures, e.g. changes to the hardware and software or<br />

communications links and networks,<br />

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

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

Regular and eventtriggered<br />

checks<br />

Co-ordinated approach<br />

Audit and update

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

Saved successfully!

Ooh no, something went wrong!