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 - Hardware & Software Remarks<br />

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

S 4.112 Secure operation of the RAS system<br />

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

Implementation responsibility: Administrator<br />

For the secure operation of a RAS system it is essential that the hardware and<br />

software components of the system have been securely installed and<br />

configured. Safeguards S 4.110 Secure installation of the RAS system and<br />

S 4.111 Secure configuration of the RAS system must therefore have been<br />

performed before the RAS system goes live. In addition, all the organisational<br />

processes must have been defined and implemented (e.g. reporting channels<br />

and responsibilities). It should also be noted that the desired level of system<br />

security can only be assured if the physical security of the hardware<br />

components which make up the RAS system is also assured (see also S 4.110<br />

Secure installation of the RAS system).<br />

<strong>The</strong> security of a RAS system can be roughly broken down into three areas:<br />

1. the security of the RAS server,<br />

2. the security of the RAS client and<br />

3. the security of data transmission.<br />

Whereas the desired level of security of the RAS server can be controlled<br />

through implementation of local security guidelines, the RAS client is<br />

typically not under the complete control of the <strong>IT</strong> personnel who are<br />

responsible for the LAN. <strong>The</strong> security of data transmission media is generally<br />

completely out of their control. For this reason, protection of communications<br />

between client and server must be secured by additional means.<br />

In the environment of the RAS server the following recommendations for<br />

secure operation should be considered:<br />

- RAS access should be continuously monitored using logging and<br />

management tools.<br />

- <strong>The</strong> information collected in the course of monitoring should be regularly<br />

reviewed by a trained administrator. This person should if possible be<br />

supported with a log file analysis software tool. <strong>The</strong> data protection<br />

regulations must be considered (see also S 2.110 Data privacy guidelines<br />

for logging procedures).<br />

- If any security incidents are detected, the measures previously specified<br />

must be implemented immediately. <strong>The</strong> identified security incidents should<br />

be documented in an incident report (see also module 3.8 Handling of<br />

security incidents on this point).<br />

- In order that a controlled user authentication procedure (e.g. Remote<br />

Access Service under Windows NT, RADIUS, TACACS, TACACS+,<br />

SECURE-ID) is possible for RAS access, the consistency of the<br />

authentication data must be assured. This can be effected either through<br />

central administration of the data (using an authentication server) or else<br />

through periodic synchronisation.<br />

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

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

Monitoring of RAS<br />

access<br />

Regular analysis of log<br />

files

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

Saved successfully!

Ooh no, something went wrong!