<Past |
Future> |
7.5 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
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) |
8.0 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
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) |
8.1 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
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) |
8.2 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
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) |
8.3 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
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) |
2017 (9.0.x) |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
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) |
2018 SP1 (10.x) |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
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) |
2019 (11.0) |
DIVEST [12, 13, 14, 15, 16] |
DIVEST [12, 13, 14, 15, 16] |
Unapproved |
Unapproved |
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) |
2021 (13.x) |
Approved w/Constraints [12, 13, 14, 15, 16] |
Approved w/Constraints [12, 13, 14, 15, 16] |
Approved w/Constraints [12, 13, 14, 15, 16] |
DIVEST [13, 15, 16, 17, 18, 19] |
DIVEST [13, 15, 17, 18, 19, 20] |
DIVEST [13, 15, 17, 18, 19, 20] |
DIVEST [13, 15, 17, 18, 19, 20] |
Authorized w/ Constraints (DIVEST) [13, 15, 17, 18, 19, 20] |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
2022.x |
Unapproved |
Unapproved |
Unapproved |
DIVEST [13, 15, 16, 17, 18, 19] |
DIVEST [13, 15, 17, 18, 19, 20] |
DIVEST [13, 15, 17, 18, 19, 20] |
DIVEST [13, 15, 17, 18, 19, 20] |
Authorized w/ Constraints (DIVEST) [13, 15, 17, 18, 19, 20] |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
2023.x |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [13, 15, 16, 17, 18, 19] |
Approved w/Constraints [13, 15, 17, 18, 19, 20] |
Approved w/Constraints [13, 15, 17, 18, 19, 20] |
DIVEST [13, 15, 17, 18, 19, 20] |
Authorized w/ Constraints (DIVEST) [13, 15, 17, 18, 19, 20] |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
2023.0.11+ |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
DIVEST [13, 15, 17, 18, 19, 20] |
Authorized w/ Constraints (DIVEST) [13, 15, 17, 18, 19, 20] |
Authorized w/ Constraints (DIVEST) [13, 15, 17, 18, 19, 20] |
Authorized w/ Constraints (DIVEST) [13, 15, 17, 18, 19, 20] |
Authorized w/ Constraints (DIVEST) [13, 15, 17, 18, 19, 20] |
Authorized w/ Constraints (DIVEST) [13, 15, 17, 18, 19, 20] |
2023.1.6+ |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
DIVEST [13, 15, 17, 18, 19, 20] |
Authorized w/ Constraints (DIVEST) [13, 15, 17, 18, 19, 20] |
Authorized w/ Constraints (DIVEST) [13, 15, 17, 18, 19, 20] |
Authorized w/ Constraints (DIVEST) [13, 15, 17, 18, 19, 20] |
Authorized w/ Constraints (DIVEST) [13, 15, 17, 18, 19, 20] |
Authorized w/ Constraints (DIVEST) [13, 15, 17, 18, 19, 20] |
2024.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
DIVEST [13, 15, 17, 18, 19, 20] |
Authorized w/ Constraints (DIVEST) [13, 15, 17, 18, 19, 20] |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
2024.0.2+ |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [13, 15, 17, 18, 19, 20] |
Authorized w/ Constraints [13, 15, 17, 18, 19, 20] |
Authorized w/ Constraints [13, 15, 17, 18, 19, 20] |
Authorized w/ Constraints [13, 15, 17, 18, 19, 20] |
Authorized w/ Constraints [13, 15, 17, 18, 19, 20] |
Authorized w/ Constraints [13, 15, 17, 18, 19, 20] |
| | [1] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period. | | [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 ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | [3] | Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). | | [4] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
This technology supports the use of data transfer via FTP, SSH and SFTP. Data transfer must occur over SSH or SFTP. | | [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] | Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). | | [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 ISO can provide assistance in reviewing the NIST vulnerabilities. | | [8] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
This product can be configured with a MySQL Database, which currently has TRM constraints due to its many known security issues. If MySQL is selected for use with this product, these factors must be considered especially when an instance of this product will be considered a Moderate or High-Risk system (Refer to MySQL Database TRM entry for more details). | | [9] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
This technology must use the latest version of Java Runtime Environment (JRE) - Oracle.
Users must ensure that Firefox, Google Chrome, Microsoft .NET Framework, Microsoft Internet Explorer (IE), Microsoft Internet Information Services (IIS), Microsoft Structured Query Language (SQL) Server, and Safari are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) | | [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 ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | [11] | Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). | | [12] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
This technology must use the latest version of Java Runtime Environment (JRE) - Oracle.
Users must ensure that Firefox, Google Chrome, Microsoft .NET Framework, Microsoft Internet Explorer (IE), Microsoft Internet Information Services (IIS), Microsoft Structured Query Language (SQL) Server, and Safari are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Users must Divest the use of Internet Explorer with this technology. Other authorized internet browsers are available. See Category Tab for details.
The File Transfer Protocol (FTP) features of this software must not be used as the FTP protocol is prohibited for use on the VA network. (For further information see: VA Policy Memo VAIQ 7615193 on Prohibited Use of File Transfer Protocol (FTP) and Telnet Services)
The Secure Socket Layer (SSL) features of this software must not be used as the SSL protocol is prohibited for use on the VA network. | | [13] | 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. | | [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] | Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information System Security Officer (ISSO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). | | [17] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
This technology must use the latest version of Java Runtime Environment (JRE) - Oracle.
Users must ensure that Firefox, Google Chrome, Microsoft Edge, Microsoft Internet Information Services (IIS), Microsoft Structured Query Language (SQL) Server, and MySQL are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
The File Transfer Protocol (FTP) features of this software must not be used as the FTP protocol is prohibited for use on the VA network. (For further information see: VA Policy Memo VAIQ 7615193 on Prohibited Use of File Transfer Protocol (FTP) and Telnet Services)
The Secure Socket Layer (SSL) features of this software must not be used as the SSL protocol is prohibited for use on the VA network. | | [18] | If this product uses a MySQL database, the product must be configured with a commercial edition of the MySQL Database, which currently has TRM constraints limiting its use for intranet and non-sensitive data only due to its many known security issues. If a commercial edition of MySQL is selected for use with this product, these factors must be considered especially when an instance of this product will be considered a Moderate or High-Risk system. See MySQL Database – Commercial Edition TRM entry for more details. | | [19] | 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. | | [20] | Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 or its successor to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 or 140-3 compliant full disk encryption (FOE) must be implemented on the storage device where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information System Security Officer (ISSO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). By September 22, 2026, all FIPS 140-2 certificate validations will be placed on the Historical List, please refer to FIPS Transition Effort for further guidance and timeline of changes. |
|
Note: |
At the time of writing, version 2024.0.2 is the most current version, released 06/11/2024.
Due to security vulnerabilities, users are permitted to use minor releases and patches X.X and later as identified by the ‘+’ versioning. |