Product Documentation

Sécuriser le déploiement de Director

Feb 01, 2018

This article highlights areas that might have an impact on system security when deploying and configuring Director.

Configure Microsoft Internet Information Services (IIS)

You can configure Director with a restricted IIS configuration. Note that this is not the default IIS configuration.

Filename extensions

You can disallow unlisted file name extensions.

Director requires these file name extensions in Request Filtering:

  • .aspx
  • .css
  • .html
  • .js
  • .png
  • .svc

Director requires the following HTTP verbs in Request Filtering. You can disallow unlisted verbs.

  • GET
  • POST
  • HEAD

Director does not require:

  • ISAPI filters
  • ISAPI extensions
  • CGI programs
  • FastCGI programs

Important:

  • Director requires Full Trust. Do not set the global .NET trust level to High or lower.
  • Director maintains a separate application pool. To modify the Director settings, select the Director Site and modify.

Configure user rights

When Director is installed, its application pools are granted the logon right Log on as a service and the privileges Adjust memory quotas for a process, Generate security audits, and Replace a process level token. This is normal installation behavior when application pools are created.

You do not need to change these user rights. These privileges are not used by Director and are automatically disabled.

Director communications

In a production environment, Citrix recommends using the Internet Protocol security (IPsec) or HTTPS protocols to secure data passing between Director and your servers. IPsec is a set of standard extensions to the Internet Protocol that provides authenticated and encrypted communications with data integrity and replay protection. Because IPsec is a network-layer protocol set, higher level protocols can use it without modification. HTTPS uses the Transport Layer Security (TLS) protocols to provide strong data encryption.

Note:

  • Citrix strongly recommends that you do not enable unsecured connections to Director in a production environment.
  • Secure communications from Director requires configuration for each connection separately.
  • The SSL protocol is not recommended.  Use the more secure TLS protocol instead.
  • You must secure communications with NetScaler using TLS, not IPsec.

To secure communications between Director and XenApp and XenDesktop servers (for monitoring and reports), refer to Data Access Security.

To secure communications between Director and NetScaler (for NetScaler Insight), refer to Configure network analysis.

To secure communications between Director and License server, refer to Secure the License Administration Console.

Director security separation

If you deploy any web applications in the same web domain (domain name and port) as Director, any security risks in those web applications could potentially reduce the security of your Director deployment. Where a greater degree of security separation is required, Citrix recommends that you deploy Director in a separate web domain.