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.

Threats Catalogue Deliberate Acts Remarks<br />

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

T 3.43 Inappropriate handling of passwords<br />

Even the use of well thought out authentication procedures will be of little<br />

avail if the users are careless in handling the necessary access-granting means.<br />

Whether the access-granting means used are passwords, PINs or<br />

authentication tokens, in practice they are often disclosed to other persons or<br />

not kept safe.<br />

Often users disclose their passwords to other users for reasons of convenience.<br />

Passwords are frequently shared within teams so that it is easier for individual<br />

staff to access shared files. <strong>The</strong> obligation to use a password is often<br />

experienced as onerous and, to make life easier, passwords are never changed<br />

or else all staff use the same password.<br />

Where a token-based procedure (e.g. smart card or one-time password<br />

generator) is used for user authentication, if this is lost there is a danger that<br />

the token could be used by unauthorised persons. An unauthorised user might<br />

thus be able to establish a remote access connection using this token.<br />

Where large numbers of different passwords and PINs are used, often users<br />

cannot remember them all. Frequently this results in passwords being<br />

forgotten, which sometimes means that extra work is required in order to be<br />

able to continue working with the system. Again, authentication tokens can<br />

get lost. With very secure <strong>IT</strong> Systems, the loss of passwords or tokens can<br />

even result in loss of all user data.<br />

Often passwords are written down in order to prevent their being forgotten.<br />

This is not a problem as long as they are carefully looked after so that they are<br />

protected against unauthorised access. Unfortunately this is not always the<br />

case. A classic example is to keep the password written underneath the<br />

keyboard or on a sticker attached to the screen. Keeping authentication tokens<br />

underneath the keyboard is also a popular habit.<br />

Another means of avoiding forgetting passwords is to choose "suitable"<br />

passwords. But if users are able to choose their passwords themselves and<br />

have not been made sufficiently aware of the problems, they will often choose<br />

trivial passwords such as "4711" or the names of friends.<br />

Examples:<br />

- It was established in one company using spot checks that many passwords<br />

were not suitable or were not being changed sufficiently frequently.<br />

Technical means were employed to ensure that passwords were changed<br />

every month and also contained numbers or special characters. It turned out<br />

that one administrator was choosing his passwords as follows:<br />

january98, february98, march98 etc.<br />

- In a government organisation it was discovered that users whose offices<br />

faced the street often used the same password, the name of the hotel over<br />

the road which, with its large illuminated letters, dominated the view out of<br />

the window.<br />

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

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

Passing on of<br />

passwords or token<br />

Loss of an<br />

authentication token<br />

Too many different<br />

passwords<br />

Password under the<br />

keyboard<br />

Passwords which are too<br />

simple

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

Saved successfully!

Ooh no, something went wrong!