<Past |
Future> |
2.2.x |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
2.7.x |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
2.8.x |
Approved w/Constraints [2, 5, 6] |
Approved w/Constraints [2, 5, 7, 8] |
Approved w/Constraints [2, 5, 7, 8] |
Approved w/Constraints [2, 5, 7, 8] |
Approved w/Constraints [7, 8, 9, 10] |
Approved w/Constraints [7, 8, 9, 10] |
Approved w/Constraints [7, 8, 9, 10] |
Approved w/Constraints [7, 8, 9, 10] |
Approved w/Constraints [7, 8, 9, 10] |
Approved w/Constraints [7, 8, 9, 10] |
Approved w/Constraints [7, 8, 9, 10] |
Approved w/Constraints [7, 8, 9, 10] |
2.9.x |
Unapproved |
Approved w/Constraints [2, 5, 7, 8] |
Approved w/Constraints [2, 5, 7, 8] |
Approved w/Constraints [2, 5, 7, 8] |
Approved w/Constraints [7, 8, 9, 10] |
Approved w/Constraints [7, 8, 9, 10] |
Approved w/Constraints [7, 8, 9, 10] |
Approved w/Constraints [7, 8, 9, 10] |
Approved w/Constraints [7, 8, 9, 10] |
Approved w/Constraints [7, 8, 9, 10] |
Approved w/Constraints [7, 8, 9, 10] |
Approved w/Constraints [7, 8, 9, 10] |
| | [1] | Several levels of RDP session encryption are available. Administrators should ensure that FIPS 140-2 encryption is enabled for all remote connection sessions. | | [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] | Several levels of Remote Desktop Protocol (RDP) session encryption are available. Administrators should ensure that Federal Information Processing Standard (FIPS) 140-2 encryption is enabled for all remote connection sessions. | | [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] | Several levels of Remote Desktop Protocol (RDP) session encryption are available. Administrators should ensure that Federal Information Processing Standard (FIPS) 140-2 encryption is enabled for all remote connection sessions.
Per the Initial Product Review (IPR):
It is advised that product version v2.82 or later should only be used | | [7] | Several levels of Remote Desktop Protocol (RDP) session encryption are available. Administrators should ensure that Federal Information Processing Standard (FIPS) 140-2 encryption is enabled for all remote connection sessions.
This technology requires using a Universal Service Bus (USB) technology to transfer data into the records. As such, proper precautions need to be taken to protect data.
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)
Per the Security Assessment Review, users must abide by the following constraints:
- It is advised that product version v2.82 or later should only be used.
| | [8] | 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. | | [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 VA Handbook 6500. | | [10] | 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 approved and the user should take the proper steps to decline those installations. |
|
Note: |
At the time of writing, 2.9.0 is the most current version released. It is advised that product version v2.82 or later should only be used. |