5 1 0:Securing SEP sesam Network Traffic
Overview
To protect your network traffic from theft and other threats, it is strongly recommended to use the HTTPS protocol for transferring data over the network. HTTP and HTTPS are both protocols used for transferring data over the internet, but they have a key difference in security. The main difference between the two protocols is that HTTPS uses Transport Layer Security (TLS) to encrypt data, ensuring that it cannot be read by anyone intercepting the data, and digitally signs requests and responses. This makes HTTPS significantly more secure than HTTP.
Since SEP sesam v. 5.1.0 Apollon, the insecure transport protocols HTTP and FTP can be disabled. This applies to:
- Accessing the user interface (GUI or WebUI) on the SEP sesam UI REST Server (switching from HTTP to HTTPS)
- Transferring data from and to clients or the SEP sesam storage environment (switching from FTP/HTTP to HTTPS)
Note | |
For encryption, SEP sesam uses CPU instruction sets, such as Advanced Vector Extensions (AVX). This ensures that data transfer via HTTPS performs similarly to HTTP or FTP. However, this requires the use of modern processor architectures. |
SEP sesam uses individual Transmission Control Protocol (TCP) network ports when using the FTP and HTTP/HTTPS protocols. By disabling the insecure protocols, the TCP ports used for these protocols are also closed.
For more information on using only HTTPS for:
- The UI, refer to Can I disable HTTP for connections to REST server?
- Data transmission, refer to Disabling Insecure Transport Modes.
See also
Ransomware Protection Best Practices — Configuring Clients — Disabling Insecure Transport Modes — Configuring SSL Secured Communication for SEP sesam Backup Network