| Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to,
VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information
Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users
should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology
(OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation. |
| The VA Decision Matrix displays the current and future VAIT
position regarding different releases of a TRM entry. These decisions are
based upon the best information available as of the most current date. The consumer of this information has the
responsibility to consult the organizations responsible for the desktop, testing, and/or production environments
to ensure that the target version of the technology will be supported.
|
|
|
| Legend: |
| White |
Authorized: The technology/standard has been authorized for use.
|
| Yellow |
Authorized w/ Constraints: The technology/standard can be used within the specified constraints located
below the decision matrix in the footnote[1] and on the General tab.
|
| Gray |
Authorized w/ Constraints (POA&M): This technology or standard can be used only if a POA&M review is conducted and signed by
the Authorizing Official Designated Representative (AODR) as designated by the Authorizing Official (AO) or designee
and based upon a recommendation from the POA&M Compliance Enforcement,
has been granted to the project team or organization that wishes to use the technology.
|
| Orange |
Authorized w/ Constraints (DIVEST): VA has decided to divest itself on the use of the technology/standard.
As a result, all projects currently utilizing the technology/standard must plan to eliminate their use of
the technology/standard. Additional information on when the entry is projected to become unauthorized may be
found on the Decision tab for the specific entry.
|
| Black |
Unauthorized: The technology/standard is not (currently) permitted to be used under any circumstances.
|
| Blue |
Authorized w/ Constraints (PLANNING/EVALUATION): The period of time this technology is currently being evaluated, reviewed,
and tested in controlled environments. Use of this technology is strictly controlled and not available
for use within the general population. If a customer would like to use this technology, please work with
your local or Regional OI&T office and contact the appropriate evaluation office
displayed in the notes below the decision matrix. The Local or Regional OI&T
office should submit an
inquiry to the TRM
if they require further assistance or if the evaluating office is not listed in the notes below.
|
|
| Release/Version Information: |
|
VA decisions for specific versions may include a ‘.x’ wildcard, which denotes a decision that pertains to a range of multiple versions.
|
|
For example, a technology authorized with a decision for 7.x would cover any version of 7.(Anything) - 7.(Anything). However, a 7.4.x decision
would cover any version of 7.4.(Anything), but would not cover any version of 7.5.x or 7.6.x on the TRM.
|
|
VA decisions for specific versions may include ‘+’ symbols; which denotes that the decision for the version specified also includes versions greater than
what is specified but is not to exceed or affect previous decimal places.
|
|
For example, a technology authorized with a decision for 12.6.4+ would cover any version that is greater than 12.6.4, but would not exceed the .6 decimal ie: 12.6.401
is ok, 12.6.5 is ok, 12.6.9 is ok, however 12.7.0 or 13.0 is not.
|
| Any major.minor version that is not listed in the VA Decision Matrix is considered Authorized w/ Constraints (POA&M). |
|
<Past |
Future> |
| 4 (aka 1.4) |
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) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
| 5 (aka 1.5) |
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) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
| 6 (aka 1.6) |
Authorized w/ Constraints (DIVEST)
[13, 15, 16, 17] |
Authorized w/ Constraints (DIVEST)
[13, 15, 16, 17] |
Authorized w/ Constraints (DIVEST)
[13, 15, 16, 17] |
Authorized w/ Constraints (DIVEST)
[13, 15, 16, 17] |
Authorized w/ Constraints (DIVEST)
[13, 15, 16, 17] |
Authorized w/ Constraints (DIVEST)
[13, 15, 16, 17] |
Authorized w/ Constraints (DIVEST)
[13, 15, 16, 17] |
Authorized w/ Constraints (DIVEST)
[13, 15, 16, 17] |
Authorized w/ Constraints (DIVEST)
[13, 15, 16, 17] |
Authorized w/ Constraints (DIVEST)
[13, 15, 16, 17] |
Authorized w/ Constraints (DIVEST)
[13, 15, 16, 17] |
Authorized w/ Constraints (DIVEST)
[13, 15, 16, 17] |
| 7 (aka 1.7) |
Authorized w/ Constraints (DIVEST)
[13, 15, 16, 17] |
Authorized w/ Constraints (DIVEST)
[13, 15, 16, 17] |
Authorized w/ Constraints (DIVEST)
[13, 15, 16, 17] |
Authorized w/ Constraints (DIVEST)
[13, 15, 16, 17] |
Authorized w/ Constraints (DIVEST)
[13, 15, 16, 17] |
Authorized w/ Constraints (DIVEST)
[13, 15, 16, 17] |
Authorized w/ Constraints (DIVEST)
[13, 15, 16, 17] |
Authorized w/ Constraints (DIVEST)
[13, 15, 16, 17] |
Authorized w/ Constraints (DIVEST)
[13, 15, 16, 17] |
Authorized w/ Constraints (DIVEST)
[13, 15, 16, 17] |
Authorized w/ Constraints (DIVEST)
[13, 15, 16, 17] |
Authorized w/ Constraints (DIVEST)
[13, 15, 16, 17] |
| 8 (aka 1.8) |
Authorized w/ Constraints
[13, 15, 16, 17] |
Authorized w/ Constraints
[13, 15, 16, 17] |
Authorized w/ Constraints
[13, 15, 16, 17] |
Authorized w/ Constraints
[13, 15, 16, 17] |
Authorized w/ Constraints
[13, 15, 16, 17] |
Authorized w/ Constraints
[13, 15, 16, 17] |
Authorized w/ Constraints
[13, 15, 16, 17] |
Authorized w/ Constraints
[13, 15, 16, 17] |
Authorized w/ Constraints
[13, 15, 16, 17] |
Authorized w/ Constraints
[13, 15, 16, 17] |
Authorized w/ Constraints
[13, 15, 16, 17] |
Authorized w/ Constraints
[13, 15, 16, 17] |
| | | | [1] | This Industry Standard is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population. | | | [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 authorized and the user should take the proper steps to decline those installations. | | | [4] | Due to potential information security risks, cloud based technologies may not be used without an Enterprise Security Change Control Board (ESCCB) approval. This body is in part responsible for ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | | [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] | Due to potential information security risks, cloud based technologies may not be used without the approval of the VA Enterprise Cloud Services (ECS) Group. This body is in part responsible for ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | | [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] | Due to potential information security risks, cloud based technologies may not be used without the approval of the Enterprise Cloud Solution Office (ECSO). This body is in part responsible for ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | | [9] | It is advised that if this product is used within the Department of Veterans Affairs (VA) that the following constraints be applied:
1. Security of data at rest and data in transit is delegated to applications developed using this specification.
2. The Jakarta EE specification is supported by an active Eclipse Foundation working group, their mailing list must be continually monitored for guidance in applying the specification. | | | [10] | Per the Initial Product Review, users must abide by the following constraints:
- Security of data at rest and data in transit is delegated to applications developed using this specification.
- The Jakarta EE specification is supported by an active Eclipse Foundation working group, their mailing list must be continually monitored for guidance in applying the specification.
| | | [11] | 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 ISO can provide assistance in reviewing the NIST 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 ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | | [13] | This technology must use the latest TRM-authorized version of Java Development Kit (JDK) - Oracle.
Per the Initial Product Review, users must abide by the following constraints:
- Oracle Java will require a 3rd party FIPS 140-2 certified solution for any data containing PHI/PII or VA sensitive information.
- System Owners/Administrators must monitor any new or existing vulnerabilities associated with Oracle Java EE as the vendor no longer releases updates to the product. Jakarta EE offers the same functionality of Oracle Java EE and is the replacement/rename of the product. Per the vendor, Jakarta is continuously receiving updates as it is the replacement/rename of Oracle Java EE. Oracle Java received its last formal release/update September 2017, but paid support is active through 2030.
| | | [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 VA Handbook 6500. | | | [15] | 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. | | | [16] | 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. | | | [17] | 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 8 is the most current version and was released 09/15/2017.
Because the newer versions of Java Development Kit (JDK) and Jave Runtime Environment (JRE) support the Java EE specifications for older versions of Java EE (e.g. JDK 8, supports Java EE 6 standards), older supported versions of Java EE SDK (Software Development Kit) remain in a divest status for use with newer TRM authorized versions for Java software as needed. |
