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

regulations. <strong>The</strong> procurer must also ensure that the other bodies whose<br />

stipulations must be adhered to, such as the Data Privacy Officer, the <strong>IT</strong><br />

Security Officer or the Staff / Works Council, are involved in good time.<br />

It must be decided how many and which candidates on the list should be<br />

tested. For obvious reasons the first two or three product leaders should be<br />

selected and tested as to whether they actually fulfil the most important<br />

criteria of the Requirements Catalogue. This is particularly important with<br />

regard to the necessary requirements. Test licences should be obtained and<br />

tests carried out as described in S 2.82 Developing a test plan for Standard<br />

Software and S 2.83 Testing Standard Software.<br />

Besides to the criteria of the Requirements Catalogue, the decision can be<br />

based on the following points:<br />

- References<br />

If the manufacturer or distributor can provide reference installations for his<br />

product, the experience of this user can be included in the assessment of<br />

the product.<br />

In the event that external test results or quality assurances are available for<br />

the software product (e.g. test results in journals, conformity tests<br />

according to accepted standards, tests and certificates according to relevant<br />

standards and norms, such as ISO 12119), these results should be taken<br />

into consideration during the preselection process.<br />

- Product popularity<br />

In the event that the product is widely spread, the individual user has little<br />

or no influence on the product manufacturer as far as troubleshooting or the<br />

implementation of certain functions is concerned. He can assume, however,<br />

that the product is further developed. <strong>The</strong>re are often external tests carried<br />

out by journals or commissioned by the manufacturer. With popular<br />

products, weaknesses are generally more widely known which means that<br />

the user can assume that most weaknesses are already known and that the<br />

knowledge concerning weaknesses and remedies is distributed quickly, i.e.<br />

he can obtain help.<br />

In case of a low degree of popularity, a user can have more influence on<br />

the manufacturer. External tests are generally not available as these are too<br />

expensive and time-consuming for products from small manufacturers.<br />

Products with a low degree of popularity do not usually contain more<br />

errors than those which are widely spread. <strong>The</strong> disadvantage is that these<br />

errors are often not detected as quickly, thus allowing swift elimination. If<br />

security breaches are involved, however, these are probably not known to<br />

potential attackers or they are not worthwhile targets.<br />

- Cost-effectiveness / costs for purchase, operation, maintenance and<br />

training<br />

Before the decision to purchase a certain product is taken, the following<br />

question should always be asked: Is the cost of the product proportionate to<br />

the benefits of the product? In addition to the initial purchase costs, the<br />

costs for operation, maintenance and training should be considered. It<br />

should be clarified, for example, whether the existing hardware platform<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!