S 3.76 Basic user training on how to use groupware and e-mail

Initiation responsibility: Head of IT, IT Security Officer

Implementation responsibility: User

The users must be trained in the use of communication services and groupware applications such as e-mail before actually using them to avoid errors during operation and to ensure that they comply with the organisation's internal policies. In particular, they must be made aware of the potential risks and threats involved, and they must be informed which security safeguards they need to take when sending and receiving e-mails. It must be pointed out that any abnormal behaviour of the communication software must be reported.

Users must be informed that files whose contents may be considered offensive are not allowed to be sent, stored on information servers, or requested from information servers. In addition, the users must promise to follow the following rules when using communication services:

In addition, the users must be informed of the following points:

In most groupware systems, the information is transported in unencrypted form over public lines and may be stored temporarily on a number of intermediate computers before it finally reaches its recipient. It is therefore easy to manipulate the information when in route. However, the sender of an e-mail is usually allowed to enter any e-mail address as the sender address (From field), which means you can only be sure of the authenticity of the sender after contacting the sender or when using digital signatures. When in doubt, the authenticity of the sender should be verified by checking with the sender or, even better, by using encryption and/or digital signatures. As a general rule, users should not rely on the authenticity of the sender information in an e-mail.

With e-mails a fast response is expected. The mailbox should therefore be checked several times per day. If absent for a longer period, then a substitute should be arranged, for example by having incoming e-mails forwarded to a substitute (see also S 2.274 Deputisation arrangements for e-mail).

Since it is impossible in many cases to determine which e-mail client a given e-mail recipient uses and which software and operating systems are used on the transportation route, the users should be aware that problems can arise during transmission and that recipients may have problems displaying messages and attachments. Such problems can occur especially when using unusual character sets or file formats, or when using outdated email software.

Users should also be aware of the fact that e-mails may not be received by the recipient for various reasons. Especially with time-critical or important e-mails the sender should not rely on an automatic receipt confirmation. A preferred alternative is an independent reply, e.g. in form of a short e-mail with an individually worded confirmation.

Deletion of e-mails

Users must be informed of the fact that an e-mail which they deleted via their mail application themselves has in most cases not been irretrievably deleted. Many mail programs do not delete e-mails immediately, but transfer them to special folders. Users must be instructed on how to completely delete e-mails on their clients.

In addition, e-mails may still be present on mail servers after being deleted on the clients. Many Internet providers and administrators archive incoming and outgoing e-mails. Many mail applications do not delete e-mails, but move them to a "Recycle Bin" area which also has to be erased.

The users must be aware of the fact that the confidentiality of e-mails can only be ensured by encryption and that they must not rely on "quick deletion" after receipt. The same applies to other groupware applications such as diary entries.

Publication of the rules

All rules and operating instructions for the use of groupware must be available to the employees at all times, e.g. in the intranet.

Review questions: