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.

<strong>IT</strong> <strong>Baseline</strong> <strong>Protection</strong> of Generic Components Handling of security incidents<br />

_________________________________________________________________________________________<br />

3.8 Handling of security incidents<br />

Description<br />

To maintain <strong>IT</strong> security in ongoing operations, it is necessary<br />

to have developed and practised a policy for the handling of<br />

security incidents. A security incident refers to an event<br />

whose impact could cause significant loss or damage. To<br />

prevent or contain any loss or damage, security incidents<br />

should be dealt with swiftly and efficiently. If there is a<br />

predefined procedure available to be invoked, then reaction<br />

times can be minimised. <strong>The</strong> possible loss or damage which could occur in a security incident can<br />

affect both the confidentiality and integrity of data and also its availability.<br />

A special part of security incident handling is the contingency planning concept (see Section 3.3). In a<br />

contingency planning concept, the effects of failure of critical components in particular <strong>IT</strong> systems are<br />

analysed in advance and a procedure for ensuring that availability is maintained or can be restored is<br />

specified.<br />

Security incidents can, for example, be triggered by<br />

- user errors which result in loss of data or alteration of sensitive system parameters,<br />

- the appearance of security loopholes in hardware or software components,<br />

- large-scale infection by computer viruses,<br />

- hacking of Internet servers,<br />

- disclosure of confidential data,<br />

- loss of personnel resources or<br />

- criminal action (break-in, theft or blackmail relating to <strong>IT</strong> equipment).<br />

All types of security incident must be tackled in an appropriate manner. This applies both to security<br />

incidents against which it is possible to take specific protective measures, e.g. computer viruses, and<br />

also to security incidents which affect the organisation unexpectedly.<br />

This chapter presents a systematic approach as to how to draw up a policy for the handling of security<br />

incidents and how to ensure that this is implemented and integrated within an organisation. <strong>The</strong> effort<br />

involved in preparing and implementing such a policy is not trivial. <strong>The</strong>refore this chapter should be<br />

considered mainly where relatively large <strong>IT</strong> systems are used and/or for systems on which the<br />

organisation is especially reliant.<br />

Threat Scenario<br />

Security incidents can be triggered by a number of threats. <strong>The</strong> catalogue of threats contains a large<br />

collection of threats which can cause major or minor security incidents.<br />

A great deal of damage can be triggered by these threats if no suitable procedures have been<br />

developed as to how to handle them. This chapter therefore considers the following threat as<br />

representative of all the threats which can occur in the field of security incidents:<br />

- T 2.62 Inappropriate handling of security incidents<br />

_________________________________________________________________________________________<br />

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

Sicherheitsvorfälle:<br />

Feuer<br />

- Meldewege<br />

- Verhaltensmaßnahmen

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

Saved successfully!

Ooh no, something went wrong!