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

2.2 Error handling<br />

- Is the security of RAS connections also assured after a critical<br />

failure or error (e.g. by preventing any further connections<br />

after abnormal termination)?<br />

- Can the system behaviour be reconfigured after a critical<br />

failure or error? For example, is it possible to configure the<br />

system so that after a critical error it is automatically rebooted<br />

or the Administrator is informed?<br />

2.3 Administration<br />

- Does the documentation delivered with the product contain a<br />

full description of all the technical and administrative details?<br />

- Can the administrative functions be accessed via a graphical<br />

user interface which is intuitive to use? Are the administrative<br />

functions designed so that attention is drawn to any incorrect,<br />

insecure or inconsistent configurations settings or these are<br />

prevented?<br />

- Do the administrative functions permit both command line<br />

data input and entry via a graphical user interface?<br />

- Is access to the administrative functions protected through<br />

adequate access control, e.g. using password entry,<br />

2.4<br />

implementation of a role concept (Administrator, Internal<br />

Auditor), two-person rule?<br />

Logging<br />

- Does the product offer logging facilities?<br />

- Is it possible to configure the amount of detail logged? Is all<br />

the relevant data captured by the logging?<br />

- Do the logging facilities allow data to be captured in different<br />

categories (e.g. by connection, user, protocol, service)?<br />

- Are there constraints on who may access the logged data?<br />

- Does the product allow the logged data to be stored not only<br />

locally but also on remote computers (central logging)? Are<br />

different data transmission methods offered for remote<br />

storage, so that external logging systems can also be used (e.g.<br />

syslog)? Can the logged data be transmitted securely?<br />

- Does the product offer a component enabling analysis of the<br />

logged data?<br />

- Is the logging mechanism compatible with the system<br />

management system used (transmission format, transmission<br />

protocol)?<br />

- Does the product offer facilities enabling the administrator to<br />

be informed or suitable protective measures (rejecting the<br />

RAS client, blocking of user accounts) to be automatically<br />

implemented in the event of certain predefined events<br />

occurring (e.g. denial of access, several successive<br />

-<br />

unsuccessful attempts at authentication)?<br />

Can logging be performed in such a way that the data privacy<br />

protection regulations can be satisfied?<br />

2.5 Communication and data transmission<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!