Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 24.11

Citrix Receiver Windows Desktop Lock

General Information

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website:	Go to site
Description:	Citrix Receiver Windows Desktop Lock utilizes Citrix Receiver in order to launch a published desktop with pass-through authentication configured within the virtual client. This entry covers the Desktop Edition of this technology and not any mobile versions. See Category tab/Comparable for the corresponding Mobile entry. Note: The implementation of mobile technology applications that operate on Mobile Operating Systems must be reviewed and authorized by the Mobile Technology and Endpoint Security Engineering Team: http://vaww.eie.va.gov/SysDesign/CS/MT/default.aspx Note: Beginning August 2018, Citrix Workspace app replaces Citrix Receiver. While you can still download older versions of Citrix Receiver, new features and enhancements are released for Citrix Workspace app. Citrix Workspace app is a new client from Citrix that works similar to Citrix Receiver and is fully backward-compatible with your organization’s Citrix infrastructure. Citrix Workspace app provides the full capabilities of Citrix Receiver, and new capabilities based on your organization’s Citrix deployment.
Technology/Standard Usage Requirements:	Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Information:	This technology has not been assessed by the Section 508 Office. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. For additional information or assistance regarding Section 508, please contact the Section 508 Office at Section508@va.gov.
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v23.3
Decision Date:	03/13/2023 at 16:47:52 UTC
Introduced By:	TRM Request
Vendor Name:	Citrix

Vendor Release Information

The Vendor Release table provides the known releases for the TRM Technology, obtained from the vendor (or from the release source).

You must be logged into the RSAA website prior to clicking the Attestation URLs or the URLs won't open.

Version	Release Date	Vendor End of Life Date	Vendor Desupport Date
4.3	06/30/2015
4.4	12/18/2015
4.5	09/15/2016
4.6	12/01/2016
4.11	02/26/2018
4.12	06/04/2018

Current Decision Matrix (03/08/2023)

Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.

The VA Decision Matrix displays the current and future VAIT position regarding different releases of a TRM entry. These decisions are based upon the best information available as of the most current date. The consumer of this information has the responsibility to consult the organizations responsible for the desktop, testing, and/or production environments to ensure that the target version of the technology will be supported.

Legend:

White	Authorized: The technology/standard has been authorized for use.
Yellow	Authorized w/ Constraints: The technology/standard can be used within the specified constraints located below the decision matrix in the footnote[1] and on the General tab.
Gray	Authorized w/ Constraints (POA&M): This technology or standard can be used only if a POA&M review is conducted and signed by the Authorizing Official Designated Representative (AODR) as designated by the Authorizing Official (AO) or designee and based upon a recommendation from the POA&M Compliance Enforcement, has been granted to the project team or organization that wishes to use the technology.
Orange	Authorized w/ Constraints (DIVEST): VA has decided to divest itself on the use of the technology/standard. As a result, all projects currently utilizing the technology/standard must plan to eliminate their use of the technology/standard. Additional information on when the entry is projected to become unauthorized may be found on the Decision tab for the specific entry.
Black	Unauthorized: The technology/standard is not (currently) permitted to be used under any circumstances.
Blue	Authorized w/ Constraints (PLANNING/EVALUATION): The period of time this technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population. If a customer would like to use this technology, please work with your local or Regional OI&T office and contact the appropriate evaluation office displayed in the notes below the decision matrix. The Local or Regional OI&T office should submit an inquiry to the TRM if they require further assistance or if the evaluating office is not listed in the notes below.

Release/Version Information:

VA decisions for specific versions may include a ‘.x’ wildcard, which denotes a decision that pertains to a range of multiple versions.

For example, a technology authorized with a decision for 7.x would cover any version of 7.(Anything) - 7.(Anything). However, a 7.4.x decision would cover any version of 7.4.(Anything), but would not cover any version of 7.5.x or 7.6.x on the TRM.

VA decisions for specific versions may include ‘+’ symbols; which denotes that the decision for the version specified also includes versions greater than what is specified but is not to exceed or affect previous decimal places.

For example, a technology authorized with a decision for 12.6.4+ would cover any version that is greater than 12.6.4, but would not exceed the .6 decimal ie: 12.6.401 is ok, 12.6.5 is ok, 12.6.9 is ok, however 12.7.0 or 13.0 is not.

Any major.minor version that is not listed in the VA Decision Matrix is considered Authorized w/ Constraints (POA&M).

<Past

CY2019

CY2020

CY2021

Future>

Release

4.3

Unapproved

4.4

Unapproved

4.5

Prohibited

4.6

DIVEST
[3, 4, 5, 7]

Unapproved

4.11

DIVEST
[3, 4, 5, 7]

Unapproved

4.12

Approved w/Constraints
[3, 4, 5, 7]

Approved w/Constraints
[3, 4, 7, 8]

Unapproved

Decision Constraints


[1]	Security Engineering (SE) conducted a pre-assessment and security requirements verification of Citrix Windows Desktop Lock. It is advised that if this product is used within the Department of Veterans Affairs (VA) that the following constraints be applied: A security vulnerability was identified for version 4.5 (CVE 2016-9111) of Citrix Windows Desktop Lock. The vulnerability concerned access control mechanisms that may allow an attacker to bypass the authentication requirement by leveraging physical access to the Virtual Desktop Infrastructure (VDI). This condition could not be replicated or confirmed by the vendor. Further, the identifier could not be reached for additional investigation of the condition as of December 8, 2016. SETL will need to conduct its own independent testing to assure that the condition does not exist in version 4.6 or cannot be replicated. Ensure that FIPS encryption is properly configured so that sensitive data stored with Citrix Receiver for Windows Desktop Lock is encrypted with a FIPS 140-2 validated cryptographic module. VA Handbook 6500, SC-28 ` Protection of Information at Rest ` requires VA sensitive information to be encrypted using FIPS 140-2 validated encryption.

