7.x |
Approved w/Constraints [6, 7, 8, 9, 10] |
Approved w/Constraints [6, 7, 8, 9, 10] |
Approved w/Constraints [6, 7, 8, 9, 10] |
Approved w/Constraints [6, 7, 8, 10, 11] |
Approved w/Constraints [6, 7, 8, 10, 11] |
Approved w/Constraints [6, 7, 8, 10, 11] |
Approved w/Constraints [6, 7, 8, 10, 11] |
Approved w/Constraints [6, 7, 8, 10, 11] |
Approved w/Constraints [6, 7, 8, 10, 11] |
Approved w/Constraints [6, 7, 8, 10, 11] |
Approved w/Constraints [6, 7, 8, 10, 11] |
Approved w/Constraints [6, 7, 8, 10, 11] |
| | [1] | This technology must use the latest version of Java Runtime Environment (JRE) - Oracle. | | [2] | In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004 , VA Directive 6517, and VA Directive 6513. The local ISO can advise on the ESCCB review process. | | [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] | In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004 , VA Directive 6517, and VA Directive 6513. The local ISO can advise on the ESCCB review process. | | [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] | This technology must use the latest version of Java Runtime Environment (JRE) - Oracle.
This technology must use the latest TRM-approved version of Java Development Kit (JDK) - Oracle.
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)
Users must not utilize Cisco Systems Virtual Private Network (VPN) Client, Eclipse Temurin and Open Java Development Kit (OpenJDK), as they are at the time of writing, unapproved in the TRM.
Users must ensure that Microsoft .NET Framework, VMware vSphere and PostgreSQL are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) | | [7] | 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. | | [8] | This product can be configured with a PostgreSQL Database, which currently has TRM constraints limiting its use to Red Hat Enterprise Linux (RHEL) only due to its many known security issues on other platforms. If PostgreSQL is selected for use with this product, these factors must be considered especially when an instance of this product will be considered a Moderate or High-Risk system. See PostgreSQL Database TRM entry for more details. | | [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] | In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004 , VA Directive 6517, and VA Directive 6513. The local ISSO (Information System Security Officer) can advise on the ESCCB review process. | | [11] | 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. |
|