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

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

S 2.61 Requirements document for modem usage<br />

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

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

<strong>The</strong> following must be determined:<br />

- Who is responsible for the secure operation of the modem (e.g. <strong>IT</strong> users for<br />

stand-alone operation, the administrator for networked systems)<br />

- Who is entitled to use the modem<br />

- In which cases must confidential information be encrypted before<br />

transmission?<br />

- In which cases must data transmissions be entered in a protocol (e.g.<br />

transmission of person related data)? If the communications software<br />

includes a protocol feature, it should be used effectively.<br />

All login procedures, successful or not, must be recorded. Correctly entered<br />

passwords should not be recorded. But it is worth considering listing<br />

unsuccessful login attempts in order to reveal password attacks.<br />

Evidence of password attacks could be, for example, frequent unsuccessful<br />

login attempts by one user, unsuccessful login attempts always from the same<br />

connection, attempts to login under different user names from one connection<br />

or during a connection.<br />

After the connection has been established, a login prompt will appear for the<br />

caller. Before the successful login it must be ensured that as little information<br />

as possible is given regarding the contacted <strong>IT</strong> system. Neither the type of<br />

installed hardware nor the operating system should be revealed. <strong>The</strong> login<br />

prompt should contain the name of the <strong>IT</strong> system and/or the organisation, a<br />

warning that all connections will be listed and an input requirement for user<br />

name and password. <strong>The</strong> reason for an unsuccessful login attempt may not be<br />

shown (false user name, false password).<br />

Separating Dial-In / Dial-Out<br />

For incoming and outgoing connections, separate lines and modems should be<br />

deployed. A caller should not have the opportunity to reconnect externally via<br />

the dialled <strong>IT</strong> system. (If this is absolutely necessary for workers with external<br />

duties, they must provide strong authentication, e.g. via a chip-card).<br />

Otherwise, hackers might abuse access to set up expensive long-distance<br />

connections or to cover up any traces they may have left.<br />

When calling back, a different modem or a different line should be used for<br />

the call back than the modem used when first calling (see also S 5.44 One-way<br />

connection setup).<br />

Additional controls:<br />

- Are all employees authorised for communication aware of the related<br />

regulations?<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!