X2Go

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:	X2Go is an open source remote desktop software for Linux. X2Go provides remote access to the Linux graphical user interface and it provides a secure remote connection via Secure Shell. Please note that this software contains a server package and a client package. The server package must be installed on a Linux host. The Client packages can be run on Linux, OS X, or Windows. The TRM decisions in this entry only apply to technologies and versions owned, operated, managed, patched, and version-controlled by VA. This includes technologies deployed as software installations on VMs within VA-controlled cloud environments (e.g. VA Enterprise Cloud (VAEC)). Cloud services provided by the VAEC, which are listed in the VAEC Service Catalog, and those controlled and managed by an external Cloud Service Provider (i.e. SaaS) are not in the purview of the TRM. For more information on the use of cloud services and cloud-based products within VA, including VA private clouds, please see the Enterprise Cloud Solutions Office (ECSO) Portal at: https://dvagov.sharepoint.com/sites/OITECSO
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/22/2023 at 16:47:07 UTC
Aliases:	X2Go Client; X2Go Server
Introduced By:	TRM Request
Vendor Name:	X2Go Community

Vendor Release Information

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

Version	Release Date	Vendor End of Life Date	Vendor Desupport Date
Client 4.0.x	02/21/2017
Client 4.1.x	03/12/2017
Server 4.0.0.x
Server 4.0.1.0.x
Server 4.0.1.1.x
Server 4.0.1.2.x
Server 4.0.1.3.x
Server 4.0.1.4.x
Server 4.0.1.5.x
Server 4.0.1.6.x
Server 4.0.1.7.x
Server 4.0.1.8.x
Server 4.0.1.9.x
Server 4.0.1.10.x
Server 4.0.1.19.x
Server 4.0.1.20.x
Server 4.0.1.22.x	11/11/2017
Server 4.1.0.x	03/01/2018

