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.62 Specifying priorities for handling security<br />

incidents<br />

Initiation responsibility: Agency/company Management, <strong>IT</strong> Security<br />

Management<br />

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

Experience suggests that security incidents are the result of a conjunction of<br />

different causes. As a consequence it is generally the case that the resulting<br />

potential damage involves several categories of damage (for example,<br />

impairment of physical integrity of a person, negative effects on external<br />

relationships, financial consequences, see also Section 2.2, Determination of<br />

protection requirements). It is therefore important to establish as far in<br />

advance as possible exactly where priorities lie with regard to dealing with<br />

problems. This priority assignment determines among other things the<br />

sequence in which problems should be tackled.<br />

<strong>The</strong> assignment of priorities depends heavily on an organisation's particular<br />

circumstances. To assign priorities, the following questions should be<br />

considered:<br />

- What categories of damage are relevant to the organisation?<br />

- In what order should damage in the individual damage categories be<br />

rectified?<br />

In answering these questions, it can be helpful to work through a procedure for<br />

determining protection requirements from the <strong>IT</strong> baseline protection point of<br />

view (see Section 2.2). This procedure for determining protection<br />

requirements defines the damage categories which are relevant to the<br />

organisation.<br />

Examples of relevant damage categories are as follows:<br />

- Violation of laws, regulations or contracts<br />

- Impairment of the right to informational self-determination<br />

- Impairment of the physical integrity of a person<br />

- Impaired performance of duties<br />

- Negative effects on external relationships<br />

- Financial consequences<br />

As part of the exercise of specifying the protection requirements, the extent of<br />

the damage is defined for each damage category.<br />

Example: damage category "financial consequences"<br />

Damage category: financial consequences<br />

Damage / loss = medium Damage or loss is less than DM<br />

25,000<br />

Damage / loss = high Damage or loss is between DM<br />

25,000 and DM 5 million<br />

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

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

Security incidents<br />

compete with other<br />

problems<br />

How serious is the<br />

damage?

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

Saved successfully!

Ooh no, something went wrong!