[2]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[3]	Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, extra vigilance should be applied to ensure the versions remain properly patched to mitigate known and future vulnerabilities. The local ISO can provide assistance in reviewing the NIST vulnerabilities.

[4]	Users should check with their supervisor, Information Security Office (ISO) or local OIT representative for permission to download and use this software. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Freeware may only be downloaded directly from the primary site that the creator of the software has advertised for public download and user or development community engagement. Users should note, any attempt by the installation process to install any additional, unrelated software is not authorized and the user should take the proper steps to decline those installations.

[5]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[6]	Security Engineering (SE) conducted a pre-assessment and security requirements verification of Citrix Windows Desktop Lock. It is advised that if this product is used within the Department of Veterans Affairs (VA) that the following constraints be applied: A security vulnerability was identified for version 4.5 (CVE 2016-9111) of Citrix Windows Desktop Lock. The vulnerability concerned access control mechanisms that may allow an attacker to bypass the authentication requirement by leveraging physical access to the Virtual Desktop Infrastructure (VDI). This condition could not be replicated or confirmed by the vendor. Further, the identifier could not be reached for additional investigation of the condition as of December 8, 2016. SETL will need to conduct its own independent testing to assure that the condition does not exist in version 4.6 or cannot be replicated. Ensure that FIPS encryption is properly configured so that sensitive data stored with Citrix Receiver for Windows Desktop Lock is encrypted with a FIPS 140-2 validated cryptographic module. VA Handbook 6500, SC-28 ` Protection of Information at Rest ` requires VA sensitive information to be encrypted using FIPS 140-2 validated encryption.

[7]	Security Engineering (SE) conducted a pre-assessment and security requirements verification of Citrix Windows Desktop Lock. It is advised that if this product is used within the Department of Veterans Affairs (VA) that the following constraints be applied: A security vulnerability was identified for version 4.5 (CVE 2016-9111) of Citrix Windows Desktop Lock. The vulnerability concerned access control mechanisms that may allow an attacker to bypass the authentication requirement by leveraging physical access to the Virtual Desktop Infrastructure (VDI). This condition could not be replicated or confirmed by the vendor. Further, the identifier could not be reached for additional investigation of the condition as of December 8, 2016. SETL will need to conduct its own independent testing to assure that the condition does not exist in version 4.6 or cannot be replicated. Ensure that FIPS encryption is properly configured so that sensitive data stored with Citrix Receiver for Windows Desktop Lock is encrypted with a FIPS 140-2 validated cryptographic module. VA Handbook 6500, SC-28 ` Protection of Information at Rest ` requires VA sensitive information to be encrypted using FIPS 140-2 validated encryption.

[8]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

Note:

At the time of writing, version 4.12 is the most current version, released 06/04/2018.

Type	Name	Source	Description
Vendor Provided*	About Citrix Workspace App	Publicly Available	This site provides and overview of Citrix Workspace App, which replaced Citrix Receiver Windows Desktop Lock.
*NOTE: Vendor provided information is subject to the accuracy of the manufacturer.

Name	Description
No components have been identified for this entry.


Collaboration and Electronic Workplace Collaboration Software	Content Management
Systems Management Systems Management Tools	Application Management
Collaboration and Electronic Workplace Productivity Software	Miscellaneous Productivity Tools and Utilities

General Analysis

Adoption Benefits

There is no licensing fee associated with this technology.
The technology supports a number of industry standard file formats.
This product may improve productivity for specific staff by allowing for faster workstation logon when transitioning from one computer to another.
This is a well-documented technology.

Adoption Risks

This technology is available as freeware. As such this technology may be without clearly defined support options which may result in suboptimal enterprise level support.
There are multiple published vulnerabilities for Citrix Workspace App.
Citrix Workspace app Desktop Lock is not Federal Information Processing standards (FIPS) 140-2 certified.
There has been no recent development for this technology.
System scans indicate that this technology is no longer in use within the VA network.
The potential exists to store Personally Identifiable Information (PII), Protected Health Information (PHI) and/or VA Sensitive data and proper security standards must be followed in these cases.
There are known Common Vulnerabilities and Exposures (CVEs) and VA Cyber Security Operations Center (CSOC) vulnerabilities. Please see https://nvd.nist.gov/vuln/search for more details.
There are other authorized solutions that provide similar functionality available on the TRM.

Architectural Benefits

The solution is compatible with virtual machines, therefore consistent with the enterprise Server Virtualize First Policy (VAIQ 7266972 08-27-2012).

Architectural Risks

The technology is not portable as it runs only on Windows platforms.

- The information contained on this page is accurate as of the Decision Date (03/13/2023 at 16:47:52 UTC).

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 24.11

General Information

Vendor Release Information

Current Decision Matrix (03/08/2023)

Decision Constraints

References

Technology Components

VA Categories

View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Optional Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 24.11

General Information

Vendor Release Information

Current Decision Matrix (03/08/2023)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Optional Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

EMAIL UPDATES

VA Categories

View the VA Categorization Framework