<Past |
Future> |
17.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
18.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
19.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
20.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
21.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
22.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
23.x |
Divest [4, 7, 8, 9, 10] |
Divest [4, 7, 8, 9, 10] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
24.x |
Approved w/Constraints [4, 7, 8, 9, 10] |
Approved w/Constraints [4, 7, 8, 9, 10] |
Approved w/Constraints [4, 7, 8, 9, 10] |
Divest [7, 9, 10, 11, 12] |
Divest [7, 9, 10, 11, 12] |
Divest [7, 9, 10, 11, 12] |
Divest [7, 9, 10, 11, 12] |
Divest [7, 9, 10, 11, 12] |
Divest [7, 9, 10, 11, 12] |
Unapproved |
Unapproved |
Unapproved |
25.x |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [7, 9, 10, 11, 12] |
Approved w/Constraints [7, 9, 10, 11, 12] |
Approved w/Constraints [7, 9, 10, 11, 12] |
Approved w/Constraints [7, 9, 10, 11, 12] |
Approved w/Constraints [7, 9, 10, 11, 12] |
Approved w/Constraints [7, 9, 10, 11, 12] |
Approved w/Constraints [7, 9, 10, 11, 12] |
Approved w/Constraints [7, 9, 10, 11, 12] |
Approved w/Constraints [7, 9, 10, 11, 12] |
26.x |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [7, 9, 10, 11, 12] |
Approved w/Constraints [7, 9, 10, 11, 12] |
Approved w/Constraints [7, 9, 10, 11, 12] |
Approved w/Constraints [7, 9, 10, 11, 12] |
Approved w/Constraints [7, 9, 10, 11, 12] |
Approved w/Constraints [7, 9, 10, 11, 12] |
Approved w/Constraints [7, 9, 10, 11, 12] |
Approved w/Constraints [7, 9, 10, 11, 12] |
Approved w/Constraints [7, 9, 10, 11, 12] |
| | [1] | 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. | | [2] | 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. | | [3] | This technology has the option to be configured with Mnesia. Due to Mnesia`s relational database structure, it must not be configured with Erlang Open Telecom Platform (OTP). | | [4] | This technology has the option to be configured with Mnesia, a soft real-time database management system. Due to Mnesia`s relational database structure, it must not be configured with Erlang Open Telecom Platform (OTP). | | [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] | 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. | | [7] | This technology has received one or more VA security bulletins that provide specific guidance on vulnerability patching and mitigation. It is the responsibility of VA system owners to ensure that the appropriate mitigations are taken to address all known and future discovered vulnerabilities with this product. See the Reference tab for more information on security bulletins related to this product. | | [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] | 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. | | [11] | This technology has the option to be configured with Mnesia, a soft real-time database management system. Due to Mnesia`s relational database structure, it must not be configured with Erlang Open Telecom Platform (OTP).
Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM.
Users must not utilize the CentOS operating system, as it is unapproved for use on the TRM. | | [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 ISSO (Information System Security Officer) to ensure compliance with both VA Handbook 6500 and VA Directive 6500. |
|
Note: |
At the time of writing, version 26.1.1 is the most current version and was released 09/20/2023. |