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.158 Reporting computer virus infections<br />

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

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

When a computer virus infects a system, the priority is to prevent other <strong>IT</strong><br />

systems from becoming infected. To this end, a contact person should be<br />

appointed at the institution, to whom a computer virus infection must be<br />

reported without delay. On the basis of the documents produced in accordance<br />

with S 2.155 Identification of <strong>IT</strong> systems potentially threatened by computer<br />

viruses, this person can immediately decide which users need to be informed<br />

about the occurrence of a computer virus as appropriate. <strong>The</strong>se alerting routes<br />

must also be established within the framework of the reporting system.<br />

In addition to the institution’s own staff, all externals who may be affected by<br />

the virus infection must also be informed. <strong>The</strong>se include in particular those<br />

people who it is presumed have forwarded or received the virus.<br />

To obtain an overview of the current threat posed by computer viruses, the<br />

BSI maintains a set of statistics about all virus infections that have occurred.<br />

For this purpose, a virus reporting sheet was issued on which a virus incident<br />

should be recorded. <strong>The</strong> virus report is used by the BSI for statistical purposes<br />

only; it can also be submitted anonymously (a preprinted form is provided in<br />

the appendix).<br />

<strong>The</strong> appointed contacts are then finally also the people via whom the measures<br />

leading to elimination of the detected computer virus infection are to be<br />

initiated. <strong>The</strong>se should document all infections with computer viruses, their<br />

effects and their elimination. This information forms a basis for updating the<br />

virus protection concept, and provides a record of incidences of damage that<br />

have occurred and of the effort and expense of correction.<br />

In order to set up the reporting system, it is necessary for the contact person to<br />

be made known to all staff in an appropriate form. This may take the form of a<br />

leaflet, for example (cf. S 6.23 Procedures in the event of computer virus<br />

infection). Especially when there is a hoax (see T 5.80 Hoaxes) it is important<br />

that users forward these supposed security instructions only to the contact<br />

person appointed to deal with virus problems, and do not spread them further.<br />

In the same way, the contacts must regularly keep themselves informed of any<br />

new computer viruses that appear so that they can arrange for the computer<br />

virus scanning programs to be updated or those users affected to be alerted, as<br />

the need arises.<br />

Additional controls:<br />

- Has it been ensured that the contact person for computer virus infections is<br />

known to all <strong>IT</strong> users?<br />

- Has it been ensured that the contact person can alert all those potentially<br />

affected by an acute computer virus infection as quickly as possible?<br />

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

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

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

Saved successfully!

Ooh no, something went wrong!