| | | | [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.
| | | [11] | Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request with the Project Special Forces (SPF) team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). |
|
