<Past |
Future> |
7.3 |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
7.4.x |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
7.5.x |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
7.6.x |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
8.x |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
9.0 |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
9.1 |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
9.2 |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
9.3 |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
9.4.x |
DIVEST [11, 12, 13, 14] |
DIVEST [11, 12, 13, 14] |
DIVEST [11, 12, 13, 14] |
Authorized w/ Constraints (DIVEST) [11, 12, 13, 14] |
Authorized w/ Constraints (DIVEST) [11, 12, 13, 14] |
Authorized w/ Constraints (DIVEST) [11, 12, 13, 14] |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
10.0.x |
DIVEST [11, 12, 13, 14] |
DIVEST [11, 12, 13, 14] |
DIVEST [11, 12, 13, 14] |
Authorized w/ Constraints (DIVEST) [11, 12, 13, 14] |
Authorized w/ Constraints (DIVEST) [11, 12, 13, 14] |
Authorized w/ Constraints (DIVEST) [11, 12, 13, 14] |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
11.0.x |
DIVEST [11, 12, 13, 14] |
DIVEST [11, 12, 13, 14] |
DIVEST [11, 12, 13, 14] |
Authorized w/ Constraints (DIVEST) [11, 12, 13, 14] |
Authorized w/ Constraints (DIVEST) [11, 12, 13, 14] |
Authorized w/ Constraints (DIVEST) [11, 12, 13, 14] |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
12.0.x |
Approved w/Constraints [11, 12, 13, 14] |
Approved w/Constraints [11, 12, 13, 14] |
Approved w/Constraints [11, 12, 13, 14] |
Authorized w/ Constraints [11, 12, 13, 14] |
Authorized w/ Constraints [11, 12, 13, 14] |
Authorized w/ Constraints [11, 12, 13, 14] |
Authorized w/ Constraints [11, 12, 13, 14] |
Authorized w/ Constraints [11, 12, 13, 14] |
Authorized w/ Constraints [11, 12, 13, 14] |
Authorized w/ Constraints [11, 12, 13, 14] |
Authorized w/ Constraints [11, 12, 13, 14] |
Authorized w/ Constraints [11, 12, 13, 14] |
Note: |
At the time of writing, version 12.0.7 is the most current version, released 02/29/2024. |
| | [11] | 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. | | [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] | This technology must use the latest version of Java Development Kit (JDK) - Oracle.
Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM.
Users must not utilize Maven Integration for Eclipse (M2Eclipse), as it is at the time of writing, unapproved in the TRM.
Per the Initial Product Review, users must abide by the following constraints:
- Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. Administrators must ensure Jetty is properly configured to meet VA 6500 requirements.
- As of this writing (Mar 11th, 2024), the VA has authorized with constraints Java versions 8, 11 and 16.x-19.x. It must be noted that the VA only supports versions with Long Term Support (LTS). At the present time that only includes versions 8, 11, and 17. Versions 16.x, 18.x and 19.x do not have LTS and all have passed the “Vendor End of Life” date noted in the VA TRM.
- Due to potential information security risks, SaaS/PaaS solutions must complete the Veterans-Focused Integration Process Request (VIPR) process where a collaborative effort between Demand Management (DM), Enterprise Program Management Office Information Assurance (EPMO IA), Digital Transformation Center (DTC), Enterprise Cloud Solutions Office (ECSO), Chief Technology Officer (CTO), and stakeholders determines the SaaS/PaaS category during the Discovery Phase. All SaaS and Non AWS or Azure (VAEC) PaaS assets are routed to EPMO IA for Analysis and Approval to Operate (ATO) with technical oversight, acquisition, production, and sustainment provided by DTC.
- Jetty has been identified as having numerous published vulnerabilities. Users must ensure that they vigilantly check the published vulnerabilities for this product and apply the necessary remediations as soon as possible.
All published vulnerabilities within the last 18 months are showing either that they’ve been addressed or are specific to another application or service. Those applications and services have also addressed their respective CVE’s. However, VA users looking to implement Jetty should double check the CVE’s, along with search parameters for the specific versions of Jetty, Java EE, Java SE and/or whatever applications they are using Jetty with, to ensure there are no CVE’s affecting their specific implementation.
| | [14] | 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, visit the Product Marketplace. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). |
|