| 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 System Security Officer (ISSO), 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> |
| 23.x |
Authorized w/ Constraints (DIVEST)
[2, 3, 4, 5, 6, 7, 8, 9, 10, 11] |
Authorized w/ Constraints (DIVEST)
[2, 3, 4, 5, 6, 7, 8, 9, 10, 11] |
Authorized w/ Constraints (DIVEST)
[2, 3, 4, 5, 6, 7, 8, 9, 10, 11] |
Authorized w/ Constraints (DIVEST)
[2, 3, 4, 5, 6, 7, 8, 9, 10, 11] |
Authorized w/ Constraints (DIVEST)
[2, 3, 4, 5, 6, 7, 8, 9, 10, 11] |
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) |
| 24.x |
Authorized w/ Constraints
[2, 3, 4, 5, 6, 7, 8, 9, 10, 11] |
Authorized w/ Constraints
[2, 3, 4, 5, 6, 7, 8, 9, 10, 11] |
Authorized w/ Constraints
[2, 3, 4, 5, 6, 7, 8, 9, 10, 11] |
Authorized w/ Constraints
[2, 3, 4, 5, 6, 7, 8, 9, 10, 11] |
Authorized w/ Constraints
[2, 3, 4, 5, 6, 7, 8, 9, 10, 11] |
Authorized w/ Constraints
[2, 3, 4, 5, 6, 7, 8, 9, 10, 11] |
Authorized w/ Constraints
[2, 3, 4, 5, 6, 7, 8, 9, 10, 11] |
Authorized w/ Constraints
[2, 3, 4, 5, 6, 7, 8, 9, 10, 11] |
Authorized w/ Constraints
[2, 3, 4, 5, 6, 7, 8, 9, 10, 11] |
Authorized w/ Constraints
[2, 3, 4, 5, 6, 7, 8, 9, 10, 11] |
Authorized w/ Constraints
[2, 3, 4, 5, 6, 7, 8, 9, 10, 11] |
Authorized w/ Constraints
[2, 3, 4, 5, 6, 7, 8, 9, 10, 11] |
| Note: |
At the time of writing, version 24.2 is the most current version, released 09/09/2024. |
| | | | [2] | This product can be configured with a PostgreSQL Database, which currently has TRM constraints limiting its use to Red Hat Enterprise Linux (RHEL) only due to its many known security issues on other platforms. If PostgreSQL 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 PostgreSQL Database TRM entry for more details. | | | [3] | 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. | | | [4] | 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. | | | [5] | 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. | | | [6] | 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. | | | [7] | In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004 , VA Directive 6517, and VA Directive 6513. The local ISSO (Information System Security Officer) can advise on the ESCCB review process. | | | [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 both VA Handbook 6500 and VA Directive 6500. | | | [9] | 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. | | | [10] | Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request, visit the Product Marketplace. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | | [11] | 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 TRM-authorized version of Java Development Kit (JDK) - Oracle.
Users must not utilize the Secure Sockets Layer (SSL) protocol, as it requires a POA&M.
This technology must use the latest TRM-authorized version of Java Runtime Environment (JRE) - Oracle.
This technology can be deployed with Kubernetes. At the time of writing, the baseline for Kubernetes dictates that it can only be used in on-premises in Amazon Web Services (AWS) VA Enterprise Cloud (VAEC) implementations.
Users must ensure that when using OpenSSL that authorized versions are utilized.
Users must not utilize Amazon Redshift Java Database Connectivity (JDBC) Driver, Apache Cassandra, Cockroach Database (CockroachDB), CouchDB, MariaDB, MongoDB Open Database Connectivity (ODBC) Driver, Redis, MySQL - Community Edition, ZLib and SQLite Java Database Connectivity (JDBC), as they are at the time of writing, unapproved in the TRM.
This technology should not be used with Open Java Development Kit (OpenJDK) as it requires a POA&M. There are other authorized java environments available. See Category tab for details.
This technology can utilize commercial cloud storage options (Google Drive, Dropbox, etc.). These services require a POA&M for use on the VA network.
Users must ensure that Kubernetes, Microsoft Access, Microsoft Structured Query Language (SQL) Server, Oracle Database (DB), MongoDB Enterprise Advanced, MySQL - Commercial, and PostgreSQL are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Per the Security Assessment Review, users must abide by the following constraints:
- DBeaver Enterprise will require a 3rd party FIPS 140-2 or its successor certified solution for any data containing PHI/PII or VA sensitive information.
- System owners should use the latest version of this product and monitor both the CVE Details and NIST NVD websites for any new security vulnerabilities.
- 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.
- Users should be instructed NOT to select the Data Share option during installation. If they do, it should be turned off as soon as possible in the application’s Preferences menu
- To mitigate, the ISSO shall educate and prohibit users from using the integrated cloud service capability until the VA Cloud Security Requirements have been met and the affected A&A package has been appropriately updated
- Users should be instructed not to use this option. Only VA Authorized versions of this product should be used.
- Vulnerability exists because DBeaver Enterprise Edition installs 26 .exe files without a digital signature. This prevents the verification of the control`s publisher and assurance that it has not been tampered with since being published. To mitigate, an administrator shall monitor the .exe and .dll files used by the application with a file integrity checker to ensure no unauthorized changes occur.
- To mitigate, Exploit Protection mitigations in Windows 10 must be configured for java.exe, javaw.exe, and javaws.exe.
- To mitigate, system administrators shall use the latest version of the product where possible and monitor both the CVE Details and NIST NVD websites for any new security vulnerabilities.
- To mitigate, system administrators shall use the latest version of the product where possible and monitor both the CVE Details and NIST NVD websites for any new security vulnerabilities.
- To mitigate, system administrators shall use the latest version of the product where possible and monitor both the CVE Details and NIST NVD websites for any new security vulnerabilities.
- To mitigate, system administrators shall use the latest version of the product where possible and monitor both the CVE Details and NIST NVD websites for any new security vulnerabilities.
This technology or standard can be used only if a POA&M review is conducted and signed by the AODR as designated by the 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.
- To mitigate, system administrators shall use the latest version of the product where possible and monitor both the CVE Details and NIST NVD websites for any new security vulnerabilities.
This technology or standard can be used only if a POA&M review is conducted and signed by the AODR as designated by the 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.
- To mitigate, system administrators shall use the latest version of the product where possible and monitor both the CVE Details and NIST National Vulnerability Database websites for any new security vulnerabilities.
This technology or standard can be used only if a POA&M review is conducted and signed by the AODR as designated by the 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.
- To mitigate, system administrators shall use the latest version of the product where possible and monitor both the CVE Details and NIST NVD websites for any new security vulnerabilities.
This technology or standard can be used only if a POA&M review is conducted and signed by the AODR as designated by the 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.
|
|
