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

S 2.182 Regular revision of <strong>IT</strong> security measures<br />

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

Implementation responsibility: Head of <strong>IT</strong> Section, <strong>IT</strong> Security Management<br />

In the <strong>IT</strong> <strong>Baseline</strong> <strong>Protection</strong> <strong>Manual</strong> a number of procedures are presented<br />

which are necessary if the desired level of <strong>IT</strong> security is to be achieved.<br />

However, it is not sufficient simply to make these procedures known, but it is<br />

also necessary to monitor adherence to them on a regular basis. However, in<br />

this context "regular" does not mean that revisions takes place at times which<br />

are predictable, as pre-announced checks generally produce a distorted picture<br />

of the object under investigation.<br />

Revisions should be geared towards remedying defects. If revisions are to be<br />

accepted, it is important that this is recognised by all those involved as the<br />

objective of the revision and that staff do not feel they are being treated like<br />

schoolchildren. It is therefore a good idea to discuss possible solutions to<br />

problems with participants during a check and to pre-prepare appropriate<br />

remedies.<br />

When employees ignore or circumvent a procedure, this is generally a sign<br />

that the procedure cannot be reconciled with work routines or that it is not<br />

possible for staff to implement it. For example, an instruction not to leave<br />

confidential material unattended on the printer is inappropriate if the only<br />

resource available for printing is a network printer some distance away.<br />

If shortcomings are identified during security revisions, the aim should be not<br />

simply to remove the symptoms. It is far more important to determine the<br />

causes of these problems and to identify solutions. <strong>The</strong>se could, for example,<br />

involve changes to existing procedures or taking additional technical<br />

measures.<br />

Revisions should help to remove the sources of errors. It is extremely<br />

important if revisions are to be accepted by staff that it does not result in any<br />

individuals being exposed or identified as "guilty". When employees live in<br />

fear of being exposed in this way, there is a danger that they will not be frank<br />

in reporting weaknesses and security shortcomings they are aware of but that<br />

they will instead attempt to hush up existing problems.<br />

Additional controls:<br />

- Are all procedures and <strong>IT</strong> security measures reviewed to ensure that they<br />

are implementable?<br />

- How often are checks carried out to ensure that existing procedures and <strong>IT</strong><br />

security measures are adhered to?<br />

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

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

Unannounced revisions<br />

Tailor procedures to<br />

work routines<br />

Remove causes of<br />

security shortcomings<br />

Avoid assigning blame

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

Saved successfully!

Ooh no, something went wrong!