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 />

- Which <strong>IT</strong> systems and <strong>IT</strong> applications will definitely not suffer any<br />

damage or consequential damage?<br />

- How high could any direct damage or consequential damage caused by the<br />

security incident be? Particular attention should be paid here to the<br />

dependence of the various <strong>IT</strong> systems and <strong>IT</strong> applications.<br />

- What was the trigger for the security incident (e.g. carelessness, an<br />

adversary or failure of the infrastructure)?<br />

- When and in which location did the security incident occur? This could<br />

actually be some time prior to when the security incident was first detected.<br />

Well maintained log files can be extremely useful here, but only if one can<br />

be sure that they have not been tampered with.<br />

- Are only internal <strong>IT</strong> users affected by the security incident, or are external<br />

third parties affected also?<br />

- How much information regarding the security incident has already leaked<br />

out to the public?<br />

If it transpires that the security incident could have serious consequences then<br />

it should be escalated to at least the next level.<br />

Once these factors have been clarified, the options available must be specified.<br />

<strong>The</strong>se will consist of both immediate measures and supplementary measures.<br />

<strong>The</strong> previously determined assignment of priorities should be considered here<br />

(see S 6.62 Specifying priorities for handling security incidents). <strong>The</strong> time that<br />

will be required to implement these measures and the cost and resources<br />

which will be necessary to resolve the problem and restore normal operating<br />

conditions must also be estimated.<br />

If the level of the damage, the time required to repair the situation and the cost<br />

of this exceed predefined limits, then the next higher escalation and decision<br />

levels must be called in before any decisions are made as to which measures<br />

should be selected. <strong>The</strong> outcome of a structured investigation and assessment<br />

of a security incident on the lines outlined above will be the various options<br />

available.<br />

Additional controls:<br />

- Is the necessary information generated from the definition of protection<br />

requirements available to the persons receiving reports of security incidents<br />

and the next escalation levels?<br />

- Are any technical means available to support the evaluation of security<br />

incidents, for example, tools for analysing logged data?<br />

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

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

Consult log data<br />

Determine actions

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

Saved successfully!

Ooh no, something went wrong!