Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 24.11

DBeaver Enterprise

General Information

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website:	Go to site
Description:	DBeaver is a universal database management program for users who need to work with data. With DBeaver the user is able to manipulate data, for example, in a regular spreadsheet, create analytical reports based on records from different data storages, and export information in an appropriate format. For advanced database users, DBeaver uses an SQL-editor, plenty of administration features, abilities of data and schema migration, and monitoring database connection sessions. This technology does not use a database to store data. This technology is utilizes Java Database Connectivity (JDBC) and Open Database Connectivity (ODBC) to integrate with multiple Structured Query Language (SQL), NoSQL, and Cloud databases, including but not limited to Microsoft SQL Server, Oracle Database (DB), MySQL, PostgreSQL, MariaDB, DB2, MongoDB, Apache Cassandra, Redis, and CouchDB. The TRM decisions in this entry only apply to technologies and versions owned, operated, managed, patched, and version-controlled by VA. This includes technologies deployed as software installations on VMs within VA-controlled cloud environments (e.g. VA Enterprise Cloud (VAEC)). Cloud services provided by the VAEC, which are listed in the VAEC Service Catalog, and those controlled and managed by an external Cloud Service Provider (i.e. SaaS) are not in the purview of the TRM. For more information on the use of cloud services and cloud-based products within VA, including VA private clouds, please see the Enterprise Cloud Solutions Office (ECSO) Portal at: https://dvagov.sharepoint.com/sites/OITECSO
Technology/Standard Usage Requirements:	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 Security Officer (ISO), 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.
Section 508 Information:	This technology has not been assessed by the Section 508 Office. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. For additional information or assistance regarding Section 508, please contact the Section 508 Office at Section508@va.gov
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v24.3
Decision Date:	03/18/2024 at 23:36:52 UTC
Aliases:	DBeaver Pro
Introduced By:	TRM Request
Vendor Name:	DBeaver

Vendor Release Information

The Vendor Release table provides the known releases for the TRM Technology, obtained from the vendor (or from the release source).

You must be logged into the RSAA website prior to clicking the Attestation URLs or the URLs won't open.

Version	Release Date	Vendor End of Life Date	Vendor Desupport Date
23.x	03/13/2023

Current Decision Matrix (03/12/2024)

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 Security Officer (ISO), 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

CY2022

CY2023

CY2024

Future>

Release

23.x

Unapproved

Approved w/Constraints
[1, 2, 3, 4, 5, 6, 7, 8, 9, 10]

Authorized w/ Constraints
[1, 2, 3, 4, 5, 6, 7, 8, 9, 10]

Decision Constraints


[1]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. Users must Divest the use of Amazon Redshift Java Database Connectivity (JDBC) Driver with this technology. 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 is unapproved for use on the TRM. 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 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 is unapproved for use at this time. 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 are unapproved in the VA and these options must not be utilized. Users must ensure that Kubernetes, Microsoft Access, Microsoft Structured Query Langugage (SQL) Server, Oracle Database (DB), MongoDB Enterprise Advanced, MySQL - Commerical, 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: 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. System owners must ensure they are using the most recent, TRM authorized, version of DBeaver Enterprise v23.x. DBeaver Enterprise v23.3.0 will require a 3rd party FIPS 140-2 or its successor certified solution for any data containing PHI/PII or VA sensitive information. TRM provides the following guidance for unapproved software: 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. Unapproved: 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 check vendor documentation for instructions on installing and using a VA authorized JDK Platform. System owners shall use the latest version of these products where possible and monitor both the CVE Details and NIST National Vulnerability Database websites for any new security vulnerabilities. To mitigate, System owners should use the latest version of these products where possible and monitor both the CVE Details andNIST National Vulnerability Database websites for any new security vulnerabilities. Unapproved: 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. 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. To mitigate, administrators shall choose not to participate in the program by disabling it during installation or through the application menu. To mitigate, administrators shall control the versioning of DBeaver Enterprise version 23.x software and not allow users to install unapproved versions.

[2]	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.

[3]	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.

[4]	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.

[5]	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.

[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 ISSO (Information System Security Officer) to ensure compliance with both VA Handbook 6500 and VA Directive 6500.

[7]	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.

[8]	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).

[9]	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.

[10]	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.

Note:

At the time of writing, version 23.3.0 is the most current version, released 12/11/2023.

Type	Name	Source	Description
*NOTE: Vendor provided information is subject to the accuracy of the manufacturer.

Name	Description
Open Java Development Kit (OpenJDK)	Open Java Development Kit (OpenJDK) is a managed component that comes included in all DBeaver distributions. The user can change the default JDK version by replacing directory jre in dbeaver installation folder.


Information Management Technologies Data Management	Database-Related Management Tools

General Analysis

Adoption Benefits

