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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Safeguard Catalogue - Hardware & Software Remarks<br />

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

S 4.2 Screen Lock<br />

Initiation responsibility: Head of <strong>IT</strong> Section, <strong>IT</strong> Security Management<br />

Implementation responsibility: <strong>IT</strong> users<br />

"Screen lock" refers to a facility enabling the concealment of information<br />

currently displayed on the screen. In order that access to an <strong>IT</strong> system is<br />

reliably prevented during a short absence of the <strong>IT</strong> user, it should only be<br />

possible to inactivate a screen lock after successful user authentication, i.e.<br />

following entry of a password.<br />

It should be possible for the user to activate the screen lock manually. In<br />

addition, the screen lock should be automatically initiated after a predefined<br />

period of inactivity. All users should be made aware of the need to activate the<br />

screen lock when they leave their workstation for a short period. If a user is to<br />

be away from the workstation for an extended period, he should log off.<br />

<strong>The</strong> period after which a screen lock is activated due to a lack of user inputs<br />

should be neither too short nor too long. If it is too short, the screen lock may<br />

be triggered while the user has merely paused for thought. On the other hand,<br />

if the period is too long, then a third party could exploit the absence of the<br />

user. A reasonable period to set is a time interval of 15 minutes. <strong>The</strong> <strong>IT</strong><br />

Security Management Team should specify how the delay should be defined<br />

so as to satisfy the security requirements of the <strong>IT</strong> systems concerned and their<br />

operational environment.<br />

Most operating systems come supplied with screen lock facilities. When these<br />

are used, care must be taken to ensure that they are configured so that input of<br />

a password is required.<br />

A password-supported screen lock is offered in Microsoft Windows 3.x as a<br />

screen saver. However, the documentation points out that if the current<br />

application is not a Windows application, the screen saver will not be<br />

activated automatically, regardless of whether the application is executed in a<br />

window, from the MS-DOS command line or has been iconised. Under<br />

Windows 95, on the other hand, the screen saver is also automatically<br />

activated for DOS applications. Apart from Microsoft Windows, there are<br />

other products offering password-supported screen savers. Before employing<br />

such products, it is necessary to check whether the screen lock will work<br />

under all applications.<br />

Under UNIX, a screen lock can be activated with programs such as lock or,<br />

while under X-Windows, the same result can be achieved with lockscreen.<br />

Additional controls:<br />

- Has a screen lock been installed on the relevant computers?<br />

- Is the screen lock feature applied consistently?<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!