<Past |
Future> |
4.0.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
6.1.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
6.2.x |
Divest [2, 3, 4, 5] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
6.3.x |
Approved w/Constraints [2, 3, 4, 5] |
Approved w/Constraints [2, 3, 4, 5] |
Approved w/Constraints [2, 3, 5, 6] |
Approved w/Constraints [2, 5, 6, 7] |
Approved w/Constraints [2, 5, 6, 7] |
Divest [2, 5, 6, 7] |
Divest [2, 5, 7, 8] |
Divest [2, 5, 7, 8] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
6.5.x |
Unapproved |
Unapproved |
Approved w/Constraints [2, 3, 5, 6] |
Approved w/Constraints [2, 5, 6, 7] |
Approved w/Constraints [2, 5, 6, 7] |
Approved w/Constraints [2, 5, 6, 7] |
Approved w/Constraints [2, 5, 7, 8] |
Approved w/Constraints [2, 5, 7, 8] |
Approved w/Constraints [2, 5, 7, 8] |
Approved w/Constraints [2, 5, 7, 8] |
Divest [2, 5, 7, 8] |
Divest [2, 5, 7, 8] |
6.6.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [2, 5, 6, 7] |
Approved w/Constraints [2, 5, 7, 8] |
Approved w/Constraints [2, 5, 7, 8] |
Approved w/Constraints [2, 5, 7, 8] |
Approved w/Constraints [2, 5, 7, 8] |
Divest [2, 5, 7, 8] |
Divest [2, 5, 7, 8] |
7.0.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [2, 5, 7, 8] |
Approved w/Constraints [2, 5, 7, 8] |
7.1.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| | [1] | Known security vulnerabilities must be properly remediated prior to product deployment. Product must remain properly patched per Federal and Department standards in order to mitigate known and future security vulnerabilities.
Per VA Handbook 6500, Federal Information Processing Standards (FIPS) 140-2 certified encryption must be used to encrypt data in transit and at rest if Personally Identifiable Information (PII), Protected Health Information (PHI) or VA sensitive information is involved or additional mitigating controls must be documented in an approved System Security Plan (SSP). Additionally, the technology must be implemented within the VA production network (not in a Demilitarized Zone (DMZ)). | | [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] | 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] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period. | | [5] | 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. | | [6] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
This technology comes bundled with Postgre SQL which is in a divestiture state. If users wish to operate this technology they must configure the technology to work with either Microsoft SQL Server or MySQL.
If users choose to operate MySQL they must note the following:
MySQL Database currently has TRM constraints for intranet use only due to its many known security issues. If MySQL is selected for use with this product, these factors should 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) | | [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] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period. This technology comes bundled with PostgreSQL. Baselines for PostgreSQL apply. (Refer to PostgreSQL TRM entry for more details.) Alternately, this product may be configured to utilize Microsoft SQL Server or MySQL.
If users choose to operate MySQL they must note the following: MySQL Database currently has TRM constraints for intranet use only due to its many known security issues. If MySQL is selected for use with this product, these factors should 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) |
|
Note: |
At the time of writing, version 7.1.4.2 is the most current version of this technology and was released 06/23/2022. |