|
| [1] | In order to minimize security risks, strict compliance to the following constraints must be adhered to: Proper steps must be taken to ensure any PII/PHI/VA sensitive data at rest and/or in transit is protected per VA Handbook 6500 including the use of FIPS 140-2 certified encryption. NOTE: This product does not use FIPS 140-2 certified encryption. This technology may not be used outside of the VA production network (not in a DMZ) unless those specific uses and instances of this technology are authorized by the Enterprise Security Change Control Board (ESCCB) along with a Memorandum of Understanding and Interconnection Security Agreements (MOU/ISA) which detail the security requirements for those users and systems that share information and resources outside of the VA production network. |
|
| [2] | As of April 23, 2015, per the Deputy CIO of Architecture, Strategy and Design (ASD), all technologies in use by the VA require an assessment by the VA Section 508 office. Section 508 of the Rehabilitation Act Amendments of 1998 is a federal law that sets the guidelines for technology accessibility. A VA Section 508 assessment of this technology has not been completed at the time of publication. Therefore, as of April 23, 2015 only users of this technology who have deployed the technology to the production environment, or have project design and implementation plans authorized, may continue to operate this technology. In the case of a project that has implemented, or been authorized for a specific site or number of users, and that project needs to expand operations to other sites or to an increased user base, it may do so as long as the project stays on the existing version of the technology that was authorized or implemented as of April 22, 2015. Use of this technology in all other cases is prohibited.
|
|
| [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] | 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. |
|
| [5] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users need to be aware that this software does not provide Federal Information Processing Standard (FIPS) 140-2 certified encryption. As such it may not be used for transfer of Personally Identifiable Information (PII), Protected Health Information (PHI), or other VA sensitive data.
The software File Transfer Protocol (FTP) Client must utilize the sFTP protocol instead of the FTP protocol. |
|
| [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] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users need to be aware that this software does not provide Federal Information Processing Standard (FIPS) 140-2 certified encryption. As such it may not be used for transfer of Personally Identifiable Information (PII), Protected Health Information (PHI), or other VA sensitive data.
The software File Transfer Protocol (FTP) Client must utilize the sFTP protocol instead of the FTP protocol. |
|
| [8] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
This technology must use the latest version of Java Runtime Environment (JRE) - Oracle.
Users need to be aware that this software does not provide Federal Information Processing Standard (FIPS) 140-2 certified encryption. As such it may not be used for transfer of Personally Identifiable Information (PII), Protected Health Information (PHI), or other VA sensitive data.
The software File Transfer Protocol (FTP) Client must utilize the sFTP protocol instead of the FTP protocol.
Users must ensure that Microsoft Internet Explorer (IE) is implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) |
|
| [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 ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. |
|
| [10] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must not utilize Java Runtime Environment (JRE) - Oracle, as it is unapproved for use on the TRM.
Users need to be aware that this software does not provide Federal Information Processing Standard (FIPS) 140-2 certified encryption. As such it may not be used for transfer of Personally Identifiable Information (PII), Protected Health Information (PHI), or other VA sensitive data.
The software File Transfer Protocol (FTP) Client must utilize the SFTP protocol instead of the FTP protocol.
Users must ensure that Microsoft Internet Explorer (IE), Firefox, and Google Chrome are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Users must Divest the use of Internet Explorer with this technology. Other authorized internet browsers are available. See Category Tab for details.
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)
Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM.
Users must not utilize Open Java Development Kit (OpenJDK), as it is unapproved for use on the TRM. |
|
| [11] | 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. |
|
| [12] | 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. |
|
| [13] | 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. |
|
| [14] | 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. |
|
| [15] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must ensure that Firefox, Google Chrome, and Microsoft Edge are implemented with VA-authorized baselines. (Refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM.
This technology should not be used with Open Java Development Kit (OpenJDK) as it is unapproved for use at this time. There are other authorized java environments available. See Category tab for details.
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) |
|
| [16] | 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 ISSO (Information System Security Officer) can provide assistance in reviewing the NIST vulnerabilities. |