Current Decision Matrix (03/20/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 VA IT 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. Any major.minor version that is not listed in the VA Decision Matrix is considered unapproved for use.

Legend:

White	Approved: The technology/standard has been approved for use.
Yellow	Approved 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	Unapproved: 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	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 unapproved may be found on the Decision tab for the specific entry.
Black	Prohibited: The technology/standard is not (currently) permitted to be used under any circumstances.
Blue	Planning/Evaluation Constraint: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 approved 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 approved 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.

<Past

CY2017

CY2018

CY2019

Future>

Release

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

Client 4.0.x

Approved w/Constraints
[1, 2, 3, 4, 5]

Approved w/Constraints
[1, 2, 5, 6, 7]

Approved w/Constraints
[1, 2, 5, 6, 8]

Divest
[2, 5, 6, 8, 9]

Divest
[2, 5, 6, 8, 10]

Unapproved

Client 4.1.x

Approved w/Constraints
[1, 2, 3, 4, 5]

Approved w/Constraints
[1, 2, 5, 6, 7]

Approved w/Constraints
[1, 2, 5, 6, 8]

Divest
[2, 5, 6, 8, 9]

Divest
[2, 5, 6, 8, 10]

Server 4.0.0.x

Prohibited

Server 4.0.1.0.x

Prohibited

Server 4.0.1.1.x

Prohibited

Server 4.0.1.2.x

Prohibited

Server 4.0.1.3.x

Prohibited

Server 4.0.1.4.x

Prohibited

Server 4.0.1.5.x

Prohibited

Server 4.0.1.6.x

Prohibited

Server 4.0.1.7.x

Prohibited

Server 4.0.1.8.x

Prohibited

Server 4.0.1.9.x

Prohibited

Server 4.0.1.10.x

Prohibited

Server 4.0.1.19.x

Approved w/Constraints
[1, 2, 3, 4, 5]

Approved w/Constraints
[1, 2, 5, 6, 7]

Approved w/Constraints
[1, 2, 5, 6, 8]

Divest
[2, 5, 6, 8, 9]

Divest
[2, 5, 6, 8, 10]

Unapproved

Server 4.0.1.20.x

Approved w/Constraints
[1, 2, 3, 4, 5]

Approved w/Constraints
[1, 2, 5, 6, 7]

Approved w/Constraints
[1, 2, 5, 6, 8]

Divest
[2, 5, 6, 8, 9]

Divest
[2, 5, 6, 8, 10]

Unapproved

Server 4.0.1.22.x

Unapproved

Divest
[2, 5, 6, 8, 9]

Divest
[2, 5, 6, 8, 10]

Unapproved

Server 4.1.0.x

Unapproved

Divest
[2, 5, 6, 8, 10]

Decision Constraints


[1]	The X2Go server must not be used to connect more than one server since the PostgreSQL database (a TRM technology that is in divestiture) is only needed if users are planing to use more than one connected server (server array). Users must also comply with the constraints of the SQLite TRM entry. This product can only be used when the VA approved network mapping tool does not meet the necessary requirements and the use for an alternative tool is warranted. According to the Initial Product Review, it is advised that if this product is used within VA that the following constraints be applied: The application does not comply with the minimum standards for security required by the VA in that it is not FIPS 140-2 compliant. X2Go would routinely be used during sessions to access and transmit VA sensitive information. VA Handbook 6500 policies mandate use of FIPS 140-2 for such data being processed, at rest and in transit. If it is imperative that X2Go remote desktop technology be used in a special instance, configure the Linux server to leverage FIPS 140-2 ciphers to ensure that proper endpoint encryption is enabled. X2Go is not recommended for general use in VA as it is currently not a part of the VA standard baseline configuration. Further investigation and security testing is necessary before consideration for baseline configuration status and potential implementation in VA infrastructure. Vulnerabilities were identified for X2Go Server versions prior to 4.0.1.10.x. The current and most stable version is 4.0.1.19. Server version 4.0.0.x through and including Server version 4.0.1.10.x are prohibited from use. There is no clearly identifiable entity fully responsible for maintaining up-to-date product releases and fixes, such as for CVE-2013-4376 and CVE-2013-7383. As open source, VA would need to implement an aggressive program to monitor X2Go for newly discovered vulnerabilities and necessary fixes. If X2Go is used to satisfy a VA project requirement, a Federal Risk and Authorization Management Program (FedRAMP) compliant Cloud Service Provider (CSP) must be utilized. The FedRAMP approved impact level of the cloud service must be in compliance with the VA requirements for the system being leveraged. If the cloud solution is used to satisfy a VA mission requirement, VA should clearly define the required security controls and document them in a VA approved Memorandum of Understanding and Interconnection Security Agreement (MOU/ISA) contract and other VA approved agreements (e.g., Data Use Agreement) as stated in VA Handbook 6500 and VA Directive 6513 - Secure External Connections. Further, only Cloud Service Providers (CSP) that have been approved TIC 2.0 compliant may be used within the VA. All traffic to and from the CSP must traverse through VA Trusted Internet Connection (TIC) gateway. TIC compliance is a shared responsibility between the CSP and VA. The CSP is required to provide an architecture that supports TIC while VA enforces the TIC routing and compliance.

[2]	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 approved and the user should take the proper steps to decline those installations.

[3]	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.

[4]	Due to potential information security risks, cloud based technologies may not be used without an Enterprise Security Change Control Board (ESCCB) approval. This body is in part responsible for ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[5]	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.

[6]	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.

[7]	Due to potential information security risks, cloud based technologies may not be used without the approval of the VA Enterprise Cloud Services (ECS) Group. This body is in part responsible for ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[8]	Due to potential information security risks, cloud based technologies may not be used without the approval of the Enterprise Cloud Solution Office (ECSO). This body is in part responsible for ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[9]	Users must also comply with the constraints of the SQLite TRM entry. This product can only be used when the VA approved network mapping tool does not meet the necessary requirements and the use for an alternative tool is warranted. According to the Initial Product Review, it is advised that if this product is used within VA that the following constraints be applied: The application does not comply with the minimum standards for security required by the VA in that it is not FIPS 140-2 compliant. X2Go would routinely be used during sessions to access and transmit VA sensitive information. VA Handbook 6500 policies mandate use of FIPS 140-2 for such data being processed, at rest and in transit. If it is imperative that X2Go remote desktop technology be used in a special instance, configure the Linux server to leverage FIPS 140-2 ciphers to ensure that proper endpoint encryption is enabled. X2Go is not recommended for general use in VA as it is currently not a part of the VA standard baseline configuration. Further investigation and security testing is necessary before consideration for baseline configuration status and potential implementation in VA infrastructure. Vulnerabilities were identified for X2Go Server versions prior to 4.0.1.10.x. The current and most stable version is 4.0.1.19. Server version 4.0.0.x through and including Server version 4.0.1.10.x are prohibited from use. There is no clearly identifiable entity fully responsible for maintaining up-to-date product releases and fixes, such as for CVE-2013-4376 and CVE-2013-7383. As open source, VA would need to implement an aggressive program to monitor X2Go for newly discovered vulnerabilities and necessary fixes. If X2Go is used to satisfy a VA project requirement, a Federal Risk and Authorization Management Program (FedRAMP) compliant Cloud Service Provider (CSP) must be utilized. The FedRAMP approved impact level of the cloud service must be in compliance with the VA requirements for the system being leveraged. If the cloud solution is used to satisfy a VA mission requirement, VA should clearly define the required security controls and document them in a VA approved Memorandum of Understanding and Interconnection Security Agreement (MOU/ISA) contract and other VA approved agreements (e.g., Data Use Agreement) as stated in VA Handbook 6500 and VA Directive 6513 - Secure External Connections. Further, only Cloud Service Providers (CSP) that have been approved TIC 2.0 compliant may be used within the VA. All traffic to and from the CSP must traverse through VA Trusted Internet Connection (TIC) gateway. TIC compliance is a shared responsibility between the CSP and VA. The CSP is required to provide an architecture that supports TIC while VA enforces the TIC routing and compliance.

[10]	Users must also comply with the constraints of the SQLite TRM entry. This technology can only be used when the VA approved network mapping tool does not meet the necessary requirements and the use for an alternative tool is warranted. Per the Initial Product Review, users must abide by the following constraints: X2Go is not recommended for general use in VA, as it is currently not a partof the VA standard baseline configuration. Further investigation, security, andfunctionality testing is necessary before consideration for baselineconfiguration status and potential implementation in VA infrastructure. X2Go does not comply with the minimum standards for security required bythe VA in that it is not FIPS 140-2 compliant. VA Handbook 6500 policiesmandate the use of FIPS 140-2 for such data being processed, at rest and intransit. Vulnerabilities were identified for X2Go Server versions prior to 4.0.1.10. Thecurrent and most stable version is 4.0.1.19. There is no clearly identifiableentity fully responsible for maintaining up-to-date product releases and fixes,such as for CVE-2013-4376 and CVE-2013-7383. As open source, VA wouldneed to implement an aggressive program to monitor X2Go for newlydiscovered vulnerabilities and necessary fixes. If X2Go is used to satisfy a VA project requirement, a Federal Risk andAuthorization Management Program (FedRAMP) compliant Cloud ServiceProvider (CSP) must be utilized. The FedRAMP approved impact level of thecloud service must be in compliance with the VA requirements for the systembeing leveraged. If the cloud solution is used to satisfy a VA missionrequirement, VA should clearly define the required security controls anddocument them in a VA approved Memorandum of Understanding andInterconnection Security Agreement (MOU/ISA) contract and other VAapproved agreements (e.g., Data Use Agreement) as stated in VA Handbook6500 and VA Directive 6513 - Secure External Connections. Further, onlyCloud Service Providers (CSP) that have been approved TIC 2.0 compliantmay be used within the VA. All traffic to and from the CSP must traversethrough VA Trusted Internet Connection (TIC) gateway. TIC compliance is ashared responsibility between the CSP and VA. The CSP is required toprovide an architecture that supports TIC while VA enforces the TIC routingand compliance.

Note:

At the time of writing, version 4.1.2.2 is the most current version, released 02/12/2020.

References

The following reference(s) are associated with this entry:
Type	Name	Description
Vendor Provided*	Version History	This links to an index of the various releases of x2go server and x2go client.
Other	X2Go Client (4.1.2.2) released	This page provides release notes for the latest version 4.1.2.2
*NOTE: Vendor provided information is subject to the accuracy of the manufacturer.

Technology Components

Note: This list may not be complete. No component, listed or unlisted, may be used outside of the technology in which it is released. The usage decision for a component is found in the Decision and Decision Constraints.
Name	Description
PyHoca-CLI	The PyHoca-CLI command line client (CLI) that is written in Python.
PyHoca-GUI	The PyHoca-GUI is a Python-based system tray applet.
X2Go Client-Side Printing	X2Go Client-Side Printing is an optional component that provides a backend that spools X2Go print jobs and the X2Go server-side printing add-on package.
X2Go Desktop Bindings	X2Go Desktop Bindings is an optional component that provides desktop binding tools for the most common desktop environments.
X2Go Desktop Sharing	X2Go Desktop Sharing is an optional component for some Linux environments that enables desktop sharing.
X2Go Session Broker	X2Go Session Broker is an optional component that provides an agent and authentication services.

VA Categories View the VA Categorization Framework

Domain Area	Category	Customer Guidance	Category Locked By ELT Date
Systems Management Systems Management Tools	Remote Desktop Management

Open Source

This entry is available as an open source technology.

Operating Systems Supported by the Technology

macOS - Approved w/Constraints
Red Hat Enterprise Linux (RHEL) - Approved w/Constraints
Windows Client - Approved w/Constraints
Windows Server - Approved w/Constraints

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

This technology is available at no cost through open-source licensing and supports VA`s open source initiative.
This technology has customer support provided through third party companies.

Adoption Risks

There are known Common Vulnerabilities and Exposures (CVEs) associated with this technology. Please see https://nvd.NIST.gov/vuln/search for more details.
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.
X2Go is currently not a part of the VA standard baseline configuration.
This technology can potentially use Secure Sockets Layer (SSL), an unapproved protocol.
There is no indication based on available vendor documentation that this technology is Federal Information Processing Standard (FIPS) 140-2 compliant.

Architectural Benefits

This technology is portable as it runs on multiple TRM-approved operating systems.

Architectural Risks

This technology includes cloud-based functionality which has potential information security risks.

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (03/20/2023)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Open Source

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime 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.7

General Information

Vendor Release Information

Current Decision Matrix (03/20/2023)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Open Source

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

EMAIL UPDATES