<Past |
Future> |
6.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
7.x |
Divest [2, 3, 4, 5] |
Divest [2, 3, 4, 5] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
8.0.x |
Approved w/Constraints [2, 3, 4, 5] |
Approved w/Constraints [2, 3, 4, 5] |
Approved w/Constraints [2, 3, 4, 5] |
Approved w/Constraints [2, 6, 7, 8, 9] |
Approved w/Constraints [2, 6, 7, 9, 10] |
Approved w/Constraints [2, 6, 7, 9, 10] |
Divest [2, 6, 7, 9, 10] |
Divest [2, 6, 7, 9, 10] |
Divest [2, 6, 7, 9, 10] |
Unapproved |
Unapproved |
Unapproved |
8.2.x |
Approved w/Constraints [2, 3, 4, 5] |
Approved w/Constraints [2, 3, 4, 5] |
Approved w/Constraints [2, 3, 4, 5] |
Approved w/Constraints [2, 6, 7, 8, 9] |
Approved w/Constraints [2, 6, 7, 9, 10] |
Approved w/Constraints [2, 6, 7, 9, 10] |
Divest [2, 6, 7, 9, 10] |
Divest [2, 6, 7, 9, 10] |
Divest [2, 6, 7, 9, 10] |
Divest [2, 6, 7, 9, 10] |
Unapproved |
Unapproved |
8.6.x |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [2, 6, 7, 8, 9] |
Approved w/Constraints [2, 6, 7, 9, 10] |
Approved w/Constraints [2, 6, 7, 9, 10] |
Approved w/Constraints [2, 6, 7, 9, 10] |
Divest [2, 6, 7, 9, 10] |
Divest [2, 6, 7, 9, 10] |
Divest [2, 6, 7, 9, 10] |
Divest [2, 6, 7, 9, 10] |
Unapproved |
8.7.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [2, 6, 7, 9, 10] |
Approved w/Constraints [2, 6, 7, 9, 10] |
Approved w/Constraints [2, 6, 7, 9, 10] |
Approved w/Constraints [2, 6, 7, 9, 10] |
Approved w/Constraints [2, 6, 7, 9, 10] |
Approved w/Constraints [2, 6, 7, 9, 10] |
8.9.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| | [1] | Per VA Handbook 6500 (Appendix F) all systems with a Moderate or High risk assessment are required to use a FIPS 140-2 compliant DBMS solution, including backup, to protect information at rest or have mitigating controls documented in an approved System Security Plan (SSP) for the system. It is the responsibility of the system owner to ensure that an appropriate DBMS backup and encryption technology is selected or that mitigating controls are in place and documented in the SSP. Additionally, if Personally Identifiable Information (PII), Protected Health Information (PHI) and/or VA Sensitive data is involved, FIPS 140-2 certified encryption must be used to encrypt data in transit and at rest and the technology must be implemented within the VA production network (not in a DMZ) or additional mitigating controls must be documented in an approved 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] | 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] | 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] | Due to potential information security risks, cloud based versions of this product are not permitted without a waiver signed by the Deputy CIO of ASD based upon a recommendation from the Architecture and Engineering Review Board (AERB). In addition, cloud based features of this software may not be used without an Enterprise Security Change Control Board (ESCCB) approval to ensure that confidential organization and/or PII/PHI data are not compromised (ref: VA Directive 6004, VA Directive 6517 and VA Directive 6513). Use of public cloud storage requires documented Federal Risk and Authorization Management Program (FedRAMP) compliance and a Memorandum of Understanding / Interconnection Security Agreement (MOU/ISA) between the vendor and VA prior to ESCCB review. | | [6] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period. | | [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] | Due to potential information security risks, cloud based technologies may not be used without the approval of the VA Enterprise Cloud Services (ECS) Group. This body is in part responsible for ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | [9] | 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. | | [10] | Due to potential information security risks, cloud based technologies may not be used without the approval of the Enterprise Cloud Solution Office (ECSO). This body is in part responsible for ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). |
|
Note: |
At the time of writing, version 8.9.8 is the most current version, released 06/01/2024. |