Select any two versions of this STIG to compare the individual requirements
Select any old version/release of this STIG to view the previous requirements
A DoD approved VPN, or gateway/proxy, must be leveraged to access the Windows VDA from a remote network. This VPN, or gateway, must handle user authentication and tunneling of Citrix traffic. The VPN, or gateway, must meet the DoD encryption requirements, such as FIPS 140-2, for the environment. If no VPN, or gateway/proxy, is used for remote access to the VDA, this is a finding. If the VPN, or gateway/proxy, does not authenticate the remote user before providing access to the VDA, this is a finding. If the VPN, or gateway/proxy, fails to meet the DoD encryption requirements for the environment, this is a finding.
Implement a DoD-approved VPN or gateway/proxy that will authenticate user access and tunnel/proxy traffic to the Windows VDA. Ensure the VPN or gateway/proxy is configured to authenticate the user before accessing the environment, and meets the DoD encryption requirements, such as FIPS 140-2, for the environment.
Some organizations consider port 80 to be a non-secure port regardless of the protocol. Ensure VDA registration traffic to the Delivery Controller is occurring on an approved port. To verify the Delivery Controller is using an approved port, perform the following: 1. On each the Delivery Controller, open a command prompt. 2. Navigate to the Citrix install directory Program Files\Citrix\Broker\Service. 3. Run the command "BrokerService.exe /Show" to display the currently used "VDA Port". 4. Ensure the port in use on each Delivery Controller matches and is approved by the DoD organization. To verify the Windows VDA is using the approved port for registration, perform the following: 1. In Active Directory, open the Group Policy object used to apply VDA settings to the Windows VDA. 2. Navigate to Computer Configuration >> Policies >> Citrix Policies. 3. Edit the "Unfiltered Policy", or the custom policy used to apply Delivery Controller settings in the GPO. 4. Under the "Settings" tab, find the Virtual Delivery Agent Setting called "Controller registration port". 5. Ensure the port number matches the approved port set on the Delivery Controller. If an unapproved port is used, this is a finding.
Some organizations consider port 80 to be a non-secure port regardless of the protocol. It is necessary to set the Delivery Controller and VDAs to use an approved port for registration traffic. To set the registration port on the broker to an approved port (e.g., 8080) perform the following: 1. On each the Delivery Controller, open a command prompt. 2. Navigate to the Citrix install directory Program Files\Citrix\Broker\Service. 3. Run the command "BrokerService.exe -VDAPort 8080" to set the registration port to 8080. Replace 8080 with an approved port in the organization. 4. Run the command "BrokerService.exe /Show" to verify the VDA Port is changed. To configure the Windows VDA to use the approved port set on the Delivery Controller, perform the following: 1. In Active Directory, open the Group Policy object used to apply VDA settings to the Windows VDA. If this GPO does not yet exist, create it. 2. Navigate to Computer Configuration >> Policies >> Citrix Policies. 3. Edit the "Unfiltered Policy” or create a custom Citrix policy to apply Delivery Controller settings in the GPO. 4. Under the "Settings" tab, find the Virtual Delivery Agent Setting called "Controller registration port". 5. Click "Add" to enable the setting and specify the approved port set on the Delivery Controller. 6. Ensure this GPO is linked to the OUs with the relevant Windows VDAs.