Advanced Settings

This section covers the guidelines for advanced settings.

The operating system on which the MultiScanner runs is an Ubuntu Server. So, if you have the basic knowledge of working with Linux, you are able to configure the advanced settings on this system.

Note: The default username and password of the operating system are "multiscanner" and "1" respectively. It is highly recommended to change them after you installed the scanner.

MultiScanner configurations can be found in a JSON file that you can find in the following path:

/opt/manager/configs/configs.json

By changing the contents of this file, you can change the way the system works.

It is recommended that if you are not familiar with these settings work, you avoid changing them. Below, some of the important settings are explained:

• HTTPS: This configuration determines if the MultiScanner runs with https protocol or not. If you are willing to run the MultiScanner with HTTPS, it is recommended to replace the HTTPS certificate file that you can find in the “certs” folder with your organization’s HTTPS certificate.
• port: This configuration determines the port on which the MultiScanner runs, that is port 80 (or 443 in case https config is enabled) by default, and you can customize it if you are willing to. Note that the port you choose should not be used by another process other than the MultiScanner service.
• timeout: This configuration is for detecting crashes in the antivirus. By default, if an antivirus does not send any response after 3600 seconds (1 hour), it is considered to have crashed or encountered an error. You can customize this threshold based on your organization’s needs.
• error-tracking: Cyberno sends a log to its server to investigate the possible errors of the MultiScanner service. Clear the contents of the “error_tracking” field if you are not willing to send this log to our servers. However, it is recommended not to do so, because in that case, it is not possible for Cyberno to detect those errors in real-time.
• throttle: If this configuration equals true and if an IP address or a user sends many requests to perform a DoS or Brute-Force attack, they will get blocked and will face error code 429.
• my_domain: This configuration must be equals to the domain address on which the MultiScanner is accessible in your organization’s network.
• lan: This configuration, which can be found in the “my_ip” section, must multi-scanner server’s IP address. If you use VMware-based antivirus, it has to be enabled.
• auto-activate: This configuration determines if the E-mail address of users that requested to register in the system will be accepted automatically or not. By default, it should be equals to “false” for the system to send an E-mail including the password to the user. It is recommended not to change this configuration.
• ttl: This field determines how long the authentication should be valid. By default, this configuration equals "10080 minutes", or 1 week. This value means that if a user logs in to the system, they do not need to log in again. You can customize this parameter based on your organization’s needs.
• mail: Your organization’s e-mail service information is needed to be inserted here for sending the e-mails to users. For example, this e-mail server could send a new password to its e-mail.
• type: This section determines the type of data storage. If it equals “memory”, it means the data gets stored in the memory and all the scans data gets removed after the MultiScanner stops scanning. If it equals "sqlite", all the data gets stored in a SQLite database in the following path:

/opt/manager/database

If you use the latter, you have a log of all the finished scans that lasts forever, and you can always get access to it.

Note: This system uses SQLite for storing data by default, however it also supports other databases like PostgreSQL, MySQL, Oracle and Microsoft SQL Server.

When you finished setting up the advanced configurations, you need to restart the MultiScanner service. To do so, run the following command:

sudo systemctl restart multiscanner.service