Security
The following guidelines summarize the best practices for running the Model Manager server in a secure way:
•
Do not give unprivileged users in the organization shell access to the system where the Model Manager server runs. Although the file system directories and processes of the Model Manager server are protected from interference by other users on the system through operating system permissions, it is general best practice to restrict shell access on production servers.
•
Set up the Model Manager server to use TLS (via HTTPS) when connecting from web browsers and COMSOL Multiphysics. This increases the protection of passwords sent when logging in and reduces the risk of data leaks. The easiest way to get transport layer security is to use a reverse proxy with a certificate, which might already have been set up for other systems. Alternatively, you can add a TLS-enabled connector with a certificate to the Model Manager server — see Adding a Connector With TLS.
•
Use a low-privilege account when running the Model Manager server process. This reduces the risk of privilege escalation attacks to the system. See Installing a Model Manager Server for more information.
•
Configure the firewall of the computer or network segment where the Model Manager server runs to only expose the main port of the Model Manager server to the outside. If running the Model Manager server behind a reverse proxy, only expose the port of the reverse proxy to the outside instead.
•
If you expose the Model Manager server to the internet, make sure to operate the Model Manager server on a network isolated from your regular corporate network. One option for implementing this is to install the Model Manager server on a computer in a so-called DMZ network located between the internet and your regular corporate network. Another option is to install the Model Manager server utilizing a cloud service provider.
•
Ensure that the Preference Directory of the Model Manager server is not accessible by untrusted parties.
•
Using permissions, you can configure access control for the content stored on the Model Manager server as needed. You can also use separate instances of the Model Manager server — with each server using their own databases — to isolate different content and user groups. The latter is best practice when exposing the Model Manager server to users outside of your organization.