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

Normally this should entail the use of predefined acceptance configurations<br />

and simulated operational scenarios. During testing care must be taken to<br />

ensure that only the persons authorised to participate in testing can access<br />

the RAS system.<br />

Upon completion of installation of a RAS system, the system should have a<br />

secure starting configuration which initially allows access only to the<br />

authorised administrators (see also S 4.111 Secure configuration of the RAS<br />

system). <strong>The</strong>se persons should then convert the RAS system to a secure<br />

operating state. Once this is achieved, continuous operations can then<br />

commence.<br />

Example<br />

Under Windows NT the installation of RAS servers and clients is very simple<br />

and is virtually identical as the Windows NT Remote Access Service contains<br />

both client and server functions.<br />

<strong>The</strong> following applies to a RAS client running under Windows NT:<br />

- <strong>The</strong> server functions of the Remote Access Service must be disabled. This<br />

is done by allowing only outgoing calls on all devices which can be used<br />

for remote access (e.g. modem, ISDN card, VPN adapter). <strong>The</strong> relevant<br />

dialogue boxes are reached by selecting the following sequence of options:<br />

Control Panel, Network, Services, Remote Access Service, Attached<br />

Device, Configure.<br />

- For the RAS client only the protocols that are permitted for remote access<br />

should be enabled. This is done by selecting Control Panel, Network,<br />

Services, Remote Access Service, Attached Device, Network.<br />

- <strong>The</strong> characteristics of a RAS connection are specified in Windows NT<br />

through Dial-Up Networking. Here the parameters required under the RAS<br />

security concept should be set (e.g. "Require data encryption").<br />

<strong>The</strong> following applies to a RAS server running under Windows NT:<br />

- <strong>The</strong> client functions of the Remote Access Service must be disabled. This<br />

is done by allowing only incoming calls on all the devices which can be<br />

used for remote access.<br />

- For the RAS server only the protocols that are permitted for remote access<br />

should be enabled.<br />

- <strong>The</strong> parameters required under the RAS security concept must be set for<br />

incoming RAS connections. This is done by selecting Control Panel,<br />

Network, Services, Remote Access Service, Attached Device, Network.<br />

- Only authorised users should be allowed to dial in. This can be specified<br />

under Windows NT through either RAS Manager or User Manager.<br />

Additional controls:<br />

- Have all deviations from the planning premises for the RAS system been<br />

noted in the planning documentation?<br />

- Have the security mechanisms been function tested (e.g. has encryption of<br />

communications been tested using a network analyser)?<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!