| | [1] | Only product add-ons that comply with TRM may be used. At time of writing, several add-ons correspond to unapproved or prohibited TRM technologies. These include Putty, TeamViewer, VNC, FTP, Telnet, non-FIPS SSH and several others. If a desired add-on has not been evaluated for TRM, the end user must submit a TRM review request and the technology approved prior to use.
This product is capable of storing login credentials for all systems the end user accesses. As a result, the database option used must be encrypted with a FIPS 140-2 validated technology as per VA handbook 6500 otherwise the storage of this information is not permitted. Note that the product can leverage cloud based resources for the storage of usernames and passwords. Use of cloud or vendor hosted storage for this functionality is NOT permitted. | | [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] | Only product add-ons that comply with TRM may be used. At time of writing, several add-ons correspond to unapproved or prohibited TRM technologies. These include Putty, TeamViewer, Virtual Network Computing (VNC), File Transfer Protocol (FTP), Telnet, non-FIPS SSH and several others. If a desired add-on has not been evaluated for TRM, the end user must submit a TRM review request and the technology approved prior to use.
This product is capable of storing login credentials for all systems the end user accesses. As a result, the database option used must be encrypted with a Federal Information Processing Standard (FIPS) 140-2 validated technology as per VA handbook 6500 otherwise the storage of this information is not permitted. Note that the product can leverage cloud based resources for the storage of usernames and passwords. Use of cloud or vendor hosted storage for this functionality is NOT permitted.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period. | | [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 approved and the user should take the proper steps to decline those installations. | | [5] | Only product add-ons that comply with TRM may be used. At time of writing, several add-ons correspond to unapproved or prohibited TRM technologies. These include Putty, TeamViewer, Virtual Network Computing (VNC), File Transfer Protocol (FTP), Telnet, non-FIPS SSH and several others. If a desired add-on has not been evaluated for TRM, the end user must submit a TRM review request and the technology approved prior to use.
This product is capable of storing login credentials for all systems the end user accesses. As a result, the database option used must be encrypted with a Federal Information Processing Standard (FIPS) 140-2 validated technology as per VA handbook 6500 otherwise the storage of this information is not permitted. Note that the product can leverage cloud based resources for the storage of usernames and passwords. Use of cloud or vendor hosted storage for this functionality is NOT permitted.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
This assessment includes an Initial Product Review (IPR) completed by the VA Enterprise Security Solutions Service with the following constraints:
- A checklist or detailed user training must be used to inform users of security responsibilities.
- All equipment used for remote access solutions that process VA classified information is government owned and managed.
- The user must implement automated controls or train users to physically disconnect or disable NICs when no longer connect to the secure VPN.
| | [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] | Only product add-ons that comply with TRM may be used. All TRM unapproved software bundled with this product must be removed after installation of the product. At time of writing, several add-ons correspond to unapproved or prohibited TRM technologies. These include Putty, TeamViewer, Virtual Network Computing (VNC), File Transfer Protocol (FTP), Telnet, non-FIPS SSH and several others. If a desired add-on has not been evaluated for TRM, the end user must submit a TRM review request and the technology approved prior to use.
This product is capable of storing login credentials for all systems the end user accesses. As a result, the database option used must be encrypted with a Federal Information Processing Standard (FIPS) 140-2 validated technology as per VA handbook 6500 otherwise the storage of this information is not permitted. Note that the product can leverage cloud based resources for the storage of usernames and passwords. Use of cloud or vendor hosted storage for this functionality is NOT permitted.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
This assessment includes an Initial Product Review (IPR) completed by the VA Enterprise Security Solutions Service with the following constraints:
- A checklist or detailed user training must be used to inform users of security responsibilities.
- All equipment used for remote access solutions that process VA classified information is government owned and managed.
- The user must implement automated controls or train users to physically disconnect or disable NICs when no longer connect to the secure VPN.
| | [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] | Only product add-ons that comply with TRM may be used. All TRM unapproved software bundled with this product must be removed after installation of the product. At time of writing, several add-ons correspond to unapproved or prohibited TRM technologies. These include Putty, TeamViewer, Virtual Network Computing (VNC), File Transfer Protocol (FTP), Telnet, non-FIPS SSH (Secure Shell) and several others. If a desired add-on has not been evaluated for TRM, the end user must submit a TRM review request and the technology approved prior to use.
This product is capable of storing login credentials for all systems the end user accesses. As a result, the database option used must be encrypted with a Federal Information Processing Standard (FIPS) 140-2 validated technology as per VA handbook 6500 otherwise the storage of this information is not permitted. Note that the product can leverage cloud based resources for the storage of usernames and passwords. Use of cloud or vendor hosted storage for this functionality is NOT permitted.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
This assessment includes an Initial Product Review (IPR) completed by the VA Enterprise Security Solutions Service with the following constraints:- A checklist or detailed user training must be used to inform users of security responsibilities.
- All equipment used for remote access solutions that process VA classified information is government owned and managed.
- The user must implement automated controls or train users to physically disconnect or disable NICs when no longer connect to the secure VPN (Virtual Private Network).
| | [10] | Only product add-ons that comply with TRM may be used. All TRM unapproved software bundled with this product must be removed after installation of the product. At time of writing, several add-ons correspond to unapproved or prohibited TRM technologies. These include Putty, TeamViewer, Virtual Network Computing (VNC), File Transfer Protocol (FTP), Telnet, non-FIPS SSH (Secure Shell) and several others. If a desired add-on has not been evaluated for TRM, the end user must submit a TRM review request and the technology approved prior to use.
This product is capable of storing login credentials for all systems the end user accesses. As a result, the database option used must be encrypted with a Federal Information Processing Standard (FIPS) 140-2 validated technology as per VA handbook 6500 otherwise the storage of this information is not permitted. Note that the product can leverage cloud based resources for the storage of usernames and passwords. Use of cloud or vendor hosted storage for this functionality is NOT permitted.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
This assessment includes an Initial Product Review (IPR) completed by the VA Enterprise Security Solutions Service with the following constraints:
- Use a FIPS 140-2 validated cryptographic module to secure VA sensitive data in applications developed using Devolutions Remote Desktop Manager Free Edition.
- All FTP and Telnet services were restricted as of August 10, 2015 to the origination IP address and destination IP address in the firewall rules and by using access control lists (ACLs). The TRM entry for Telnet has been updated to unapproved.
- It is advised to implement automated controls or train users to physically disconnect or disable NICs when no longer connected to the secure VPN.
| | [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). |
|