University of Jyväskylä information systems usage policy
Table of contents
Restriction of access rights
The restriction of access rights during an investigation procedure is defined in the consequences for misuse of information systems.
Email handling
The secrecy of personal letters, phone calls, and other confidential messages is inviolable according to the Finnish Constitution, unless otherwise provided by law. Email is comparable to a letter in this regard. Email is confidential unless it is intended to be received by the general public.
The normal handling principles of email are regulated in the email handling rules.
An administrator may need to open files containing users' emails in the following situations:
- At the user's request. The request can be made, for example, in a situation where the email inbox does not open with the programs available to the user. The permission applies only to that specific instance. If the user requests information about the contents of the mailbox, the administrator must absolutely verify the identity of the requester.
- When the email system is unable to deliver the message due to incomplete or corrupted structure. In this case, the administrator is allowed to examine and correct the technical header information of the message, but should, as much as possible, avoid reading the text content intended for the recipient.
The administrator also has the right to remove from the email queue messages that endanger the operation of the email system or that are evidently unnecessary due to a technical error.
Handling other files
The administrator does not have the general right to read or otherwise handle the content of files owned by users.
However, the administrator has the right to handle files in the following situations:
- When the user has given permission to do so to resolve an issue.
- With a specific written request (e.g., if the performance of university duties is in danger of being impeded due to an absence, files owned by an absent employee/student that are protected from others may need to be handled. The unit supervisor, or equivalent, can authorize the administrator to grant access to the necessary files to a designated person).
- If the user account holds programs or configuration files that disrupt the operation, security, or privacy of other users of the system. In this case, the administrator can check the content of the program files and, if necessary, prevent their operation.
- If there is a justified reason to suspect that the user account has been compromised and that it holds files or programs that pose a threat or danger to the university's functionality or security.
- If the administrator suspects that the account is in the wrong hands, the administrator has the right to temporarily disable the account. The general principle is to try to contact the user before taking action, but protective and corrective measures may need to be taken immediately before contact.
- If there is a justified reason to suspect that the account holder has engaged in misuse and it can be assumed that certain files owned by the user contain evidence of misuse.
- The administrator has the right to temporarily disable the account in the case of misuse. The user's misuse is handled according to the university's information systems usage rules and the consequences for IT violations policy.
- The administrator has the right to block access to web pages that are against the law or the university's information systems usage rules.
- When the protection of the files otherwise allows it.
The administrator must inform the owner of deleted or modified files and web pages.
In addition to the above, the administrator always has the right to:
- Read and modify initialization files, mail forwarding or sorting files, and other files affecting the system's operation located in users' home directories, if they are found to threaten the system's operation, security, or user privacy. If the necessary change cannot be made without losing the user's own modifications, the old version created by the user is moved to another name, and the user is informed of the change.
- Ensure that there are no illegal or system-threatening files on shared disk areas. Such files include malware, copyright-infringing recordings, or materials deemed illegal by the Criminal Code.
- Destroy files intended for temporary storage on disk areas manually or automatically according to predefined principles. The deletion principles must be available for users to view, but there is no need to inform users of deletions made according to these principles.
Monitoring directories and file listings
Processing directory structures, file names, modification dates, sizes, protection levels, and other file-related information is part of normal maintenance, performed according to good maintenance practices.
If it is found that the protection of a file or directory is too weak given its nature, the administrator has the right to change the protection to an appropriate level.
The administrator is bound by confidentiality. In performing maintenance tasks, efforts are made to avoid unnecessarily displaying the names of files and the like.
Monitoring programs and processes
The administrator, together with the system owner, defines which software is available in the system. Programs can be prohibited or disabled if their use is not necessary for university operations and they pose a threat to service level or security. The decision is made by the system owner.
The administrator monitors the programs running on the information systems as part of normal maintenance.
The administrator may change the execution priority of a running process if it consumes system resources unreasonably.
The administrator may terminate a process if:
- The process operation is clearly disrupted,
- The process hampers the operation of the system with excessive load and is not justified by the system's intended use, or
- The process is associated with software whose use is against the system usage guidelines and regulations. In this case, the user is informed about the termination of the process and the related regulations.
Monitoring the communication network
The administrator of the university's communication network monitors traffic within the university network and external connections using network monitoring programs and log data. This is done to ensure a reasonable service level and security, as well as to manage the cost-effective use of external connections.
When monitoring traffic, the focus is on the volume and methods of communication, not the content. Monitoring of source and destination machines is statistical and does not target individual users. However, traffic can be more closely monitored for a specific system when investigating anomalies, such as those causing particularly high loads. Automatic intrusion detection systems may analyze all traffic.
The administrator may contact the responsible person for a machine causing a high volume of traffic or other anomalies to investigate potential disruptions or misuse.
The communication network administrator is authorized to block network connections or the use of a specific service to a machine or part of the network,
- that generates traffic threatening the service level or security of network traffic,
- if there is a justified reason to suspect that the machine or machines are in the wrong hands or infected with malware,
- that violates the information systems usage rules, or
- that is not properly maintained, particularly with regard to security.
In all cases, the responsible administrator of the machine or network segment must be contacted immediately after traffic has been blocked.
Technical analysis of information systems, services, and devices
Digital services can use analysis tools to investigate the security status of a service or device, the visibility of services, or other technical details related to system operation. Analysis can be targeted at systems within the university network or those outside the university network but under the university's responsibility. Actions may include vulnerability scans.
Handling of log data
The university's information systems record log data to document system operations, investigate potential disruptions or misuse, and collect billing information. At the university, log data is normally used only for technical tasks by administrators bound by confidentiality and to facilitate billing.
Data storage
As part of maintenance, the provider of information system services must ensure the backup of their systems. Backups must be stored appropriately, and the administrator must ensure the readability of the backups. Data on backups should be handled with the same principles as the corresponding data in information systems. The destruction of backups must be carried out in a manner that does not compromise the confidentiality of the data contained within them.
Monitoring the maintenance rules
The monitoring of these rules is the responsibility of the university's IT management and the owners of the information systems of other relevant university units. Violations of the rules are handled according to the consequences for misuse of information systems.