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
Access the Full Program Neighborhood client on the workstation and perform the following: 1. Select Start > Citrix > Citrix Access Clients > Program Neighborhood 2. Right Click on the selected application (s). 3. Under the Address List, verify that Fully Qualified Domain Names listed match the certificates of the XenApp servers within the enclave. If they are not listed, this is a finding.
Configure all Program Neighborhood clients with specific FQDN of the XenApp servers in the Address List.
There are two ways to verify that client drive mappings are disabled. Each is listed below. Access the XenApp server and perform the following: Method 1 1. Select Start > Administrative Tools > Terminal Services Configuration > ICA-tcp 2. Select the Client Settings tab and verify that “Connect client drives at logon” is not checked. If it is, this is a finding. Method 2 1. Access the Local Computer Policy and Import the Citrix Presentation Server Client template (icaclient.adm). 2. Navigate to the Computer Configuration > Administrative Templates > Citrix Components > Presentation Server Client > Remoting client devices 3. Verify that “Client drive mapping” is set to Disabled. If not, this is a finding.
Disable Client drive mappings on all Program Neighborhood clients.
There are two ways to verify that the clipboard mapping is disabled. Each is listed below. Method 1 Access the XenApp server and perform the following: 1. Select Start > Administrative Tools > Terminal Services Configuration > ICA-tcp 2. Select the Client Settings tab and verify that “Clipboard mapping” is checked. If it is not checked, this is a finding. Method 2 1. Access the Local Computer Policy and Import the Citrix Presentation Server Client template (icaclient.adm). 2. Navigate to the Computer Configuration > Administrative Templates > Citrix Components > Presentation Server Client > Clipboard 3. Verify that “Clipboard” is set to Disabled. If not, this is a finding.
Disable Clipboard mapping on all Program Neighborhood clients.
To verify the bitmap disk caching is disabled, perform the following: 1. Using a text editor, open the Appsrv.ini file located in the C:\Documents and Settings\Application Data\ICA Client directory. 2. Under the [WFClient] section, verify the value is set to ‘PersistentCacheEnabled=Off’. If it is not set to off, this is a finding.
Disable Bitmap Disk Caching.
To configure the Program Neighborhood Client to utilize SSL/TLS perform the following steps: 1. Select Start > All Programs > Citrix > Citrix Access Clients > Program Neighborhood. 2. Right click the application set and select Application Set Settings. 3. In the Settings dialog box, verify SSL/TLS+HTTPS is selected from the Network Protocol menu. If not, this is a finding. OR 1. Exit the Program Neighborhood client if it is running. Make sure all client components, including the Connection Center, are closed. 2. Open the individual’s user-level Appsrv.ini file (default directory: %User Profile%\Application Data\ICAClient) in a text editor. 3. Locate the section named [WFClient]. 4. Verify the values of these three parameters below: SSLCIPHERS= GOV SECURECHANNELPROTOCOL= TLS SSLEnable=On 5. If any of these three values are incorrect or missing, this is a finding.
Configure SSL/TLS+HTTPS for the ICA client.
1. Select Start > All Programs > Citrix > Citrix Access Clients > Program Neighborhood. 2. Navigate to Help > About Program Neighborhood 3. If the Program Neighborhood version is not at 10.200 or higher, this is a finding.
Upgrade Program Neighborhood clients to the required minimum version.
On the ICA workstation perform the following: 1. Select Start > All Programs > Citrix > Citrix Access Clients > Program Neighborhood. 2. Select the Logon Information tab and verify that Smart Card is selected. If not, this is a finding.
Enable Smart Card for ICA Program Neighborhood clients.
On the ICA workstation, perform the following: 1. Select Start > All Programs > Citrix > Citrix Access Clients > Program Neighborhood. 2. Select the Logon Information tab and verify that Pass thru authentication is not checked under Smart Card. If it is, this is a finding. OR 1. Access the Appsrv.ini file located in users’ profiles to check whether pass-thru is configured. For instance, if a user’s profile is stored locally, this file is located in C:\Documents and Settings\user\Application Data\ICAClient. 2. In the [WFClient] section, verify the following entries do not exist: EnableSSOnThruICAFile=On SSOnUserSetting=On If these two entries exist, this is a finding.
Disable smart-card pass thru authentication.
Enabling smart card support for Program Neighborhood Agent is done through the Web Interface. On the XenApp Server perform the following: 1. Select Start > All Programs > Citrix > Management Consoles > Access Management Console 2. Navigate to Citrix Resources > Configuration Tools > Web Interface > (PNAgent Website Name) 3. Right Click on the config.xml and select Change Authentication Methods. 4. Verify that “Smart Card” is checked. If it is not, this is a finding.
Enable Smart Card for ICA Program Neighborhood Agents.
To verify that TLS protocol is configured, perform the following on the XenApp server: 1. Select Start > All Programs > Citrix > Management Consoles > Access Management Console 2. Navigate to Citrix Resources > Configuration Tools > Web Interface > (PNAgent Website Name) 3. Right Click on the config.xml and select Manage Server Settings. 4. Verify that “Use SSL/TLS for communications between clients and the Web server” is checked. If it is, this is a finding.
Use TLS for all communications between the Program Neighborhood Agent and the Web server.
On the XenApp Server perform the following: 1. Select Start > All Programs > Citrix > Management Consoles > Access Management Console 2. Navigate to Citrix Resources > Configuration Tools > Web Interface > (PNAgent Website Name) 3. Right Click on the config.xml and select Manage Server Settings. 4. Verify that “Allow users to customize the server URL” is unchecked. If it is, this is a finding.
Disable the option to change server URLs.