This technology has a comprehensive set of documentation.
This technology may improve productivity for specific staff whose responsibilities include database management and data manipulation.
This technology optionally extends the functionality of Microsoft Office technologies.
This technology utilizes built-in Authentication and Authorization (A&A) capabilities.

Adoption Risks

This technology has a free trial period, which carries the potential for the disruption of service delivery and inaccurate financial planning.
This technology relies on Java Development Kit (JDK) - Oracle, which has a rapid release and update schedule.
This technology can potentially use Secure Sockets Layer (SSL), an unapproved protocol.
This technology can potentially use Open Java Development Kit (OpenJDK), an unapproved protocol.
This technology can be implemented with Kubernetes. At the time of writing, Kubernetes is limited to on premises VA Enterprise Cloud implementations on Amazon Web Services (AWS) Servers. Other uses of this technology are unapproved.
There are other authorized solutions that provide similar functionality available on the TRM. The use of several similar solutions may increase organization requirements for support and maintenance.
The technology requires the purchase of licenses from vendor, which could potentially lead to vendor lock-in.
This technology can potentially integrate with Apache Cassandra, Cockroach Database (CockroachDB), CouchDB, MariaDB, MongoDB Open Database Connectivity (ODBC) Driver, Redis, MySQL - Community Edition, ZLib and SQLite Java Database Connectivity (JDBC), unapproved technologies.
This technology can integrate with and alter database technologies.
There are known Common Vulnerabilities and Exposures (CVEs) associated with this technology. Please see https://nvd.nist.gov/vuln/search for more details.
This technology may utilize external data connections.
The potential exists to store Personally Identifiable Information (PII), Protected Health Information (PHI) and/or VA Sensitive data and proper security standards must be followed in these cases.
Due to the rapid release schedule of this technology, the VA may be unable to update to the most recent patch and may require a deployment model requiring the use of specific versions.
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.
This product can be configured with a MySQL Commercial Edition 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.
DBeaver Enterprise v23.3.0 is not FIPS 140-2 or its successor certified.
This technology can potentially use Open Secure Socket Layer (OpenSSL), which users must ensure that authorized versions are utilized.
A vulnerability exists because DBeaver Enterprise v23.3.0 installs 26 .exe files without a digital signature. This prevents the verification of the files publisher and assurance that it has not been tampered with since being published.
A vulnerability exists because there is a published vulnerability for DBeaver before version 21.2.3.
A vulnerability exists because DBeaver Enterprise v23.3.0 installs an outdated version of zlib (1.2.13) which is listed as Unapproved on the VA Technical Reference Model.
A vulnerability exists because DBeaver Enterprise v23.3.0 installs an outdated version of OpenJDK v17.0.6.0 which is listed as Unapproved on the VA Technical Reference Model (TRM).
A vulnerability exists because DBeaver Enterprise v23.3.0 installed an outdated SQLite JDBC file for its sample database. There is a published vulnerability for the SQLite JDBC version used.
A vulnerability exists because DBeaver Enterprise v23.3.0 installs outdated versions of OpenSSL (1.1.1d) and (3.0.9). OpenSSL 1.1.1d is listed as Unapproved on the VA Technical Reference Model (TRM). Both versions have multiple published vulnerabilities.
A vulnerability exists because DBeaver Enterprise version 23.3.0 utilizes commercial cloud computing services.
A vulnerability exists because DBeaver Enterprise version 23.3.0 includes a Software Improvement Program which automatically sends various types of information back to the Vendor.
A vulnerability exists because DBeaver Enterprise version 23.3.0 provides automatic/user configurable checks for updates.
Amazon Redshift Java Database Connectivity (JDBC) Driver, an optional dependency of this technology, is in a divested state at the time of writing.
This technology relies on Java Runtime Environment (JRE) - Oracle, which has a rapid release and update schedule.

Architectural Benefits

This technology is portable as it runs on multiple TRM-authorized operating systems.
This technology is compatible with multiple other Technical Reference Model (TRM) technologies and standards used by the organization.
This technology can use a VA-preferred database.
This technology is compatible with virtual machines, therefore consistent with the enterprise Server Virtualize First Policy (VAIQ 7266972 08-27-2012).

Architectural Risks

This technology includes cloud-based functionality which has potential information security risks.
This technology can potentially utilize commercial cloud storage options.

- The information contained on this page is accurate as of the Decision Date (03/18/2024 at 23:36:52 UTC).

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 24.11

General Information

Vendor Release Information

Current Decision Matrix (03/12/2024)

Decision Constraints

References

Technology Components

VA Categories

View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Optional Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 24.11

General Information

Vendor Release Information

Current Decision Matrix (03/12/2024)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Optional Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

EMAIL UPDATES

VA Categories

View the VA Categorization Framework