<Past |
Future> |
1.2 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
1.3 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.0 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.1 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.2 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.3 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
3.0 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
3.1 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
3.2 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
3.3 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
3.4 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
3.5 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
3.6 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
3.7 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
4.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
5.x |
Approved w/Constraints [2, 6, 8, 9] |
Approved w/Constraints [2, 6, 8, 9] |
Approved w/Constraints [2, 6, 8, 9] |
Approved w/Constraints [2, 6, 9, 10] |
Approved w/Constraints [2, 6, 9, 10] |
Divest [9, 10, 11, 12, 13] |
Divest [9, 10, 11, 12, 13] |
Divest [9, 10, 11, 12, 13] |
Divest [9, 10, 11, 12, 13] |
Divest [9, 10, 11, 12, 13] |
Unapproved |
Unapproved |
6.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [9, 10, 11, 12, 13] |
Approved w/Constraints [9, 10, 11, 12, 13] |
Approved w/Constraints [9, 10, 11, 12, 13] |
Approved w/Constraints [9, 10, 11, 12, 13] |
Approved w/Constraints [9, 10, 11, 12, 13] |
Approved w/Constraints [9, 10, 11, 12, 13] |
Approved w/Constraints [9, 10, 11, 12, 13] |
| | [1] | This product has runtime dependencies that are not approved on the TRM as of the publication of OneVA TRM v11. eGit is approved conditionally at this time until its runtime dependencies which are automatically downloaded are individually assessed for any individual risks or issues to the VA environment. The Approve with Constraints decision on eGit is subject to change based on completion of those additional assessments. | | [2] | 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. | | [3] | 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. | | [4] | This product is no longer approved for information technology (IT) projects that are or will be mandated to follow standardized processes and tools governing IT activity critical to VA`s implementation of the Veteran-focused Integration Process (VIP). | | [5] | This technology must use the latest TRM-approved version of Java Runtime Environment (JRE) - Oracle.
This technology must use the latest TRM-approved version of Java Development Kit (JDK) - Oracle. | | [6] | Per the Initial Product Review, users must abide by the following constraints:
- EGit will require a 3rd party FIPS 140-2 certified solution for any data containing
PHI/PII or VA sensitive information.
- EGit must be included on the list of applications for continuous monitoring for
published vulnerabilities, updates, and patches; or set to auto update in order
to mitigate vulnerability vectors from outdated software.
- System owners should review the One-VA TRM entries for the approved
versions for use of Eclipse Classic.
- While Eclipse does offer community forums and developer mailing lists, relying
on them may result in slow response times.
This technology must use the latest TRM-approved version of
1) Java Development Kit (JDK) - Oracle,
2) Eclipse Classic, and
3) Java Runtime Environment (JRE) - Oracle.
| | [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 ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | [8] | 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. | | [9] | 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. | | [10] | 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. | | [11] | Per the Initial Product Review, users must abide by the following constraints:
- EGit will require a 3rd party FIPS 140-2 (or its successor) certified solution for any data containing PHI/PII or VA sensitive information.
- EGit must be included on the list of applications for continuous monitoring for published vulnerabilities, updates, and patches in order to mitigate vulnerability vectors from outdated software.
- System owners should review the One-VA TRM entries for the approved versions for use of Eclipse Classic.
- System owners should review the One-VA TRM entries for the approved versions for use of JRE and JDK.
- While Eclipse does offer community forums and developer mailing lists, relying on them may result in slow response times.
This technology must use the latest TRM-approved version of Java Runtime Environment (JRE) - Oracle.
This technology must use the latest TRM-approved version of Java Development Kit (JDK) - Oracle. | | [12] | 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. | | [13] | 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. |
|
Note: |
At the time of writing, version 6.8.0.202311291450-r is the most current version, released 12/06/2023. |