2.x |
Approved w/Constraints [8, 9, 10, 11, 12] |
Approved w/Constraints [8, 9, 10, 11, 12] |
Approved w/Constraints [8, 9, 10, 11, 12] |
Approved w/Constraints [8, 9, 11, 12, 13] |
Approved w/Constraints [9, 11, 12, 13, 14, 15] |
Divest [9, 11, 12, 13, 14, 15] |
Divest [9, 11, 12, 13, 14, 15] |
Divest [9, 11, 12, 13, 14, 15] |
Divest [9, 11, 12, 13, 14, 15] |
Divest [9, 11, 12, 13, 14, 15] |
Divest [9, 11, 12, 13, 14, 15] |
Unapproved |
3.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [9, 11, 12, 13, 14, 15] |
Approved w/Constraints [9, 11, 12, 13, 14, 15] |
Approved w/Constraints [9, 11, 12, 13, 14, 15] |
Approved w/Constraints [9, 11, 12, 13, 14, 15] |
Approved w/Constraints [9, 11, 12, 13, 14, 15] |
Approved w/Constraints [9, 11, 12, 13, 14, 15] |
Approved w/Constraints [9, 11, 12, 13, 14, 15] |
| | [1] | 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. | | [2] | 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. | | [3] | 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. | | [4] | 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. | | [5] | This technology can potentially use an unapproved protocol Secure Sockets Layer (SSL), users should refrain from utilizing this protocol. | | [6] | 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. | | [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] | Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM. | | [9] | 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. | | [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 VA Handbook 6500. | | [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 approved 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] | 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. | | [14] | Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM.
Per the RHEL SME, this entry is only applicable to upstream versions and not the versions supplied and supported by Red Hat.
HAProxy 1.8 reached end of life status in Q4 of 2022 and is no longer supported by the vendor. | | [15] | 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. |
|