<Past |
Future> |
7.1 |
Divest
|
Divest
|
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
7.5 |
Divest
|
Divest
|
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
8.0 |
Approved |
Approved |
Approved w/Constraints [1, 2] |
Approved w/Constraints [1, 2] |
Approved w/Constraints [1, 2] |
Approved w/Constraints [1, 2] |
Approved w/Constraints [1, 2] |
Divest [2, 3, 4] |
Divest [2, 3, 4] |
Divest [2, 3, 4] |
Divest [2, 3, 4] |
Divest [2, 4, 5] |
8.1 |
Approved |
Approved |
Approved w/Constraints [1, 2] |
Approved w/Constraints [1, 2] |
Approved w/Constraints [1, 2] |
Approved w/Constraints [1, 2] |
Approved w/Constraints [1, 2] |
Divest [2, 3, 4] |
Divest [2, 3, 4] |
Divest [2, 3, 4] |
Divest [2, 3, 4] |
Divest [2, 4, 5] |
8.5 |
Approved |
Approved |
Approved w/Constraints [1, 2] |
Approved w/Constraints [1, 2] |
Approved w/Constraints [1, 2] |
Approved w/Constraints [1, 2] |
Approved w/Constraints [1, 2] |
Divest [2, 3, 4] |
Divest [2, 3, 4] |
Divest [2, 3, 4] |
Divest [2, 3, 4] |
Divest [2, 4, 5] |
8.7.x |
Approved |
Approved |
Approved w/Constraints [1, 2] |
Approved w/Constraints [1, 2] |
Approved w/Constraints [1, 2] |
Approved w/Constraints [1, 2] |
Approved w/Constraints [1, 2] |
Divest [2, 3, 4] |
Divest [2, 3, 4] |
Divest [2, 3, 4] |
Divest [2, 3, 4] |
Divest [2, 4, 5] |
8.8.x |
Unapproved |
Unapproved |
Approved w/Constraints [1, 2] |
Approved w/Constraints [1, 2] |
Approved w/Constraints [1, 2] |
Approved w/Constraints [1, 2] |
Approved w/Constraints [1, 2] |
Approved w/Constraints [2, 3, 4] |
Approved w/Constraints [2, 3, 4] |
Approved w/Constraints [2, 3, 4] |
Approved w/Constraints [2, 3, 4] |
Approved w/Constraints [2, 4, 5] |
8.9.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [2, 4, 5] |
8.10.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
8.11.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| | [1] | 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). | | [2] | 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. | | [3] | 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 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). | | [4] | 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). | | [5] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period. |
|
Note: |
At the time of writing, version 8.11.0 is the most current version, released 01/27/2022. |