Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest
Please, try again later.
This article documents security improvements that can be made to the Veeam Backup Enterprise Manager server and its IIS-based websites.
By default, the Windows Server OS has numerous protocols and ciphers enabled, many of which are unnecessary when operating Veeam Backup Enterprise Manager.
Veeam backup infrastructure components support the following TLS versions:
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.
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.
These settings can further reduce the attack surface of the IIS-based websites for Veeam Backup Enterprise Manager.
C:\Program Files\Veeam\Backup and Replication\Enterprise Manager\WebApp\
Web.config
file to allow for easy reversion if needed.Web.config
file in a text editor and make the following changes:
Server: Microsoft-IIS/10.0
, which reveals the version of IIS being used. Setting enableVersionHeader = "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.
<httpRuntime
and add the following option:
enableVersionHeader = "false"
<httpRuntime
settings should look like this afterward:
<httpRuntime targetFramework="4.5" requestValidationMode="2.0" executionTimeout="300" enableVersionHeader="false" maxUrlLength="16384" maxQueryStringLength="2048000" maxRequestLength="2048000" enableVersionHeader="false" />
X-Content-Type-Options
to nosniff
. 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.
<customHeaders>
section and add the following option:
<add name="X-Content-Type-Options" value="nosniff"/>
<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>
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.
Your feedback has been received and will be reviewed.
Please, try again later.
Please try select less.
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
Your feedback has been received and will be reviewed.
Please, try again later.