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

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

S 5.33 Secure remote maintenance via modem<br />

Initiation responsibility: <strong>IT</strong> Security Management<br />

Implementation responsibility: Administrators<br />

<strong>The</strong> remote maintenance of <strong>IT</strong> systems via modem involves particularly high<br />

security risks. For security reasons, it is advisable to operate without external<br />

remote maintenance. If this is not possible, additional safeguards must be<br />

implemented.<br />

<strong>The</strong> <strong>IT</strong> system to be maintained, including the modem used, must incorporate<br />

the following functions:<br />

- <strong>The</strong> establishment of a connection for remote maintenance should also be<br />

initiated from the local <strong>IT</strong> system. This can be achieved by calling the<br />

remote maintenance point of the <strong>IT</strong> system requiring maintenance or by<br />

automatic call-back.<br />

- External maintenance personnel must authenticate themselves before<br />

commencing maintenance. If passwords are transferred unencrypted, they<br />

should be one-time (cf. S 5.34 Use of one-time passwords).<br />

- All activities during remote maintenance must be logged on to the <strong>IT</strong><br />

system being maintained.<br />

<strong>The</strong> following additional functions can be implemented on the <strong>IT</strong> system to be<br />

maintained:<br />

- Activation of a time lock on invalid access attempts.<br />

- Disablement of remote maintenance during normal operation and explicit<br />

allowance for a specified time period.<br />

- Restriction of permissions for maintenance personnel. <strong>The</strong> maintenance<br />

personnel must not possess full administrative privileges. On DOS PC's,<br />

gradation of the administration of privileges must be realised by means of<br />

additional software. Observe S 2.33 Division of administrator roles under<br />

UNIX for UNIX systems and S 2.38 Division of administrator roles in PC<br />

networks for PC networks.<br />

<strong>The</strong> maintenance personnel should only have access to those data and<br />

directories actually requiring maintenance.<br />

- <strong>The</strong> <strong>IT</strong> system should provide the maintenance personnel with their own<br />

user ID under which all maintenance should be carried out, if possible.<br />

- If the connection to the remote maintenance point is interrupted for some<br />

reason, access to the system must be terminated through automatic log-out.<br />

<strong>The</strong> remote maintenance must be monitored locally by <strong>IT</strong> experts. Even if<br />

remote maintenance is implemented due to lacking internal know-how or<br />

capacity, the maintenance personnel must not be left unobserved (cf. S 2.4<br />

Maintenance/repair regulations). If there are any doubts concerning<br />

procedures, the local <strong>IT</strong> expert should enquire immediately. It must, at any<br />

time, be possible to interrupt remote maintenance locally.<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!