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

In order that attainment of the aspired-to security level is not a one-off<br />

occurrence but is maintained in the long-term, the <strong>IT</strong> security measures<br />

implemented must also remain operable in ongoing operations. In perhaps no<br />

other area does a security level once established become so rapidly outdated as<br />

in the dynamic <strong>IT</strong> environment. In particular, lessons learned from securityrelevant<br />

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

changes in security requirements and the advent of new threats require that<br />

existing <strong>IT</strong> security measures are modified.<br />

Safeguard S 2.199 Maintenance of <strong>IT</strong> security contains detailed<br />

recommendations on how to ensure that these are properly updated.<br />

Often modifications of the <strong>IT</strong> security process require a decision from the<br />

uppermost echelons of management. To this end, Management must be<br />

informed as to the level of <strong>IT</strong> security achieved and of any existing problems<br />

and vulnerabilities. For this purpose an "<strong>IT</strong> Security" management report<br />

should be prepared at regular intervals.<br />

Safeguard S 2.200 Preparation of management reports on <strong>IT</strong> security contains<br />

advice on how to prepare and present such reports.<br />

To ensure the continuity and consistency of the entire <strong>IT</strong> security process, it is<br />

essential that the <strong>IT</strong> security process is documented. Only in this way can<br />

basic weaknesses in the process be reliably detected and any departures from<br />

course be nipped in the bud.<br />

Recommendations as to the content and scope of this documentation will be<br />

found in safeguard S 2.201 Documentation of the <strong>IT</strong> security process.<br />

Additional tools and aids regarding the <strong>IT</strong> security process are presented in<br />

safeguards S 2.202 Preparation of an <strong>IT</strong> Security Organisational <strong>Manual</strong> and<br />

M 2.203 Establishment of a pool of information on <strong>IT</strong> security.<br />

Readers who wish to gain a deeper understanding of the "<strong>IT</strong> security process"<br />

subject-matter are recommended to read Part 3 of ISO/IEC Standard 13335<br />

"Guidelines on the Management of <strong>IT</strong> Security".<br />

Additional controls:<br />

- Has an adequate <strong>IT</strong> security process being established?<br />

- Is Management sufficiently supportive of the <strong>IT</strong> security process?<br />

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

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

Further literature

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

Saved successfully!

Ooh no, something went wrong!