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

_________________________________________________________________________________________<br />

requirement. <strong>The</strong> values decided on should be documented in the security concept in an appropriate<br />

manner.<br />

Step 2: consider of damage scenarios<br />

Starting from the assumption that a loss of confidentiality, integrity or availability of an <strong>IT</strong> application<br />

or the related information occurs, the maximum damage and consequential damage are considered. On<br />

the basis of the question<br />

"What if ... ?"<br />

realistic damage scenarios are developed from the user's point of view and the expected material or<br />

non-material damage is described. <strong>The</strong> extent of this possible damage ultimately determines the<br />

protection requirements of the <strong>IT</strong> application. <strong>The</strong> persons responsible for the <strong>IT</strong> applications under<br />

consideration and their users must be asked for their personal opinions. <strong>The</strong>y will normally have a<br />

good idea of what damage could occur and should be able to provide a useful input into the data<br />

collected.<br />

To simplify calculation of the possible damage, a set of questions is presented below for each of the<br />

damage scenarios mentioned, as a tool for drawing out the possible effects. <strong>The</strong>se suggestions do not<br />

claim to be complete; they are merely intended as a guide. In every case it is necessary to consider the<br />

specific work and the situation of the agency/company, and the questions provided in this manual must<br />

be supplemented accordingly.<br />

Working through the damage scenarios listed below, including the related questions, is recommended<br />

for each of the <strong>IT</strong> applications recorded. Once this has been done, the tables above should be used to<br />

determine the protection requirement with regard to confidentiality, integrity and availability by<br />

assigning each <strong>IT</strong> application to a protection requirement category.<br />

Damage scenario „Violation of laws, regulations or contracts“<br />

Such violations can result from the loss of confidentiality, integrity or availability. <strong>The</strong> severity of the<br />

ensuing damage will often depend on the specific legal implications for this agency/company.<br />

Examples of relevant German legislation are:<br />

<strong>The</strong> Constitution, the Civil Code, the German Penal Code, the Federal Data Privacy Act and the<br />

data privacy legislation of the individual Länder, the Social Security Code, the German<br />

Commercial Code, the Staff Representation Act, the Employees’ Representation Act, the Copyright<br />

Act, the Patents Act, the <strong>Information</strong> and Communication Services Act (IuKDG), the Control and<br />

Transparency in Business Act (KonTraG).<br />

Examples of relevant regulations are:<br />

Administrative regulations, ordinances, and service regulations.<br />

Examples of contracts:<br />

Service contracts in the area of data processing, contracts for the safeguarding of<br />

business/industrial secrets.<br />

Questions:<br />

Loss of confidentiality<br />

Is confidentiality of the data required by law?<br />

_________________________________________________________________________________________<br />

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

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

Saved successfully!

Ooh no, something went wrong!