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 - Communications Remarks<br />

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

S 6.65 Notification of the parties affected<br />

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

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

Administrator, Press Office<br />

When a security incident has occurred, all the internal and external parties<br />

affected by it must be informed. This is especially important for departments<br />

or agencies which could sustain damage as a direct result of the security<br />

incident and need to take countermeasures or for any parties which process<br />

information about security incidents and can assist in preventing or resolving<br />

them. If necessary, the public should also be informed, especially if<br />

information has already leaked out.<br />

A clear concept of who should inform whom, in what sequence and in how<br />

much detail must be developed for the particular security incident concerned.<br />

In this connection steps must be taken to ensure that information regarding the<br />

security incident is only given out by appointed responsible persons, such as,<br />

for example <strong>IT</strong> Security Management or the Press Office.<br />

Who receives information and in how much detail naturally will depend<br />

primarily on the technical background. No incorrect or embellished<br />

information should be passed on, as this could lead to confusion, false<br />

assessments and loss of image.<br />

An example is presented below of which departments/agencies should<br />

typically be informed of what information.<br />

Internal departments<br />

If it is still unclear as to whether a security incident has occurred or how<br />

serious it is, the internal staff potentially affected should be asked to examine<br />

their areas of work for possible irregularities.<br />

If the countermeasures required to deal with a security incident are known, the<br />

internal departments concerned should be informed promptly as to what they<br />

must do in order to minimise the effects of a security incident or to restore<br />

secure operations.<br />

<strong>The</strong> parties who should be considered include the following:<br />

- Head of <strong>IT</strong> Section<br />

- heads of specialist departments concerned,<br />

- <strong>IT</strong> users,<br />

- <strong>IT</strong> Administrators,<br />

- <strong>IT</strong> user service,<br />

- site technical service<br />

- surveillance staff,<br />

- internal security staff and<br />

- entrance control staff.<br />

External parties<br />

If the impact of the security incident is not confined simply to the<br />

organisation, all external parties which are also affected or could also be<br />

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

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

Who informs whom?<br />

No glossing over!

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

Saved successfully!

Ooh no, something went wrong!