<Past |
Future> |
5.0 |
Unapproved |
Unapproved |
Unapproved |
Divest [3, 4] |
Divest [4, 5, 6] |
Divest [4, 5, 6, 7] |
Divest [4, 5, 6] |
Divest [4, 5, 6] |
Divest [4, 5, 6] |
Divest [4, 5, 6] |
Divest [6, 8, 9] |
Divest [6, 8, 9] |
7.0 |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [3, 4] |
Approved w/Constraints [4, 5, 6] |
Approved w/Constraints [4, 5, 6, 7] |
Approved w/Constraints [4, 5, 6] |
Approved w/Constraints [4, 5, 6] |
Approved w/Constraints [4, 5, 6] |
Approved w/Constraints [4, 5, 6] |
Approved w/Constraints [6, 8, 9] |
Approved w/Constraints [6, 8, 9] |
8.0 |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [1, 3, 4] |
Approved w/Constraints [1, 4, 5, 6] |
Approved w/Constraints [1, 4, 5, 6, 7] |
Approved w/Constraints [1, 4, 5, 6] |
Approved w/Constraints [1, 4, 5, 6] |
Approved w/Constraints [4, 5, 6] |
Approved w/Constraints [4, 5, 6] |
Approved w/Constraints [6, 8, 9] |
Approved w/Constraints [6, 8, 9] |
15.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [1, 4, 5, 6] |
Approved w/Constraints [1, 4, 5, 6] |
Approved w/Constraints [1, 6, 8, 9] |
Approved w/Constraints [1, 6, 8, 9] |
16.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
17.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
18.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
19.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
20.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
21.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
22.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
23.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
24.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| | [1] | 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. | | [2] | Product must remain patched and operated in accordance with Federal and Department security and privacy policies and guidelines. | | [3] | 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. Contact your local CIO office if more information is needed in regards to the use of this technology. | | [4] | 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. | | [5] | Release 8.0 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. Contact your local CIO office if more information is needed in regards to the use of this technology. Release 7.0 is currently approved w/constraints listed. (Refer to the Decision tab for more details) | | [6] | 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. | | [7] | As of April 23, 2015, per the Deputy CIO of Architecture, Strategy and Design (ASD), all technologies in use by the VA require an assessment by the VA Section 508 office. Section 508 of the Rehabilitation Act Amendments of 1998 is a federal law that sets the guidelines for technology accessibility. A VA Section 508 assessment of this technology has not been completed at the time of publication. Therefore, as of April 23, 2015 only users of this technology who have deployed the technology to the production environment, or have project design and implementation plans approved, may continue to operate this technology. In the case of a project that has implemented, or been approved for a specific site or number of users, and that project needs to expand operations to other sites or to an increased user base, it may do so as long as the project stays on the existing version of the technology that was approved or implemented as of April 22, 2015. Use of this technology in all other cases is prohibited.
| | [8] | Version 8 of this technology is the approved version of this technology. Version 15.x is planned as the next production environment, though a startup date has not been determined. Use of version 15.x is strictly controlled and not available for use within the general population. | | [9] | 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). |
|
Note: |
At the time of writing, version 24.4 is the most current version. |