Citrix Virtual Apps and Desktop 7.x Workspace App Security Technical Implementation Guide
Pick two releases to diff their requirements.
Open a previous version of this STIG.
- RMF Control
- AC-17
- Severity
- H
- CCI
- CCI-000068
- Version
- CVAD-WS-000030
- Vuln IDs
-
- V-234261
- Rule IDs
-
- SV-234261r640180_rule
Checks: C-37446r640178_chk
Note: For connections that are not remote, this is Not Applicable. Verify encryption has been enabled on devices running Citrix Workspace: Open the Citrix Workspace Group Policy Object administrative template by running gpedit.msc. 1. Launch the Citrix Workspace Group Policy Object administrative template using the Group Policy Management Console. 2. Under the Computer Configuration node, go to Administrative Templates >> Citrix Workspace >> Network routing and select the TLS and Compliance Mode Configuration policy. 3. Verify the policy is enabled. If the policy is not enabled, this is a finding. 4. Verify the following policy options are selected: - Verify "Require TLS for all connections" is selected. - From the Security Compliance Mode drop-down, verify "SP800-52" is selected. - Verify "Full access check and CRL required" is selected. - Verify "Enable FIPS: is selected. - From the Allow TLS Servers drop-down, verify the desired port number is entered. - Verify "TLS 1.2" is selected. - From the TLS cipher suite drop-down, verify "Select Government (GOV)" is selected. - From the Certificate Revocation Check Policy drop-down, select the policy required by your Organizational Security Policy. If any of the policy options noted above are not selected, this is a finding.
Fix: F-37411r640179_fix
Note: For connections that are not remote, this is Not Applicable. As an administrator, open the Citrix Workspace Group Policy Object administrative template by running gpedit.msc. Apply the policy on a domain OU containing User Devices running Windows Receiver. 1. Launch the Citrix Workspace Group Policy Object administrative template using the Group Policy Management Console. 2. Under the Computer Configuration node, go to Administrative Templates >> Citrix Workspace >> Network routing and select the TLS and Compliance Mode Configuration policy. 3. Select "Enabled" to enable secure connections and to encrypt communication on the server. Set the following options: - Select "Require TLS" for all connections to force Citrix Workspace for Windows to use TLS for all connections to published applications and desktops. - From the Security Compliance Mode drop-down, select the option: SP800-52 – Select SP800-52 for compliance with NIST SP 800-52. - Select Full access check and CRL required. 4. Enable FIPS - Select this option to enforce the use of FIPS-approved cryptography. You must also enable the Windows security option from the operating system group policy, System Cryptography: Use FIPS-compliant algorithms for encryption, hashing, and signing. Otherwise, Citrix Workspace for Windows might fail to connect to published applications and desktops. 5. From the Allow TLS Servers drop-down, select the port number. Ensure that Citrix Workspace connects only to a specified server by using a comma-separated list. Wildcards and port numbers can be specified. For example, *.citrix.com:4433 allows connections to any server whose common name ends with .citrix.com on port 4433. The issuer of the certificate asserts the accuracy of the information in a security certificate. If Citrix Workspace does not recognize and trust the issuer, the connection is rejected. 6. From the TLS version drop-down, select "TLS 1.2". 7. TLS cipher suite - Select "Government (GOV)". 8. From the Certificate Revocation Check Policy drop-down, select the policy required by the Organizational Security Policy.
- RMF Control
- IA-2
- Severity
- M
- CCI
- CCI-001953
- Version
- CVAD-WS-000855
- Vuln IDs
-
- V-234262
- Rule IDs
-
- SV-234262r640183_rule
Checks: C-37447r640181_chk
Verify the policy value for Administrative Templates >> Citrix Components >> Citrix Workspace >> User authentication >> "Smart card authentication" is not set to "Disabled". For this setting, "Not Configured" is equivalent to "Enabled". If the "Smart card authentication" policy is set to "Disabled", this is a finding.
Fix: F-37412r640182_fix
Set the policy value for Administrative Templates >> Citrix Components >> Citrix Workspace >> User authentication >> "Smart card authentication" to "Enabled" and check the "Allow smart card authentication" box. If the environment leverages PIN pass-through, also check the "Use pass-through authentication for PIN" box.