If the company wants access to a certain data collection or makes one of their own data collections available, the Security Server is one of the obligatory elements.
The Security Server mediates inquiries to data collections and determines which institutions/persons have access to which inquiries. All activities are entered into a log, which guarantees probative value later. Therefore, the Security Server provides essential protection for the data collection of an institution, because a mistake can make data accessible to unwanted individuals.

1. One-time services in the commencement of the service
1.1. Receiving the necessary information from the client to commence the service;
1.2. Primary configuration of the service (if necessary);
1.3. Setting of the monitoring;
1.4. Setting of the services (if necessary and possible);
1.5. Registering the institution at RIHA (if necessary);
1.6. Determining the rights of access;
1.7. Setting of the parameters for the adapter server;
2. Regular activities
2.1. Monitoring
2.1.1. Following the device 24/7 and reacting to warnings;
2.2. Ordinary inspections
2.2.1. Backup of the configuration;
2.2.2. Checking up on log files;
2.2.3. Checking up on workload graphs;
2.2.4. Renewal of software as necessary (if possible);
2.2.5. Registering changes and occurrences;
3. If necessary
3.1. Solving incidents or problems related to the device, which have risen in MicroLink’s sphere of responsibility and/or are caused by MicroLink’s activity/inactivity
3.2. Management of settings subscribed by the client (e.g.):
3.2.1. Determining the rights of access;
3.2.2. Setting of the parameters for the adapter server;
3.3. Analysis of log files and workload graphs;
3.4. Making suggestions regarding the hardware, software or configurations;
3.5. Renewal of software (if possible);
3.6. Configuration management and registering changes and occurrences if necessary;
4. Activities related to the restoration of the service
4.1. Reactivation of the device;
4.2. Renewal of software;
4.3. Restoration of the configuration;
5. Closing of the service
5.1. Removing the server from the server facilities (if necessary)
5.2. Ending the service in a shared environment (if necessary)
5.3. Removing the server’s configuration from the management tools;
5.4. Removing the device from the monitoring.