- Veeam Support Knowledge Base
- General Security Guidelines for Veeam Self-Service Backup Portal
General Security Guidelines for Veeam Self-Service Backup Portal
| KB ID: | 2376 |
| Product: | Veeam Backup & Replication |
| Version: | All |
| Published: | 2017-11-10 |
| Last Modified: | 2025-02-06 |
Cheers for trusting us with the spot in your mailbox!
Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest
Oops! Something went wrong.
Please, try again later.
Purpose
This article documents security improvements that can be made to the Veeam Backup Enterprise Manager server and its IIS-based websites.
Solution
Part 1: Disabling Weak Protocols and Ciphers
By default, the Windows Server OS has numerous protocols and ciphers enabled, many of which are unnecessary when operating Veeam Backup Enterprise Manager.
Protocols
Veeam backup infrastructure components support the following TLS versions:
- TLS 1.2
- TLS 1.3 is partially supported by backup infrastructure components installed on Microsoft Windows Server 2022. PowerShell components and components using OpenSSL do not support TLS 1.3.
Note: For security reasons, disable outdated protocols TLS 1.0 and 1.1 if they are not needed. For more information, see this Microsoft article.
Ciphers
By default, the list of ciphers the Windows OS may negotiate for a given security protocol includes DES, RC2, RC4, and 3DES (Triple DES). These ciphers are considered vulnerable, and it's recommended to disable them.
Veeam backup infrastructure components support AES (128 and 256) Ciphers.
Note: The Best Practices option in IIS Crypto does not disable TLS 1.0 and TLS 1.1; you must toggle those within the Server Protocols and Client Protocols sections yourself.
Part 2: Adjust Website Settings to Enhance Security
These settings can further reduce the attack surface of the IIS-based websites for Veeam Backup Enterprise Manager.
- Browse to the web app installation folder.
Default:C:\Program Files\Veeam\Backup and Replication\Enterprise Manager\WebApp\ - Make a backup copy of the original
Web.configfile to allow for easy reversion if needed. - Open the
Web.configfile in a text editor and make the following changes:- Disable IIS Version Header — By default, IIS will include a header like
Server: Microsoft-IIS/10.0, which reveals the version of IIS being used. SettingenableVersionHeader = "false"adjusts the server configuration so that this version information is not included in the HTTP response headers. This adjustment is primarily a security measure aimed at reducing the amount of information disclosed to potential attackers.- Find the node
<httpRuntimeand add the following option:enableVersionHeader = "false"
- The
<httpRuntimesettings should look like this afterward:<httpRuntime targetFramework="4.5" requestValidationMode="2.0" executionTimeout="300" enableVersionHeader="false" maxUrlLength="16384" maxQueryStringLength="2048000" maxRequestLength="2048000" enableVersionHeader="false" />
- Find the node
- Enable X-Content-Type-Options Header — This setting prevents browsers from performing MIME type sniffing by setting
X-Content-Type-Optionstonosniff. By doing so, it ensures that browsers adhere to the specified Content-Type declared in the HTTP headers, rather than attempting to determine it themselves. This measure helps prevent security vulnerabilities like cross-site scripting (XSS) attacks and downloads of malicious content by enforcing strict handling of MIME types as they are served by the server.- Find the
<customHeaders>section and add the following option:<add name="X-Content-Type-Options" value="nosniff"/>
- The
<customHeaders>section should look like this afterward:<customHeaders> <remove name="X-Powered-By" /> <remove name="X-AspNet-Version" /> <remove name="Server" /> <add name="Strict-Transport-Security" value="max-age=31536000" /> <add name="X-Content-Type-Options" value="nosniff" /> </customHeaders>
- Find the
- Disable IIS Version Header — By default, IIS will include a header like
Part 3: Sanitize the Error Page
While error webpages can be user-friendly, they can inadvertently disclose critical server and application details to potential attackers probing your environment. To enhance security, sanitize the error page contents.
- Navigate to the web app installation folder:
Default: C:\Program Files\Veeam\Backup and Replication\Enterprise Manager\WebApp\ - Make a backup copy of the original Error.aspx file to allow for easy reversion if needed.
- Open the original Error.aspx file.
- Delete its contents.
- Save the now-blank file.
If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.