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.

Safeguard Catalogue - Communications Remarks<br />

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

S 6.54 Procedures in case of a loss of network<br />

integrity<br />

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

Implementation responsibility: Administrator, <strong>IT</strong> users<br />

If the network acts unexpectedly (for example, servers are not available,<br />

access to network resources is not possible, or network performance is<br />

consistently poor), a loss of network integrity could have occurred. This could<br />

be due to misuse of the network, e.g. due to changes in the configuration of<br />

the active network components or damage to them.<br />

Users should observe the following procedure in this case:<br />

- Working documents should be saved and any programs still running should<br />

be closed down.<br />

- <strong>The</strong> Administrator must be informed via an appropriate escalation stage<br />

(e.g. User Help Desk). <strong>The</strong> reporting procedure should not be allowed to<br />

significantly hinder the Administrator's activities.<br />

<strong>The</strong> Network Administrator should observe the following procedure:<br />

- Narrow the faulty response down to a network segment or network<br />

component.<br />

- Check the configuration of the active network components present there<br />

(this also includes password checks).<br />

- Back up all files which could provide information on the nature and cause<br />

of the problem (for example, whether an intrusion has taken place, and if<br />

so, how penetration was effected), i.e. it is especially important to back up<br />

all the relevant log files.<br />

- If necessary, restore the original configuration data (refer to S 6.52 Regular<br />

backup of configuration data of active network components).<br />

- If necessary, check the hardware in use (cabling, plug connectors, active<br />

network components etc.) for faults.<br />

- Request all users to check their working domains for irregularities.<br />

If there are signs of a deliberate attack on the network, it is essential to act<br />

immediately in order to minimise the damage and prevent further damage<br />

from occurring. This requires that there is an alarm plan which lists the steps<br />

to be implemented and specifies who should be informed of the incident (see<br />

also S 6.60 Procedural rules and reporting channels for security incidents).<br />

<strong>The</strong> alarm plan should also specify whether and how the Data Privacy Officer<br />

and the legal department should be involved.<br />

Additional controls:<br />

- What steps have been taken to ensure to ensure that the Administrator is<br />

properly informed?<br />

- Are these procedures actually followed?<br />

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

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

Misuse<br />

Notify Administrator<br />

Back up log files<br />

Implement alarm plan

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

Saved successfully!

Ooh no, something went wrong!