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

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

S 2.186 Selection of a suitable RAS product<br />

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

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

RAS products differ as to the range of functions provided, the security<br />

mechanisms offered, ease of operation and cost-effectiveness. Moreover there<br />

are differences in the hardware and software components in the operational<br />

environment which they require for smooth operation.<br />

Before a RAS product is purchased, a list of requirements against which the<br />

products available on the market can be evaluated should therefore be drawn<br />

up. An informed purchase decision which will ensure that the product<br />

purchased satisfies the requirements when put into operation can then be made<br />

on the basis of the evaluation.<br />

A RAS system generally consists of several hardware and software<br />

components so that, strictly speaking, one should not really talk about a RAS<br />

product as if it were a single entity. Initially a rough distinction can be made<br />

between LAN-side and client-side components. <strong>The</strong> specific components<br />

which have to be purchased depend on the chosen RAS system architecture.<br />

Thus, in the simplest case, for example, a Windows-based PC and a laptop,<br />

each of which is fitted with an ISDN card (see also S 2.106 Purchase of<br />

suitable ISDN cards), can function as RAS server and client and use the<br />

Windows NT Remote Access Service. On the other hand, large organisations<br />

often operate many RAS connections concurrently for different operational<br />

purposes. Solutions here generally require special <strong>IT</strong> systems (hardware and<br />

software) which are specifically designed for use as RAS servers.<br />

<strong>The</strong> list below provides a rough summary of the possible general evaluation<br />

criteria, but does not claim to be exhaustive and can be extended to include<br />

other general requirements. In addition to the criteria listed here, further<br />

specific requirements which result from the planned actual operational<br />

scenarios must be identified as part of the RAS requirements analysis (see<br />

safeguard S 2.183 Performing a RAS requirements analysis).<br />

1 General criteria<br />

1.1 Performance and scalability<br />

- Can the system satisfy the performance requirements?<br />

- Can transparent load balancing or data compression be<br />

configured for the system?<br />

- Can the system be designed in such a way that it can cope<br />

with future growth requirements (e.g. through modular system<br />

structure, simple integration of new RAS servers, no separate<br />

user administration for new RAS connections)?<br />

1.2 Maintainability<br />

- Is the product simple to maintain?<br />

- Does the vendor offer regular software updates?<br />

- It is possible to conclude maintenance contracts for the<br />

product?<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!