We can't guarantee quick solutions - Experts Exchange isn't a help desk. We're a community of IT professionals committed to sharing knowledge. Our experts volunteer their time to help other people in the technology industry learn and succeed. Plans and Pricing. Contact Us. Certified Expert Program. Credly Partnership. Udemy Partnership. Privacy Policy. Citrix is providing these links to you only as a convenience, and the inclusion of any link does not imply endorsement by Citrix of the linked Web site.
It is your responsibility to take precautions to ensure that whatever Web site you use is free of viruses or other harmful items. Was this page helpful? Thank you! Sorry to hear that. Name Name is required. Email Email address is required. Close Submit. Network analysis. Delegated Administration and Director. Secure Director deployment. Configure with Citrix Analytics for Performance.
Site analytics. Alerts and notifications. Filters data. Historical trends. Troubleshoot deployments. User issues. Feature compatibility matrix. Data granularity and retention. Troubleshoot Director failure reasons. Third party notices. Document History. Aviso legal. Este texto foi traduzido automaticamente. Este artigo foi traduzido automaticamente. Your organization may need to meet specific security standards to satisfy regulatory requirements. This document does not cover this subject, because such security standards change over time.
Keep all machines in your environment up to date with security patches. One advantage is that you can use thin clients as terminals, which simplifies this task. Protect all machines in your environment with perimeter firewalls, including at enclave boundaries as appropriate.
If you are migrating a conventional environment to this release, you may need to reposition an existing perimeter firewall or add new perimeter firewalls. For example, suppose there is a perimeter firewall between a conventional client and database server in the data center. When this release is used, that perimeter firewall must be placed so that the virtual desktop and user device are on one side, and the database servers and Delivery Controllers in the data center are on the other side.
Therefore, consider creating an enclave within your data center to contain the database servers and Controllers. Also consider having protection between the user device and the virtual desktop. All machines in your environment should be protected by a personal firewall. When you install core components and VDAs, you can choose to have the ports required for component and feature communication opened automatically if the Windows Firewall Service is detected even if the firewall is not enabled.
You can also choose to configure those firewall ports manually. If you use a different firewall, you must configure the firewall manually. TCP ports and are used for ICA and CGP and are therefore likely to be open at firewalls so that users outside the data center can access them. Citrix recommends that you do not use these ports for anything else, to avoid the possibility of inadvertently leaving administrative interfaces open to attack.
All network communications should be appropriately secured and encrypted to match your security policy. You can secure all communication between Microsoft Windows computers using IPSec; refer to your operating system documentation for details about how to do this. In addition, communication between user devices and desktops is secured through Citrix SecureICA, which is configured by default to bit encryption.
You can also secure network communications between user devices and desktops using TLS. Apply Windows best practice for account management.
Do not create an account on a template or image before it is duplicated by Machine Creation Services or Provisioning Services. Do not schedule tasks using stored privileged domain accounts. Do not manually create shared Active Directory machine accounts. To prevent non-admin users from performing malicious actions, we recommend that you configure Windows AppLocker rules for installers, applications, executables and scripts on the VDA host and on the local Windows client.
Grant users only the capabilities they require. Microsoft Windows privileges continue to be applied to desktops in the usual way: configure privileges through User Rights Assignment and group memberships through Group Policy.
One advantage of this release is that it is possible to grant a user administrative rights to a desktop without also granting physical control over the computer on which the desktop is stored.
Logon rights are required for both user accounts and computer accounts. As with Microsoft Windows privileges, logon rights continue to be applied to desktops in the usual way: configure logon rights through User Rights Assignment and group memberships through Group Policy. The Windows logon rights are: log on locally, log on through Remote Desktop Services, log on over the network access this computer from the network , log on as a batch job, and log on as a service.
For computer accounts, grant computers only the logon rights they require. Consider the following approach:. Refer to Microsoft documentation for more information. Delivery Controller installation also creates the following Windows services. These are also created when installed with other Citrix components:. Delivery Controller installation also creates the following Windows service. This is not currently used. If it has been enabled, disable it. Delivery Controller installation also creates these following Windows services.
These are not currently used, but must be enabled. Do not disable them. Except for the Citrix Storefront Privileged Administration Service, these services 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.
You do not need to change these user rights. These privileges are not used by the Delivery Controller and are automatically disabled. Do not alter these service settings. This allows Local Host Cache to work correctly. Do not alter its service settings. You can disable the Citrix Telemetry Service. Apart from this service, and services that are already disabled, do not disable any other of these Delivery Controller Windows services.
It is no longer necessary to enable creation of 8. The registry key NtfsDisable8dot3NameCreation can be configured to disable creation of 8. You can also configure this using the fsutil.
Your user environment can contain either user devices that are unmanaged by your organization and completely under the control of the user, or user devices that are managed and administered by your organization. The security considerations for these two environments are generally different. Managed user devices are under administrative control; they are either under your own control, or the control of another organization that you trust. You may configure and supply user devices directly to users; alternatively, you may provide terminals on which a single desktop runs in full-screen-only mode.
Follow the general security best practices described above for all managed user devices. This release has the advantage that minimal software is required on a user device.
0コメント