View Security VMware. Horizon 7 7.4 74
User Manual: Pdf Horizon 7.4 - Security User Guide for VMware Horizon Software, Free Instruction Manual
Open the PDF directly: View PDF .
Page Count: 41
Download | |
Open PDF In Browser | View PDF |
View Security Modified on 4 JAN 2018 VMware Horizon 7 7.4 View Security You can find the most up-to-date technical documentation on the VMware website at: https://docs.vmware.com/ If you have comments about this documentation, submit your feedback to docfeedback@vmware.com VMware, Inc. 3401 Hillview Ave. Palo Alto, CA 94304 www.vmware.com Copyright © 2009–2018 VMware, Inc. All rights reserved. Copyright and trademark information. VMware, Inc. 2 Contents View Security 4 1 Horizon 7 Accounts, Resources, and Log Files 5 Horizon 7 Accounts 5 Horizon 7 Resources Horizon 7 Log Files 6 6 2 View Security Settings 8 Security-Related Global Settings in View Administrator 9 Security-Related Server Settings in View Administrator 11 Security-Related Settings in View LDAP 12 3 Ports and Services 13 View TCP and UDP Ports 13 Services on a View Connection Server Host Services on a Security Server 18 18 4 Configuring Security Protocols and Cipher Suites on a View Connection Server Instance or on a Security Server 20 Default Global Policies for Security Protocols and Cipher Suites Configuring Global Acceptance and Proposal Policies Configure Acceptance Policies on Individual Servers Configure Proposal Policies on Remote Desktops Older Protocols and Ciphers Disabled in View 21 21 23 24 25 5 Configuring Security Protocols and Cipher Suites for Blast Secure Gateway 27 Configure Security Protocols and Cipher Suites for Blast Secure Gateway (BSG) 27 6 Deploying USB Devices in a Secure Horizon 7 Environment 29 Disabling USB Redirection for All Types of Devices Disabling USB Redirection for Specific Devices 29 30 7 HTTP Protection Measures on Connection Servers and Security Servers 33 Internet Engineering Task Force Standards World Wide Web Consortium Standards Other Protection Measures 34 37 Configure HTTP Protection Measures VMware, Inc. 33 40 3 View Security View Security provides a concise reference to the security features of VMware Horizon 7. n Required system and database login accounts. n Configuration options and settings that have security implications. n Resources that must be protected, such as security-relevant configuration files and passwords, and the recommended access controls for secure operation. n Location of log files and their purpose. n External interfaces, ports, and services that must be open or enabled for the correct operation of View. Intended Audience This information is intended for IT decision makers, architects, administrators, and others who must familiarize themselves with the security components of View. VMware, Inc. 4 Horizon 7 Accounts, Resources, and Log Files 1 Having different accounts for specific components protects against giving individuals more access and permissions than they need. Knowing the locations of configuration files and other files with sensitive data aids in setting up security for various host systems. Note Starting with Horizon 7.0, View Agent is renamed Horizon Agent. This section includes the following topics: n Horizon 7 Accounts n Horizon 7 Resources n Horizon 7 Log Files Horizon 7 Accounts You must set up system and database accounts to administer Horizon 7 components. Table 1‑1. Horizon 7 System Accounts Horizon Component Required Accounts Horizon Client Configure user accounts in Active Directory for the users who have access to remote desktops and applications. The user accounts must be members of the Remote Desktop Users group, but the accounts do not require Horizon administrator privileges. vCenter Server Configure a user account in Active Directory with permission to perform the operations in vCenter Server that are necessary to support Horizon 7. For information about the required privileges, see the View Installation document. View Composer Create a user account in Active Directory to use with View Composer. View Composer requires this account to join linked-clone desktops to your Active Directory domain. The user account should not be a Horizon administrative account. Give the account the minimum privileges that it requires to create and remove computer objects in a specified Active Directory container. For example, the account does not require domain administrator privileges. For information about the required privileges, see the View Installation document. Connection Server When you install Horizon 7, you can specify a specific domain user, the local Administrators group, or a specific domain user group as Horizon administrators. We recommend creating a dedicated domain user group of Horizon administrators. The default is the currently logged in domain user. In Horizon Administrator, you can use View Configuration > Administrators to change the list of Horizon administrators. See the View Administration document for information about the privileges that are required. VMware, Inc. 5 View Security Table 1‑2. Horizon Database Accounts Horizon Component Required Accounts View Composer database An SQL Server or Oracle database stores View Composer data. You create an administrative account for the database that you can associate with the View Composer user account. For information about setting up a View Composer database, see the View Installation document. Event database used by Horizon Connection Server An SQL Server or Oracle database stores Horizon event data. You create an administrative account for the database that Horizon Administrator can use to access the event data. For information about setting up a View Composer database, see the View Installation document. To reduce the risk of security vulnerabilities, take the following actions: n Configure Horizon 7 databases on servers that are separate from other database servers that your organization uses. n Do not allow a single user account to access multiple databases. n Configure separate accounts for access to the View Composer and event databases. Horizon 7 Resources Horizon 7 includes several configuration files and similar resources that must be protected. Table 1‑3. Horizon Connection Server and Security Server Resources Resource Location Protection LDAP settings Not applicable. LDAP data is protected automatically as part of role-based access control. LDAP backup files %ProgramData%\VMWare\VDM\backups Protected by access control. locked.properties install_directory\VMware\VMware View\Server\sslgateway\conf Ensure that this file is secured against access by any user other than Horizon administrators. install_directory\VMware\VMware View\Server\appblastgateway Ensure that this file is secured against access by any user other than Horizon administrators. Log files See Horizon 7 Log Files Protected by access control. web.xml install_directory\VMware View\Server\broker\web apps\ROOT\Web INF Protected by access control. (secure gateway configuration file) absg.properties (Blast Secure Gateway configuration file) (Tomcat configuration file) Horizon 7 Log Files Horizon 7 creates log files that record the installation and operation of its components. Note Horizon 7log files are intended for use by VMware Support. VMware recommends that you configure and use the event database to monitor Horizon 7. For more information, see the View Installation and View Integration documents. VMware, Inc. 6 View Security Table 1‑4. Horizon 7 Log Files Horizon Component File Path and Other Information All components (installation logs) %TEMP%\vmmsi.log_date_timestamp Horizon Agent:\ProgramData\VMware\VDM\logs %TEMP%\vminst.log_date_timestamp To access Horizon 7 log files that are stored in :\ProgramData\VMware\VDM\logs, you must open the logs from a program with elevated administrator privileges. Right-click the program file and select Run as administrator. If a User Data Disk (UDD) is configured, might correspond to the UDD. The logs for PCoIP are named pcoip_agent*.log and pcoip_server*.log. Published Applications View Event Database configured on an SQL Server or Oracle database server. Windows Application Event logs. Disabled by default. View Composer %system_drive%\Windows\Temp\vmware-viewcomposer-ga-new.log on the linked-clone desktop. The View Composer log contains information about the execution of QuickPrep and Sysprep scripts. The log records the start time and end time of script execution, and any output or error messages. Connection Server or Security Server :\ProgramData\VMware\VDM\logs. The log directory is configurable in the log configuration settings of the View Common Configuration ADMX template file (vdm_common.admx) . PCoIP Secure Gateway logs are written to files named SecurityGateway_*.log in the PCoIP Secure Gateway subdirectory. Blast Secure Gateway logs are written to files named absg*.log in the Blast Secure Gateway subdirectory. Horizon Services Horizon Event Database configured on an SQL Server or Oracle database server. Windows System Event logs. VMware, Inc. 7 View Security Settings 2 View includes several settings that you can use to adjust the security of the configuration. You can access the settings by using View Administrator or by using the ADSI Edit utility, as appropriate. Note For information about security settings for Horizon Client and Horizon Agent, see the Horizon Client and Agent Security document. This section includes the following topics: n Security-Related Global Settings in View Administrator n Security-Related Server Settings in View Administrator n Security-Related Settings in View LDAP VMware, Inc. 8 View Security Security-Related Global Settings in View Administrator Security-related global settings for client sessions and connections are accessible under View Configuration > Global Settings in View Administrator. Table 2‑1. Security-Related Global Settings Setting Description Change data recovery password The password is required when you restore the View LDAP configuration from an encrypted backup. When you install View Connection Server version 5.1 or later, you provide a data recovery password. After installation, you can change this password in View Administrator. When you back up View Connection Server, the View LDAP configuration is exported as encrypted LDIF data. To restore the encrypted backup with the vdmimport utility, you must provide the data recovery password. The password must contain between 1 and 128 characters. Follow your organization's best practices for generating secure passwords. Message security mode Determines the security mechanism used when JMS messages are passed between View components. n If set to Disabled, message security mode is disabled. n If set to Enabled, legacy message signing and verification of JMS messages takes place. View components reject unsigned messages. This mode supports a mix of SSL and plain JMS connections. n If set to Enhanced, SSL is used for all JMS connections, to encrypt all messages. Access control is also enabled to restrict the JMS topics that View components can send messages to and receive messages from. n If set to Mixed, message security mode is enabled, but not enforced for View components that predate View Manager 3.0. The default setting is Enhanced for new installations. If you upgrade from a previous version, the setting used in the previous version is retained. Important VMware strongly recommends setting the message security mode to Enhanced after you upgrade all View Connection Server instances, security servers, and View desktops to this release. The Enhanced setting provides many important security improvements and MQ (message queue) updates. Enhanced Security Status (Read-only) VMware, Inc. Read-only field that appears when Message security mode is changed from Enabled to Enhanced. Because the change is made in phases, this field shows the progress through the phases: n Waiting for Message Bus restart is the first phase. This state is displayed until you manually restart either all Connection Server instances in the pod or the VMware Horizon View Message Bus Component service on all Connection Server hosts in the pod. n Pending Enhanced is the next state. After all View Message Bus Component services have been restarted, the system begins changing the message security mode to Enhanced for all desktops and security servers. n Enhanced is the final state, indicating that all components are now using Enhanced message security mode. 9 View Security Table 2‑1. Security-Related Global Settings (Continued) Setting Description Reauthenticate secure tunnel connections after network interruption Determines if user credentials must be reauthenticated after a network interruption when Horizon Clients use secure tunnel connections to View desktops and applications. This setting offers increased security. For example, if a laptop is stolen and moved to a different network, the user cannot automatically gain access to the View desktops and applications because the network connection was temporarily interrupted. This setting is disabled by default. Forcibly disconnect users Disconnects all desktops and applications after the specified number of minutes has passed since the user logged in to View. All desktops and applications will be disconnected at the same time regardless of when the user opened them. The default is 600 minutes. For clients that support applications. If the user stops using the keyboard and mouse, disconnect their applications and discard SSO credentials Protects application sessions when there is no keyboard or mouse activity on the client device. If set to After ... minutes, View disconnects all applications and discards SSO credentials after the specified number of minutes without user activity. Desktop sessions are disconnected. Users must log in again to reconnect to the applications that were disconnected or launch a new desktop or application. If set to Never, View never disconnects applications or discards SSO credentials due to user inactivity. The default is Never. Other clients. Discard SSO credentials Discards the SSO credentials after a certain time period. This setting is for clients that do not support application remoting. If set to After ... minutes, users must log in again to connect to a desktop after the specified number of minutes has passed since the user logged in to View, regardless of any user activity on the client device. The default is After 15 minutes. Enable IPSec for Security Server pairing Determines whether to use Internet Protocol Security (IPSec) for connections between security servers and View Connection Server instances. This setting must be disabled before installing a security server in FIPS mode; otherwise pairing will fail. By default, IPSec for security server connections is enabled. View Administrator session timeout Determines how long an idle View Administrator session continues before the session times out. Important Setting the View Administrator session timeout to a high number of minutes increases the risk of unauthorized use of View Administrator. Use caution when you allow an idle session to persist a long time. By default, the View Administrator session timeout is 30 minutes. You can set a session timeout from 1 to 4320 minutes. For more information about these settings and their security implications, see the View Administration document. Note SSL is required for all Horizon Client connections and View Administrator connections to View. If your View deployment uses load balancers or other client-facing, intermediate servers, you can off-load SSL to them and then configure non-SSL connections on individual View Connection Server instances and security servers. See "Off-load SSL Connections to Intermediate Servers" in the View Administration document. VMware, Inc. 10 View Security Security-Related Server Settings in View Administrator Security-related server settings are accessible under View Configuration > Servers in View Administrator. Table 2‑2. Security-Related Server Settings Setting Description Use PCoIP Secure Gateway for PCoIP connections to machine Determines whether Horizon Client makes a further secure connection to the View Connection Server or security server host when users connect to View desktops and applications with the PCoIP display protocol. If this setting is disabled, the desktop or application session is established directly between the client and the View desktop or the Remote Desktop Services (RDS) host, bypassing the View Connection Server or security server host. This setting is disabled by default. Use Secure Tunnel connection to machine Determines whether Horizon Client makes a further HTTPS connection to the View Connection Server or security server host when users connect to a View desktop or an application. If this setting is disabled, the desktop or application session is established directly between the client and the View desktop or the Remote Desktop Services (RDS) host, bypassing the View Connection Server or security server host. This setting is enabled by default. Use Blast Secure Gateway for Blast connections to machine Determines whether clients that use a Web browser or the Blast Extreme display protocol to access desktops use Blast Secure Gateway to establish a secure tunnel to View Connection Server. If not enabled, clients using a Blast Extreme session and Web browsers make direct connections to View desktops, bypassing View Connection Server. This setting is disabled by default. For more information about these settings and their security implications, see the View Administration document. VMware, Inc. 11 View Security Security-Related Settings in View LDAP Security-related settings are provided in View LDAP under the object path cn=common,ou=global,ou=properties,dc=vdi,dc=vmware,dc=int. You can use the ADSI Edit utility to change the value of these settings on a View Connection Server instance. The change propagates automatically to all other View Connection Server instances in a group. Table 2‑3. Security-Related Settings in View LDAP Name-value pair Description csallowunencryptedstartsession The attribute is pae-NameValuePair. This attribute controls whether a secure channel is required between a View Connection Server instance and a desktop when a remote user session is being started. When View Agent 5.1 or later, or Horizon Agent 7.0 or later, is installed on a desktop computer, this attribute has no effect and a secure channel is always required. When a View Agent older than View 5.1 is installed, a secure channel cannot be established if the desktop computer is not a member of a domain with a two-way trust to the domain of the View Connection Server instance. In this case, the attribute is important to determine whether a remote user session can be started without a secure channel. In all cases, user credentials and authorization tickets are protected by a static key. A secure channel provides further assurance of confidentiality by using dynamic keys. If set to 0, a remote user session will not start if a secure channel cannot be established. This setting is suitable if all the desktops are in trusted domains or all desktops have View Agent 5.1 or later installed. If set to 1, a remote user session can be started even if a secure channel cannot be established. This setting is suitable if some desktops have older View Agents installed and are not in trusted domains. The default setting is 1. VMware, Inc. 12 3 Ports and Services Certain UDP and TCP ports must be open so that View components can communicate with each other. Knowing which Windows services run on each type of View server helps identify services that do not belong on the server. This section includes the following topics: n View TCP and UDP Ports n Services on a View Connection Server Host n Services on a Security Server View TCP and UDP Ports View uses TCP and UDP ports for network access between its components. During installation, View can optionally configure Windows firewall rules to open the ports that are used by default. If you change the default ports after installation, you must manually reconfigure Windows firewall rules to allow access on the updated ports. See "Replacing Default Ports for View Services" in the View Installation document. Table 3‑1. TCP and UDP Ports Used by View Source Port Target Port Protoco l Security server, View Connection Server, or Unified Access Gateway appliance 55000 Horizon Agent 4172 UDP PCoIP (not SALSA20) if PCoIP Secure Gateway is used. Security server, View Connection Server, or Unified Access Gateway appliance 4172 Horizon Client * UDP PCoIP (not SALSA20) if PCoIP Secure Gateway is used. Security server 500 VMware, Inc. Description Note Because the target port varies, see the note below this table. View Connection Server 500 UDP IPsec negotiation traffic. 13 View Security Table 3‑1. TCP and UDP Ports Used by View (Continued) Source Port Target Port Protoco l Description Security server * View Connection Server 4001 TCP JMS traffic. Security server * View Connection Server 4002 TCP JMS SSL traffic. Security server * View Connection Server 8009 TCP AJP13-forwarded Web traffic, if not using IPsec. Security server * View Connection Server * ESP AJP13-forwarded Web traffic, when using IPsec without NAT. Security server 4500 View Connection Server 4500 UDP AJP13-forwarded Web traffic, when using IPsec through a NAT device. Security server, View Connection Server, or Unified Access Gateway appliance * Horizon Agent 3389 TCP Microsoft RDP traffic to View desktops when tunnel connections are used. Security server, View Connection Server, or Unified Access Gateway appliance * Horizon Agent 9427 TCP Windows Media MMR redirection and client drive redirection when tunnel connections are used. Security server, View Connection Server, or Unified Access Gateway appliance * Horizon Agent 32111 TCP USB redirection and time zone synchronization when tunnel connections are used. Security server, View Connection Server, or Unified Access Gateway appliance * Horizon Agent 4172 TCP PCoIP if PCoIP Secure Gateway is used. Security server, View Connection Server, or Unified Access Gateway appliance * Horizon Agent 22443 TCP VMware Blast Extreme if Blast Secure Gateway is used. VMware, Inc. 14 View Security Table 3‑1. TCP and UDP Ports Used by View (Continued) Source Port Target Port Protoco l Description Security server, View Connection Server, or Unified Access Gateway appliance * Horizon Agent 22443 TCP HTML Access if Blast Secure Gateway is used. Horizon Agent 4172 Horizon Client * UDP PCoIP, if PCoIP Secure Gateway is not used. Note Because the target port varies, see the note below this table. Horizon Agent 4172 View Connection Server, security server, or Unified Access Gateway appliance 55000 UDP PCoIP (not SALSA20) if PCoIP Secure Gateway is used. Horizon Agent 4172 Unified Access Gateway appliance * UDP PCoIP. View desktops and applications send PCoIP data back to an Unified Access Gateway appliance from UDP port 4172 . The destination UDP port will be the source port from the received UDP packets and so as this is reply data, it is normally unnecessary to add an explicit firewall rule for this. Horizon Client * View Connection Server or security server or Unified Access Gateway appliance 80 TCP SSL (HTTPS access) is enabled by default for client connections, but port 80 (HTTP access) can be used in certain cases. See HTTP Redirection in View. Horizon Client * View Connection Server, security server, or Unified Access Gateway appliance 443 TCP HTTPS for logging in to View. (This port is also used for tunnelling when tunnel connections are used.) Horizon Client * View Connection Server or security server or Unified Access Gateway appliance 4172 TCP and UDP PCoIP if PCoIP Secure Gateway is used. Horizon Client * Horizon Agent 3389 TCP Microsoft RDP traffic to View desktops if direct connections are used instead of tunnel connections. Horizon Client * Horizon Agent 9427 TCP Windows Media MMR redirection and client drive redirection, if direct connections are used instead of tunnel connections. VMware, Inc. 15 View Security Table 3‑1. TCP and UDP Ports Used by View (Continued) Source Port Target Port Protoco l Horizon Client * Horizon Agent 32111 TCP USB redirection and time zone synchronization if direct connections are used instead of tunnel connections. Horizon Client * Horizon Agent 4172 TCP and UDP PCoIP if PCoIP Secure Gateway is not used. Description Note Because the source port varies, see the note below this table. Horizon Client * Horizon Agent 22443 TCP and UDP VMware Blast Horizon Client * View Connection 4172 TCP PCoIP (not SALSA20) if PCoIP Secure Gateway is and UDP used. Server, security server, or Unified Access Gateway appliance Note Because the source port varies, see the note below this table. Web Browser * Security server or Unified Access Gateway appliance 8443 TCP HTML Access. View Connection Server * View Connection Server 48080 TCP For internal communication between View Connection Server components. View Connection Server * vCenter Server or View Composer 80 TCP SOAP messages if SSL is disabled for access to vCenter Servers or View Composer. View Connection Server * vCenter Server 443 TCP SOAP messages if SSL is enabled for access to vCenter Servers. View Connection Server * View Composer 18443 TCP SOAP messages if SSL is enabled for access to View Composer. View Connection Server * View Connection Server 4100 TCP JMS inter-router traffic. View Connection Server * View Connection Server 4101 TCP JMS SSL inter-router traffic. View Connection Server * View Connection Server 8472 TCP For interpod communication in Cloud Pod Architecture. View Connection Server * View Connection Server 22389 TCP For global LDAP replication in Cloud Pod Architecture. View Connection Server * View Connection Server 22636 TCP For secure global LDAP replication in Cloud Pod Architecture. View Connection Server * View Connection Server 32111 TCP Key sharing traffic. VMware, Inc. 16 View Security Table 3‑1. TCP and UDP Ports Used by View (Continued) Source Port Target Port Protoco l Unified Access Gateway appliance * View Connection Server or load balancer 443 TCP HTTPS access. Unified Access Gateway appliances connect on TCP port 443 to communicate with a View Connection Server instance or load balancer in front of multiple View Connection Server instances. View Composer service * ESXi host 902 TCP Used when View Composer customizes linked-clone disks, including View Composer internal disks and, if they are specified, persistent disks and system disposable disks. Description Note The UDP port number that clients use for PCoIP might change. If port 50002 is in use, the client will pick 50003. If port 50003 is in use, the client will pick port 50004, and so on. You must configure firewalls with ANY where an asterisk (*) is listed in the table. Note Microsoft Windows Server requires a dynamic range of ports to be open between all Connection Servers in the Horizon 7 environment. These ports are required by Microsoft Windows for the normal operation of Remote Procedure Call (RPC) and Active Directory replication. For more information about the dynamic range of ports, see the Microsoft Windows Server documentation. HTTP Redirection in View Connection attempts over HTTP are silently redirected to HTTPS, except for connection attempts to View Administrator. HTTP redirection is not needed with more recent Horizon clients because they default to HTTPS, but it is useful when your users connect with a Web browser, for example to download Horizon Client. The problem with HTTP redirection is that it is a non-secure protocol. If a user does not form the habit of entering https:// in the address bar, an attacker can compromise the Web browser, install malware, or steal credentials, even when the expected page is correctly displayed. Note HTTP redirection for external connections can take place only if you configure your external firewall to allow inbound traffic to TCP port 80. Connection attempts over HTTP to View Administrator are not redirected. Instead, an error message is returned indicating that you must use HTTPS. To prevent redirection for all HTTP connection attempts, see "Prevent HTTP Redirection for Client Connections to Connection Server" in the View Installation document. Connections to port 80 of a View Connection Server instance or security server can also take place if you off-load SSL client connections to an intermediate device. See "Off-load SSL Connections to Intermediate Servers" in the View Administration document. To allow HTTP redirection when the SSL port number was changed, see "Change the Port Number for HTTP Redirection to Connection Server" in the View Installation document. VMware, Inc. 17 View Security Services on a View Connection Server Host The operation of View depends on several services that run on a View Connection Server host. Table 3‑2. View Connection Server Host Services Service Name Startup Type Description VMware Horizon View Blast Secure Gateway Automatic Provides secure HTML Access and Blast Extreme services. This service must be running if clients connect to View Connection Server through the Blast Secure Gateway. VMware Horizon View Connection Server Automatic Provides connection broker services. This service must always be running. If you start or stop this service, it also starts or stops the Framework, Message Bus, Security Gateway, and Web services. This service does not start or stop the VMwareVDMDS service or the VMware Horizon View Script Host service. VMware Horizon View Framework Component Manual Provides event logging, security, and COM+ framework services. This service must always be running. VMware Horizon View Message Bus Component Manual Provides messaging services between the View components. This service must always be running. VMware Horizon View PCoIP Secure Gateway Manual Provides PCoIP Secure Gateway services. This service must be running if clients connect to View Connection Server through the PCoIP Secure Gateway. VMware Horizon View Script Host Disabled Provides support for third-party scripts that run when you delete virtual machines. This service is disabled by default. You should enable this service if you want to run scripts. VMware Horizon View Security Gateway Component Manual Provides common gateway services. This service must always be running. VMware Horizon View Web Component Manual Provides web services. This service must always be running. VMwareVDMDS Automatic Provides LDAP directory services. This service must always be running. During upgrades of View, this service ensures that existing data is migrated correctly. Services on a Security Server The operation of View depends on several services that run on a security server. Table 3‑3. Security Server Services Service Name Startup Type Description VMware Horizon View Blast Secure Gateway Automatic Provides secure HTML Access and Blast Extreme services. This service must be running if clients connect to this security server through the Blast Secure Gateway. VMware Horizon View Security Server Automatic Provides security server services. This service must always be running. If you start or stop this service, it also starts or stops the Framework and Security Gateway services. VMware, Inc. 18 View Security Table 3‑3. Security Server Services (Continued) Service Name Startup Type Description VMware Horizon View Framework Component Manual Provides event logging, security, and COM+ framework services. This service must always be running. VMware Horizon View PCoIP Secure Gateway Manual Provides PCoIP Secure Gateway services. This service must be running if clients connect to this security server through the PCoIP Secure Gateway. VMware Horizon View Security Gateway Component Manual Provides common gateway services. This service must always be running. VMware, Inc. 19 Configuring Security Protocols and Cipher Suites on a View Connection Server Instance or on a Security Server 4 You can configure the security protocols and cipher suites that are accepted by View Connection Server. You can define a global acceptance policy that applies to all View Connection Server instances in a replicated group, or you can define an acceptance policy for individual View Connection Server instances and security servers. You also can configure the security protocols and cipher suites that View Connection Server instances propose when connecting to vCenter Server and View Composer. You can define a global proposal policy that applies to all View Connection Server instances in a replicated group. You cannot define individual instances to opt out of a global proposal policy. Note The security settings for View Connection Server do not apply to Blast Secure Gateway (BSG). You must configure security for BSG separately. See Chapter 5 Configuring Security Protocols and Cipher Suites for Blast Secure Gateway. Oracle's Unlimited Strength Jurisdiction Policy files are included as standard, allowing 256-bit keys by default. This section includes the following topics: n Default Global Policies for Security Protocols and Cipher Suites n Configuring Global Acceptance and Proposal Policies n Configure Acceptance Policies on Individual Servers n Configure Proposal Policies on Remote Desktops n Older Protocols and Ciphers Disabled in View VMware, Inc. 20 View Security Default Global Policies for Security Protocols and Cipher Suites Global acceptance and proposal policies enable certain security protocols and cipher suites by default. Table 4‑1. Default Global Policies Default Security Protocols Default Cipher Suites n TLS 1.2 n TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 n TLS 1.1 n TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA n TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 n TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA n TLS_RSA_WITH_AES_128_CBC_SHA n TLS_RSA_WITH_AES_256_CBC_SHA GCM cipher suites are not enabled by default for performance reasons. Configuring Global Acceptance and Proposal Policies Global acceptance and proposal policies are defined in View LDAP attributes. These policies apply to all View Connection Server instances and security servers in a replicated group. To change a global policy, you can edit View LDAP on any View Connection Server instance. Each policy is a single-valued attribute in the following View LDAP location: cn=common,ou=global,ou=properties,dc=vdi,dc=vmware,dc=int Global Acceptance and Proposal Policies Defined in View LDAP You can edit the View LDAP attributes that define global acceptance and proposal policies. Global Acceptance Policies The following attribute lists security protocols. You must order the list by placing the latest protocol first: pae-ServerSSLSecureProtocols = \LIST:TLSv1.2,TLSv1.1,TLSv1 The following attribute lists the cipher suites. This example shows an abbreviated list: pae-ServerSSLCipherSuites = \LIST:TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256,TLS_RSA_WITH_AES_128_CBC_SHA The following attribute controls the precedence of cipher suites. Normally, the server's ordering of cipher suites is unimportant and the client's ordering is used. To use the server's ordering of cipher suites instead, set the following attribute: pae-ServerSSLHonorClientOrder = 0 VMware, Inc. 21 View Security Global Proposal Policies The following attribute lists security protocols. You must order the list by placing the latest protocol first: pae-ClientSSLSecureProtocols = \LIST:TLSv1.2,TLSv1.1,TLSv1 The following attribute lists the cipher suites. This list should be in order of preference. Place the most preferred cipher suite first, the second-most preferred suite next, and so on. This example shows an abbreviated list: pae-ClientSSLCipherSuites = \LIST:TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256,TLS_RSA_WITH_AES_128_CBC_SHA Change the Global Acceptance and Proposal Policies To change the global acceptance and proposal policies for security protocols and cipher suites, you use the ADSI Edit utility to edit View LDAP attributes. Prerequisites n Familiarize yourself with the View LDAP attributes that define the acceptance and proposal policies. See Global Acceptance and Proposal Policies Defined in View LDAP. n See the Microsoft TechNet Web site for information on how to use the ADSI Edit utility on your Windows Server operating system version. Procedure 1 Start the ADSI Edit utility on your View Connection Server computer. 2 In the console tree, select Connect to. 3 In the Select or type a Distinguished Name or Naming Context text box, type the distinguished name DC=vdi, DC=vmware, DC=int. 4 In the Select or type a domain or server text box, select or type localhost:389 or the fully qualified domain name (FQDN) of the View Connection Server computer followed by port 389. For example: localhost:389 or mycomputer.mydomain.com:389 5 Expand the ADSI Edit tree, expand OU=Properties, select OU=Global, and select OU=Common in the right pane. 6 On the object CN=Common, OU=Global, OU=Properties, select each attribute that you want to change and type the new list of security protocols or cipher suites. 7 Restart the Windows service VMware Horizon View Security Gateway Component on each Connection Server instance and security server if you modified pae-ServerSSLSecureProtocols. You do not need to restart any service after modifying pae-ClientSSLSecureProtocols. VMware, Inc. 22 View Security Configure Acceptance Policies on Individual Servers To specify a local acceptance policy on an individual Connection Server instance or security server, you must add properties to the locked.properties file. If the locked.properties file does not yet exist on the server, you must create it. You add a secureProtocols.n entry for each security protocol that you want to configure. Use the following syntax: secureProtocols.n=security protocol. You add an enabledCipherSuite.n entry for each cipher suite that you want to configure. Use the following syntax: enabledCipherSuite.n=cipher suite. The variable n is an integer that you add sequentially (1, 2, 3) to each type of entry. You add an honorClientOrder entry to control the precedence of cipher suites. Normally, the server's ordering of cipher suites is unimportant and the client's ordering is used. To use the server's ordering of cipher suites instead, use the following syntax: honorClientOrder=false Make sure that the entries in the locked.properties file have the correct syntax and the names of the cipher suites and security protocols are spelled correctly. Any errors in the file can cause the negotiation between the client and server to fail. Procedure 1 Create or edit the locked.properties file in the SSL gateway configuration folder on the Connection Server or security server computer. For example: install_directory\VMware\VMware View\Server\sslgateway\conf\ 2 Add secureProtocols.n and enabledCipherSuite.n entries, including the associated security protocols and cipher suites. 3 Save the locked.properties file. 4 Restart the VMware Horizon View Connection Server service or VMware Horizon View Security Server service to make your changes take effect. Example: Default Acceptance Policies on an Individual Server The following example shows the entries in the locked.properties file that are needed to specify the default policies: # The following list should be ordered with the latest protocol first: secureProtocols.1=TLSv1.2 secureProtocols.2=TLSv1.1 # This setting must be the latest protocol given in the list above: VMware, Inc. 23 View Security preferredSecureProtocol=TLSv1.2 # The order of the following list is unimportant unless honorClientOrder is false: enabledCipherSuite.1=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 enabledCipherSuite.2=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA enabledCipherSuite.3=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 enabledCipherSuite.4=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA enabledCipherSuite.5=TLS_RSA_WITH_AES_128_CBC_SHA enabledCipherSuite.6=TLS_RSA_WITH_AES_256_CBC_SHA # Use the client's ordering of cipher suites (ignores the ordering given above): honorClientOrder=true Configure Proposal Policies on Remote Desktops You can control the security of Message Bus connections to Connection Server by configuring the proposal policies on remote desktops that run Windows. Make sure that Connection Server is configured to accept the same policies to avoid a connection failure. Procedure 1 Start the Windows Registry Editor on the remote desktop. 2 Navigate to the HKEY_LOCAL_MACHINE\Software\VMware, Inc.\VMware VDM\Agent\Configuration registry key. 3 Add a new String (REG_SZ) value, ClientSSLSecureProtocols. 4 Set the value to a list of cipher suites in the format \LIST:protocol_1,protocol_2,.... List the protocols with the latest protocol first. For example: \LIST:TLSv1.2,TLSv1.1,TLSv1 5 Add a new String (REG_SZ) value, ClientSSLCipherSuites. 6 Set the value to a list of cipher suites in the format \LIST:cipher_suite_1,cipher_suite_2,.... The list should be in order of preference, with the most preferred cipher suite first. For example: \LIST:TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_RSA_WITH_AES_128_CBC_SHA VMware, Inc. 24 View Security Older Protocols and Ciphers Disabled in View Some older protocols and ciphers that are no longer considered secure are disabled in View by default. If required, you can enable them manually. DHE Cipher Suites For more information, see http://kb.vmware.com/kb/2121183. Cipher suites that are compatible with DSA certificates use Diffie-Hellman ephemeral keys, and these suites are no longer enabled by default, starting with Horizon 6 version 6.2. For Connection Server instances, security servers, and View desktops, you can enable these cipher suites by editing the View LDAP database, locked.properties file, or registry, as described in this guide. See Change the Global Acceptance and Proposal Policies, Configure Acceptance Policies on Individual Servers, and Configure Proposal Policies on Remote Desktops. You can define a list of cipher suites that includes one or more of the following suites, in this order: n TLS_DHE_DSS_WITH_AES_128_GCM_SHA256 (TLS 1.2 only, not FIPS) n TLS_DHE_DSS_WITH_AES_256_GCM_SHA384 (TLS 1.2 only, not FIPS) n TLS_DHE_DSS_WITH_AES_128_CBC_SHA256 (TLS 1.2 only) n TLS_DHE_DSS_WITH_AES_128_CBC_SHA n TLS_DHE_DSS_WITH_AES_256_CBC_SHA256 (TLS 1.2 only) n TLS_DHE_DSS_WITH_AES_256_CBC_SHA For View Composer and View Agent Direct-Connection (VADC) machines, you can enable DHE cipher suites by adding the following to the list of ciphers when you follow the procedure "Disable Weak Ciphers in SSL/TLS for View Composer and Horizon Agent Machines" in the View Installation document. TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 Note It is not possible to enable support for ECDSA certificates. These certificates have never been supported. SSLv3 In Horizon 7, SSL version 3.0 has been removed. For more information, see http://tools.ietf.org/html/rfc7568. RC4 For more information, see http://tools.ietf.org/html/rfc7465. VMware, Inc. 25 View Security For Connection Server instances, security servers, and View desktops, you can enable RC4 on a Connection Server, security server, or a Horizon Agent machine by editing the configuration file C:\Program Files\VMware\VMware View\Server\jre\lib\security\java.security. At the end of the file is a multi-line entry called jdk.tls.legacyAlgorithms. Remove RC4_128 and the comma that follows it from this entry and restart the Connection Server, security server, or the Horizon Agent machine, as the case may be. For View Composer and View Agent Direct-Connection (VADC) machines, you can enable RC4 by adding the following to the list of ciphers when you follow the procedure "Disable Weak Ciphers in SSL/TLS for View Composer and Horizon Agent Machines" in the View Installation document. TLS_RSA_WITH_RC4_128_SHA TLS 1.0 In Horizon 7, TLS 1.0 is disabled by default. For more information, see https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf and http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-52r1.pdf. For instructions on how to enable TLS 1.0, see the sections "Enable TLSv1 on vCenter Connections from Connection Server" and "Enable TLSv1 on vCenter and ESXi Connections from View Composer" in the View Upgrades document. VMware, Inc. 26 Configuring Security Protocols and Cipher Suites for Blast Secure Gateway 5 The security settings for View Connection Server do not apply to Blast Secure Gateway (BSG). You must configure security for BSG separately. Configure Security Protocols and Cipher Suites for Blast Secure Gateway (BSG) You can configure the security protocols and cipher suites that BSG's client-side listener accepts by editing the file absg.properties. The protocols that are allowed are, from low to high, tls1.0, tls1.1, and tls1.2. Older protocols such as SSLv3 and earlier are never allowed. Two properties, localHttpsProtocolLow and localHttpsProtocolHigh, determine the range of protocols that the BSG listener will accept. For example, setting localHttpsProtocolLow=tls1.0 and localHttpsProtocolHigh=tls1.2 will cause the listener to accept tls1.0, tls1.1, and tls1.2. The default settings are localHttpsProtocolLow=tls1.1 and localHttpsProtocolHigh=tls1.2. You can examine the BSG's absg.log file to discover the values that are in force for a specific BSG instance. You must specify the list of ciphers using the format that is defined in https://www.openssl.org/docs/manmaster/man1/ciphers.html, under the section CIPHER LIST FORMAT. The following cipher list is the default: ECDHE-RSA-AES256-SHA:AES256-SHA:HIGH:!AESGCM:!CAMELLIA:!3DES:!EDH:!EXPORT:!MD5:!PSK:!RC4:!SRP:!aNULL:! eNULL Procedure 1 On the Connection Server instance, edit the file install_directory\VMware\VMware View\Server\appblastgateway\absg.properties. By default, the install directory is %ProgramFiles%. VMware, Inc. 27 View Security 2 Edit the properties localHttpsProtocolLow and localHttpsProtocolHigh to specify a range of protocols. For example, localHttpsProtocolLow=tls1.0 localHttpsProtocolHigh=tls1.2 To enable only one protocol, specify the same protocol for both localHttpsProtocolLow and localHttpsProtocolHigh. 3 Edit the localHttpsCipherSpec property to specify a list of cipher suites. For example, localHttpsCipherSpec=ECDHE-RSA-AES256-SHA:HIGH:!AESGCM:!CAMELLIA:!3DES:!EDH:!EXPORT:!MD5:!PSK:! RC4:!SRP:!aNULL:!eNULL 4 Restart the Windows service VMware Horizon View Blast Secure Gateway. VMware, Inc. 28 Deploying USB Devices in a Secure Horizon 7 Environment 6 USB devices can be vulnerable to a security threat called BadUSB, in which the firmware on some USB devices can be hijacked and replaced with malware. For example, a device can be made to redirect network traffic or to emulate a keyboard and capture keystrokes. You can configure the USB redirection feature to protect your Horizon 7 deployment against this security vulnerability. By disabling USB redirection, you can prevent any USB devices from being redirected to your users' Horizon 7 desktops and applications. Alternatively, you can disable redirection of specific USB devices, allowing users to have access only to specific devices on their desktops and applications. The decision whether to take these steps depends on the security requirements in your organization. These steps are not mandatory. You can install USB redirection and leave the feature enabled for all USB devices in your Horizon 7 deployment. At a minimum, consider seriously the extent to which your organization should try to limit its exposure to this security vulnerability. This section includes the following topics: n Disabling USB Redirection for All Types of Devices n Disabling USB Redirection for Specific Devices Disabling USB Redirection for All Types of Devices Some highly secure environments require you to prevent all USB devices that users might have connected to their client devices from being redirected to their remote desktops and applications. You can disable USB redirection for all desktop pools, for specific desktop pools, or for specific users in a desktop pool. Use any of the following strategies, as appropriate for your situation: n When you install Horizon Agent on a desktop image or RDS host, deselect the USB redirection setup option. (The option is deselected by default.) This approach prevents access to USB devices on all remote desktops and applications that are deployed from the desktop image or RDS host. n In Horizon Administrator, edit the USB access policy for a specific pool to either deny or allow access. With this approach, you do not have to change the desktop image and can control access to USB devices in specific desktop and application pools. Only the global USB access policy is available for RDS desktop and application pools. You cannot set this policy for individual RDS desktop or application pools. VMware, Inc. 29 View Security n In View Administrator, after you set the policy at the desktop or application pool level, you can override the policy for a specific user in the pool by selecting the User Overrides setting and selecting a user. n Set the Exclude All Devices policy to true, on the Horizon Agent side or on the client side, as appropriate. n Use Smart Policies to create a policy that disables the USB redirection Horizon Policy setting. With this approach, you can disable USB redirection on a specific remote desktop if certain conditions are met. For example, you can configure a policy that disables USB redirection when users connect to a remote desktop from outside your corporate network. If you set the Exclude All Devices policy to true, Horizon Client prevents all USB devices from being redirected. You can use other policy settings to allow specific devices or families of devices to be redirected. If you set the policy to false, Horizon Client allows all USB devices to be redirected except those that are blocked by other policy settings. You can set the policy on both Horizon Agent and Horizon Client. The following table shows how the Exclude All Devices policy that you can set for Horizon Agent and Horizon Client combine to produce an effective policy for the client computer. By default, all USB devices are allowed to be redirected unless otherwise blocked. Table 6‑1. Effect of Combining Exclude All Devices Policies Exclude All Devices Policy on Horizon Agent Exclude All Devices Policy on Horizon Client Combined Effective Exclude All Devices Policy false or not defined (include all USB false or not defined (include all USB Include all USB devices devices) devices) false (include all USB devices) true (exclude all USB devices) Exclude all USB devices true (exclude all USB devices) Any or not defined Exclude all USB devices If you have set Disable Remote Configuration Download policy to true, the value of Exclude All Devices on Horizon Agent is not passed to Horizon Client, but Horizon Agent and Horizon Client enforce the local value of Exclude All Devices. These policies are included in the Horizon Agent Configuration ADMX template file (vdm_agent.admx). For more information, see "USB Settings in the Horizon Agent Configuration ADMX Template" in Configuring Remote Desktop Features in Horizon 7. Disabling USB Redirection for Specific Devices Some users might have to redirect specific locally-connected USB devices so that they can perform tasks on their remote desktops or applications. For example, a doctor might have to use a Dictaphone USB device to record patients' medical information. In these cases, you cannot disable access to all USB devices. You can use group policy settings to enable or disable USB redirection for specific devices. Before you enable USB redirection for specific devices, make sure that you trust the physical devices that are connected to client machines in your enterprise. Be sure that you can trust your supply chain. If possible, keep track of a chain of custody for the USB devices. VMware, Inc. 30 View Security In addition, educate your employees to ensure that they do not connect devices from unknown sources. If possible, restrict the devices in your environment to those that accept only signed firmware updates, are FIPS 140-2 Level 3-certified, and do not support any kind of field-updatable firmware. These types of USB devices are hard to source and, depending on your device requirements, might be impossible to find. These choices might not be practical, but they are worth considering. Each USB device has its own vendor and product ID that identifies it to the computer. By configuring Horizon Agent Configuration group policy settings, you can set an include policy for known device types. With this approach, you remove the risk of allowing unknown devices to be inserted into your environment. For example, you can prevent all devices except a known device vendor and product ID, vid/pid=0123/abcd, from being redirected to the remote desktop or application: ExcludeAllDevices Enabled IncludeVidPid o:vid-0123_pid-abcd Note This example configuration provides protection, but a compromised device can report any vid/pid, so a possible attack could still occur. By default, Horizon 7 blocks certain device families from being redirected to the remote desktop or application. For example, HID (human interface devices) and keyboards are blocked from appearing in the guest. Some released BadUSB code targets USB keyboard devices. You can prevent specific device families from being redirected to the remote desktop or application. For example, you can block all video, audio, and mass storage devices: ExcludeDeviceFamily o:video;audio;storage Conversely, you can create a whitelist by preventing all devices from being redirected but allowing a specific device family to be used. For example, you can block all devices except storage devices: ExcludeAllDevices Enabled IncludeDeviceFamily o:storage Another risk can arise when a remote user logs into a desktop or application and infects it. You can prevent USB access to any Horizon 7 connections that originate from outside the company firewall. The USB device can be used internally but not externally. Be aware that if you block TCP port 32111 to disable external access to USB devices, time zone synchronization will not work because port 32111 is also used for time zone synchronization. For zero clients, the USB traffic is embedded inside a virtual channel on UDP port 4172. Because port 4172 is used for the display protocol as well as for USB redirection, you cannot block port 4172. If required, you can disable USB redirection on zero clients. For details, see the zero client product literature or contact the zero client vendor. VMware, Inc. 31 View Security Setting policies to block certain device families or specific devices can help to mitigate the risk of being infected with BadUSB malware. These policies do not mitigate all risk, but they can be an effective part of an overall security strategy. These policies are included in the Horizon Agent Configuration ADMX template file (vdm_agent.admx). For more information, see Configuring Remote Desktop Features in Horizon 7. VMware, Inc. 32 HTTP Protection Measures on Connection Servers and Security Servers 7 Horizon 7 employs certain measures to protect communication that uses the HTTP protocol. This section includes the following topics: n Internet Engineering Task Force Standards n World Wide Web Consortium Standards n Other Protection Measures n Configure HTTP Protection Measures Internet Engineering Task Force Standards Connection Server and security server comply with certain Internet Engineering Task Force (IETF) standards. n RFC 5746 Transport Layer Security (TLS) – Renegotiation Indication Extension, also known as secure renegotiation, is enabled by default. Note Client-initiated renegotiation is disabled by default on Connection Servers and security servers. To enable, edit registry value [HKLM\SOFTWARE\VMware, Inc.\VMware VDM\plugins\wsnm\TunnelService\Params]JvmOptions and remove -Djdk.tls.rejectClientInitiatedRenegotiation=true from the string. n RFC 6797 HTTP Strict Transport Security (HSTS), also known as transport security, is enabled by default. This setting cannot be disabled. n RFC 7034 HTTP Header Field X-Frame-Options, also known as counter clickjacking, is enabled by default. You can disable it by adding the entry x-frame-options=OFF to the file locked.properties. For information on how to add properties to the file locked.properties, see Configure HTTP Protection Measures. Note In releases earlier than Horizon 7 version 7.2, changing this option did not affect connections to HTML Access. VMware, Inc. 33 View Security n RFC 6454 Origin Checking, which protects against cross-site request forging, is enabled by default. You can disable it by adding the entry checkOrigin=false to locked.properties. For more information, see Cross-Origin Resource Sharing. Note In earlier releases, this protection was disabled by default. World Wide Web Consortium Standards Connection Server and security server comply with certain World Wide Web Consortium (W3) standards. n Cross-Origin Resource Sharing (CORS), which constrains client-side cross-origin requests, is enabled by default. You can disable it by adding the entry enableCORS=false to locked.properties. n Content Security Policy (CSP), which mitigates a broad class of content injection vulnerabilities, is enabled by default. You can disable it by adding the entry enableCSP=false to locked.properties. Cross-Origin Resource Sharing The Cross-Origin Resource Sharing (CORS) feature regulates client-side cross-origin requests by providing policy statements to the client on demand and by checking requests for compliance with the policy. This feature is enabled by default. Policies include the set of HTTP methods that can be accepted, where requests can originate, and which content types are valid. These vary according to the request URL, and can be reconfigured as needed by adding entries to locked.properties. An ellipsis after a property name indicates that the property can accept a list. Table 7‑1. CORS Properties Property Value Type Master Default Other Defaults enableCORS true true n/a application/x-www-formurlencoded,application/x ml,text/xml n admin=application/xamf n helpdesk=applicatio false acceptContentType... http-content-type n/json,application/te xt,application/x-wwwform-urlencoded n acceptHeader... http-header-name * n/a exposeHeader... http-header-name * n/a filterHeaders true true n/a view-vlsirest=application/json false VMware, Inc. 34 View Security Table 7‑1. CORS Properties (Continued) Property Value Type Master Default Other Defaults checkOrigin true true n/a false admin=true false allowCredentials true false broker=true helpdesk=true misc=true portal=true saml=true tunnel=true view-vlsi=true view-vlsi-rest=true allowMethod... http-method-name GET,HEAD,POST misc=GET,HEAD saml=GET,HEAD allowPreflight true true n/a false maxAge cache-time 0 n/a balancedHost load-balancer-name OFF n/a portalHost... gateway-name OFF n/a chromeExtension... chrome-extension-hash OFF n/a Example CORS properties in the locked.properties file: enableCORS = true allowPreflight = true checkOrigin = true checkOrigin-misc = false allowMethod.1 = GET allowMethod.2 = HEAD allowMethod.3 = POST allowMethod-saml.1 = GET allowMethod-saml.2 = HEAD acceptContentType.1 = application/x-www-form-urlencoded acceptContentType.2 = application/xml acceptContentType.3 = text/xml Origin Checking Origin checking is enabled by default. When it is enabled, a request will be accepted only without an Origin, or with an Origin equal to the address given in the External URL, to the balancedHost address, to any portalHost address, to any chromeExtension hash, to null, or to localhost. If Origin is not one of these possibilities, then an error "Unexpected Origin" is logged and a status of 404 is returned. If multiple Connection Servers or security servers are load balanced, you must specify the load balancer address by adding a balancedHost entry to locked.properties. Port 443 is assumed for this address. VMware, Inc. 35 View Security If clients need to connect through a Unified Access Gateway or another gateway, you must specify all of the gateway addresses by adding portalHost entries to locked.properties. Port 443 is assumed for these addresses too. Do the same if you want to provide access to a Connection Server or security server by a name that is different from the one that is specified in the External URL. Chrome Extension clients set their initial Origin to their own identity. To allow connections to succeed, register the extension by adding a chromeExtension entry to locked.properties. Content Security Policy The Content Security Policy (CSP) feature mitigates a broad class of content injection vulnerabilities, such as cross-site scripting (XSS), by providing policy directives to compliant browsers. This feature is enabled by default. You can reconfigure the policy directives by adding entries to locked.properties. Table 7‑2. CSP Properties Property Value Type Master Default Other Defaults enableCSP true true n/a false content-security-policy directives-list default-src 'self';script-src 'self' 'unsafe-inline' 'unsafeeval' data:;style-src 'self' 'unsafeinline';font-src 'self' data: portal=child-src 'self' blob:;default-src 'self';connect-src 'self' wss:;font-src 'self' data:;img-src 'self' data: blob:;media-src 'self' blob:;object-src 'self' blob:;script-src 'self' 'unsafe-inline' 'unsafe-eval' data:;style-src 'self' 'unsafe-inline';frameancestors 'self' x-frame-options OFF deny portal=sameorigin nosniff n/a 1; mode=block n/a specification x-content-type-options OFF specification x-xss-protection OFF specification You can add CSP properties to the locked.properties file. Example CSP properties: enableCSP = true content-security-policy = default-src 'self';script-src 'self' data: content-security-policy-portal = default-src 'self';frame-ancestors 'self' x-frame-options = deny x-frame-options-portal = sameorigin x-xss-protection = 1; mode=block VMware, Inc. 36 View Security Other Protection Measures Besides the Internet Engineering Task Force and W3 standards, Horizon 7 employs other measures to protect communication that uses the HTTP protocol. Reducing MIME Type Security Risks By default, Horizon 7 sends the header x-content-type-options: nosniff in its HTTP responses to help prevent attacks based on MIME-type confusion. You can disable this feature by adding the following entry to the file locked.properties: x-content-type-options=OFF Mitigating Cross-Site Scripting Attacks By default, Horizon 7 employs the XSS (cross-site scripting) Filter feature to mitigate cross-site scripting attacks by sending the header x-xss-protection=1; mode=block in its HTTP responses. You can disable this feature by adding the following entry to the file locked.properties: x-xss-protection=OFF Content Type Checking By default, Horizon 7 accepts requests with the following declared content types only: n application/x-www-form-urlencoded n application/xml n text/xml Note In earlier releases, this protection was disabled by default. To restrict the content types that View accepts, add the following entry to the file locked.properties: acceptContentType.1=content-type For example: acceptContentType.1=x-www-form-urlencoded To accept another content type, add the entry acceptContentType.2=content-type, and so on VMware, Inc. 37 View Security To accept requests with any declared content type, specify acceptContentType=*. Note In releases earlier than Horizon 7 version 7.2, changing this list does not affect connections to Horizon Administrator. Handshake Monitoring TLS handshakes on port 443 must complete within a configurable period, otherwise they will be forcibly terminated. By default, this period is 10 seconds. If smart card authentication is enabled, TLS handshakes on port 443 can complete within 100 seconds. If required, you can adjust the time for TLS handshakes on port 443 by adding the following property to the locked.properties file: handshakeLifetime = lifetime_in_seconds For example: handshakeLifetime = 20 Optionally, the client that is responsible for an over-running TLS handshake can be automatically added to a blacklist. New connections from blacklisted clients are delayed for a configurable period before being processed so that connections from other clients take priority. You can enable this feature by adding the following property to the locked.properties file: secureHandshakeDelay = delay_in_milliseconds For example: secureHandshakeDelay = 2000 To disable blacklisting of HTTPS connections, remove the secureHandshakeDelay entry or set it to 0. The IP address of a misbehaving client is added to the blacklist for a minimum period equal to the sum of handshakeLifetime and secureHandshakeDelay. Using the values in the examples above, the IP address of a misbehaving client is 22 seconds (20 * 1000) + 2000 = 22 seconds The minimum period is extended each time a connection from the same IP address misbehaves. The IP address is removed from the blacklist after the minimum period has expired and after the last delayed connection from that IP address has been processed. VMware, Inc. 38 View Security A TLS handshake over-run is not the only reason to blacklist a client. Other reasons include a series of abandoned connections, or a series of requests ending in error, such as multiple attempts to access nonexistent URLs. These various triggers have differing minimum blacklist periods. To extend monitoring of these additional triggers to port 80, add the following entry to the locked.properties file: insecureHandshakeDelay = delay_in_milliseconds For example: insecureHandshakeDelay = 1000 To disable blacklisting of HTTP connections, remove the insecureHandshakeDelay entry or set it to 0. User Agent Whitelisting Set a whitelist to restrict user agents that can interact with Horizon 7. By default, all user agents are accepted. Note This is not strictly a security feature. User agent detection relies on the user-agent request header provided by the connecting client or browser, which can be spoofed. Some browsers allow the request header to be modified by the user. A user agent is specified by its name and a minimum version. For example: clientWhitelist-portal.1 = Chrome-14 clientWhitelist-portal.2 = Safari-5.1 This means that only Google Chrome version 14 and later, and Safari version 5.1 and later are allowed to connect using HTML Access. All browsers can connect to other services. You can enter the following recognised user agent names: n Android n Chrome n Edge n IE n Firefox n Opera n Safari Note Not all of these user agents are supported by Horizon 7. These are examples. VMware, Inc. 39 View Security Configure HTTP Protection Measures To configure HTTP protection measures you must create or edit the locked.properties file in the SSL gateway configuration folder on the Connection Server or security server instance. For example: install_directory\VMware\VMware View\Server\sslgateway\conf\locked.properties n Use the following syntax to configure a property in locked.properties: myProperty = newValue n The property name is always case-sensitive and the value might be case-sensitive. Whitespace around the = sign is optional. n For CORS and CSP properties, it is possible to set service-specific values as well as a master value. For example, the admin service is responsible for handling Horizon Administrator requests, and a property can be set for this service without affecting other services by appending -admin after the property name. myProperty-admin = newValueForAdmin n If both a master value and a service-specific value are specified, then the service-specific value applies to the named service, and the master value applies to all other services. The sole exception to this is the special value "OFF". If the master value for a property is set to "OFF", then all servicespecific values for this property are ignored. For example: myProperty = OFF myProperty-admin = newValueForAdmin n ; ignored Some properties can accept a list of values. To set a single value, enter the following property: myProperty = newValue myProperty-admin = newValueForAdmin To set multiple values for a property that accepts list values, you can specify each value on a separate line: myProperty.1 = newValue1 myProperty.2 = newValue2 myProperty-admin.1 = newValueForAdmin1 myProperty-admin.2 = newValueForAdmin2 VMware, Inc. 40 View Security n To determine the correct service name to use when making a service-specific configuration, look in the debug logs for lines containing the following sequence: (ajp:admin:Request21) Request from abc.def.com/10.20.30.40: GET /admin/ In this example, the service name is admin. You can use the following typical service names: n admin for Horizon Administrator n broker for Connection Server n docroot for Local file serving n helpdesk for Helpdesk n portal for HTML Access n saml for SAML communication (vIDM) n tunnel for Secure Tunnel n view-vlsi for View API n misc for Other VMware, Inc. 41
Source Exif Data:
File Type : PDF File Type Extension : pdf MIME Type : application/pdf PDF Version : 1.5 Linearized : No Author : VMware, Inc. Create Date : 2017:12:15 11:00:03-08:00 Modify Date : 2017:12:15 11:00:03-08:00 Creator : AH XSL Formatter V6.3 MR1 for Windows (x64) : 6.3.2.23978 (2016/03/18 11:26JST) Producer : Antenna House PDF Output Library 6.3.762 (Windows (x64)) Keywords : vmwareview , security., reference , view manager., view composer , view client., view agent , vsphere., viewcomposer Title : View Security - VMware. Horizon 7 7.4 Trapped : False Page Count : 41 Page Mode : UseOutlines Page Layout : SinglePage Language : ENEXIF Metadata provided by EXIF.tools