<Past |
Future> |
8.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints [2, 4, 5, 6, 7] |
Approved w/Constraints [2, 4, 5, 6, 7] |
Approved w/Constraints [2, 4, 5, 6, 7] |
Approved w/Constraints [2, 4, 5, 6, 7] |
Authorized w/ Constraints [2, 4, 5, 6, 7] |
Authorized w/ Constraints [2, 4, 5, 6, 7] |
Authorized w/ Constraints [2, 4, 5, 6, 7] |
Authorized w/ Constraints [2, 4, 5, 6, 7] |
9.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
10.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
11.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints [2, 4, 5, 6, 7] |
Approved w/Constraints [2, 4, 5, 6, 7] |
Approved w/Constraints [2, 4, 5, 6, 7] |
Approved w/Constraints [2, 4, 5, 6, 7] |
Authorized w/ Constraints [2, 4, 5, 6, 7] |
Authorized w/ Constraints [2, 4, 5, 6, 7] |
Authorized w/ Constraints [2, 4, 5, 6, 7] |
Authorized w/ Constraints [2, 4, 5, 6, 7] |
12.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
13.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
17.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints [2, 4, 5, 6, 7] |
Approved w/Constraints [2, 4, 5, 6, 7] |
Approved w/Constraints [2, 4, 5, 6, 7] |
Approved w/Constraints [2, 4, 5, 6, 7] |
Authorized w/ Constraints [2, 4, 5, 6, 7] |
Authorized w/ Constraints [2, 4, 5, 6, 7] |
Authorized w/ Constraints [2, 4, 5, 6, 7] |
Authorized w/ Constraints [2, 4, 5, 6, 7] |
18.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
21.x |
Approved w/Constraints [1, 2, 3, 4] |
Approved w/Constraints [1, 2, 3, 4] |
Approved w/Constraints [1, 2, 3, 4] |
Approved w/Constraints [1, 2, 3, 4] |
Authorized w/ Constraints [2, 4, 5, 6, 7] |
Approved w/Constraints [2, 4, 5, 6, 7] |
Approved w/Constraints [2, 4, 5, 6, 7] |
Approved w/Constraints [2, 4, 5, 6, 7] |
Authorized w/ Constraints [2, 4, 5, 6, 7] |
Authorized w/ Constraints [2, 4, 5, 6, 7] |
Authorized w/ Constraints [2, 4, 5, 6, 7] |
Authorized w/ Constraints [2, 4, 5, 6, 7] |
23.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints [2, 4, 5, 6, 7] |
Approved w/Constraints [2, 4, 5, 6, 7] |
Approved w/Constraints [2, 4, 5, 6, 7] |
Approved w/Constraints [2, 4, 5, 6, 7] |
Authorized w/ Constraints [2, 4, 5, 6, 7] |
Authorized w/ Constraints [2, 4, 5, 6, 7] |
Authorized w/ Constraints [2, 4, 5, 6, 7] |
Authorized w/ Constraints [2, 4, 5, 6, 7] |
| | [1] | Users must not utilize Docker Community, as it is at the time of writing, unapproved in the TRM.
Users must not utilize OpenJDK, as it is at the time of writing, unapproved in the TRM.
This technology must use the latest TRM-authorized version of Java Development Kit (JDK) - Oracle.
Per the Initial Product Review (IPR), users must abide by the following constraints:
- Azul Platform Core will require a 3rd party FIPS 140-2 (or its successor) certified solution for any data containing PHI/PII or VA sensitive information.
- Azul Platform Core should be administered only by the Desktop and Device Engineering team with access to this product restricted and limited to privileges that are needed to perform specific duties. Auditing logs should be reviewed in accordance with VA Handbook 6500 and Continuous Monitoring standards.
- Alternative solutions must only be authorized if the comparable authorized solution currently in place does not meet VA needs.
- This product should be used with a VA authorized container platform that has a developed and authorized baseline configuration with specific hardening guidance regarding the secure implementation of Azul Platform Core where applicable. Please reference the TRM for the authorized solution and the Baseline Configuration Management website for more information.
| | [2] | 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. | | [3] | 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. | | [4] | 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. | | [5] | Users must not utilize Docker Desktop (Personal), as determined during the time of this writing, an unauthorized technology in the TRM.
Users must not utilize Open Java Development Kit (OpenJDK), as it, at the time of writing, requires a POA&M.
This technology must use the latest TRM-authorized version of Java Development Kit (JDK) - Oracle.
Per the Initial Product Review (IPR), users must abide by the following constraints:
- Azul Platform Core will require a 3rd party FIPS 140-2 (or its successor) certified solution for any data containing PHI/PII or VA sensitive information.
- Azul Platform Core should be administered only by the Desktop and Device Engineering team with access to this product restricted and limited to privileges that are needed to perform specific duties. Auditing logs should be reviewed in accordance with VA Handbook 6500 and Continuous Monitoring standards.
- Alternative solutions must only be authorized if the comparable authorized solution currently in place does not meet VA needs.
- This product should be used with a VA authorized container platform that has a developed and authorized baseline configuration with specific hardening guidance regarding the secure implementation of Azul Platform Core where applicable. Please reference the TRM for the authorized solution and the Baseline Configuration Management website for more information.
| | [6] | 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. | | [7] | 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. |
|
Note: |
At the time of writing, versions 8.84.0.16 (8u442), 11.78.16, 17.56.16, 21.40.18, and 23.32.11 are the most current versions, released 01/21/2025. |