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

Telnet<br />

<strong>The</strong> Telnet protocol allows a user to create a terminal session on a remote<br />

computer and defines for this purpose virtual input and output units (network<br />

virtual terminals) between which connection parameters have to be<br />

negociated.<br />

To get access to another computer using the Telnet command, the other<br />

computer must be running the Telnet Daemon. <strong>The</strong> standard port for a Telnet<br />

session is Port 23. Other port numbers may be set as parameters, allowing a<br />

connection to be made to other server processes.<br />

As Telnet allows full access to a remote host for a user, this access must be<br />

protected by strong authentication.<br />

A distinction is often made between simple and strong authentication. Simple<br />

authentication uses simple password procedures where the password is<br />

transmitted as plain text and is therefore not protected from eavesdroppers.<br />

Strong authentication, on the other hand, uses more complex procedures<br />

based, for example, on the use of one-time passwords or smart cards.<br />

<strong>The</strong>re is the risk with Telnet that an ‘invader’ may cut into an authorised<br />

Telnet connection during transmission, e.g. to tap classified information or<br />

enter his own commands in the Telnet connection. For this reason encrypted<br />

transmission should be possible.<br />

FTP<br />

<strong>The</strong> File Transfer Protocol (FTP) allows exchange of files between remote<br />

computers.<br />

When using FTP, two connections are established whereby the commands are<br />

transmitted through port 21 and the data through port 20. To allow the<br />

exchange of commands between computers with different operating systems,<br />

FTP defines a set of standard commands which are not the same as the user<br />

interface commands. <strong>The</strong> FTP client translates the user interface commands<br />

into the corresponding standard commands. For the firewall it is the standard<br />

commands which are relevant, because these are the only ones actually<br />

transmitted over TCP/IP.<br />

While the client establishes the command connection to the server port 21, the<br />

server is responsible for establishing the data connection from his port 20 to a<br />

client port (> 1023). This constitutes a security weakness, since ‘invaders’<br />

could pretend to be servers. <strong>The</strong> connection should, therefore, be set up the<br />

other way round and the client should use the standard command PASV<br />

instead of PORT. This forces the server to decide on a random port number<br />

and await the data transfer at this port. <strong>The</strong> client can then set up a connection<br />

to this port, so that the TCP connection is made from the protected network<br />

into the external one.<br />

All commands which manipulate or read files or directories (CWD, CDUP,<br />

RETR, STOR, DELE, LIST, NLIST), must be linked to a corresponding<br />

authorisation administration. This restricts access to certain files for<br />

untrustworthy users or blocks it altogether. This assumes that a strong<br />

authentication mechanism is in place.<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!