8.6.x |
Approved w/Constraints [3, 5, 8, 9] |
Approved w/Constraints [3, 5, 8, 9] |
Approved w/Constraints [3, 8, 9, 10, 11] |
Approved w/Constraints [3, 8, 9, 10, 11] |
Authorized w/ Constraints [3, 8, 9, 10, 11] |
Approved w/Constraints [3, 8, 9, 10, 11] |
Approved w/Constraints [3, 8, 9, 10, 11] |
Approved w/Constraints [3, 8, 9, 10, 11] |
Authorized w/ Constraints [3, 8, 9, 10, 11] |
Authorized w/ Constraints [3, 8, 9, 10, 11] |
Authorized w/ Constraints [3, 8, 9, 10, 11] |
Authorized w/ Constraints [3, 8, 9, 10, 11] |
| | [1] | Glink must be configured to use only Secure Shell (SSH) on the communication line to provide security and privacy, including encryption and authentication, for all Transmission Control Protocol/Internet Protocol.
Ensure use of a FIPS 140-2 validated cryptographic module is employed on a system level to secure VA sensitive data in applications and devices.
The TRM will only consider new technology if currently authorized terminal emulators do not meet VA needs or requirements; only authorized products can be used within the VA. | | [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] | Technology must remain patched and operated in accordance with Federal and Department security policies and guidelines in order to mitigate known and future security vulnerabilities. | | [4] | 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. | | [5] | Per the Initial Product Review, users must abide by the following constraints:
- Glink must be configured to use only Secure Shell (SSH) on the communication line to provide security and privacy, including encryption and authentication, for all Transmission Control Protocol/Internet Protocol.
- Ensure use of a FIPS 140-2 validated cryptographic module is employed on a system level to secure VA sensitive data in applications and devices.
- The TRM will only consider new technology if currently authorized terminal emulators do not meet VA needs or requirements; only authorized products can be used within the VA.
Users must ensure that Apache Tomcat and Microsoft Internet Information Services (IIS) are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Users must not use PuTTY with this technology as it is unapproved on the TRM.
Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM.
The File Transfer Protocol (FTP) features of this software must not be used as the FTP protocol is prohibited for use on the VA network. (For further information see: VA Policy Memo VAIQ 7615193 on Prohibited Use of File Transfer Protocol (FTP) and Telnet Services) | | [6] | 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. | | [7] | 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 ISSO (Information System Security Officer) to ensure compliance with VA Handbook 6500. | | [8] | Users should check with their supervisor, Information System Security Officer (ISSO) 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. | | [9] | 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 ISSO (Information System Security Officer) to ensure compliance with both VA Handbook 6500 and VA Directive 6500. | | [10] | Per the Initial Product Review, users must abide by the following constraints:
- Glink will require a 3rd party FIPS 140-2 (or its successor) certified solution for any data containing Personal Health Information (PHI) / Personally Identifiable Information (PII) or VA sensitive information.
- Upgrade to the latest version of the software to ensure it includes the latest security enhancements and patches for known vulnerabilities.
- Conduct regular assessments of the security of third-party components integrated with Glink for Windows, and apply updates as needed.
Users must ensure that Microsoft Internet Information Services (IIS) is implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Users must not use PuTTY with this technology as it is unapproved on the TRM.
Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM.
The File Transfer Protocol (FTP) features of this software must not be used as the FTP protocol is prohibited for use on the VA network. (For further information see: VA Policy Memo VAIQ 7615193 on Prohibited Use of File Transfer Protocol (FTP) and Telnet Services) | | [11] | The Federal Information Processing standards (FIPS) 140-2 certification status of this technology was not able to be verified. This technology will require a 3rd party FIPS 140-2 or 140-3 certified solution for any data containing PHI/PII or VA sensitive information, where applicable. More information regarding the Cryptographic Module Validation Program (CMVP) can be found on the NIST website. |
|