<Past |
Future> |
9.5 |
Divest [5, 6] |
Divest [5, 6, 7] |
Divest [5, 6, 7] |
Divest [5, 6, 7] |
Divest [5, 6, 7] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
9.6 |
Approved w/Constraints [5, 6] |
Approved w/Constraints [5, 6, 7] |
Approved w/Constraints [5, 6, 7] |
Approved w/Constraints [5, 6, 7] |
Approved w/Constraints [5, 6, 7] |
Divest [5, 6, 7, 8, 9] |
Divest [5, 6, 7, 8, 9] |
Divest [5, 6, 7, 8, 9] |
Divest [5, 6, 7, 8, 10] |
Unapproved |
Unapproved |
Unapproved |
9.8.x |
Unapproved |
Approved w/Constraints [5, 6, 7] |
Approved w/Constraints [5, 6, 7] |
Approved w/Constraints [5, 6, 7] |
Approved w/Constraints [5, 6, 7] |
Divest [5, 6, 7, 8, 9] |
Divest [5, 6, 7, 8, 9] |
Divest [5, 6, 7, 8, 9] |
Divest [5, 6, 7, 8, 10] |
Unapproved |
Unapproved |
Unapproved |
9.9.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [5, 6, 7, 8, 9] |
Approved w/Constraints [5, 6, 7, 8, 9] |
Approved w/Constraints [5, 6, 7, 8, 9] |
Approved w/Constraints [5, 6, 7, 8, 10] |
Divest [5, 6, 7, 10, 11] |
Divest [5, 6, 7, 10, 11] |
Divest [5, 6, 7, 10, 11] |
10.4.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [5, 6, 7, 10, 11] |
Approved w/Constraints [5, 6, 7, 10, 11] |
Approved w/Constraints [5, 6, 7, 10, 11] |
10.5.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| | [1] | Projects using this technology must comply with Federal and Department of Veterans Affairs (VA) Information Protection requirements, and ensure sensitive information is stored in a Federal Information Processing Standards (FIPS) 140-2 certified database and is encrypted for both storage and transmission across the network. | | [2] | 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.
| | [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] | 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. | | [6] | 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). | | [7] | 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. | | [8] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period. | | [9] | 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). | | [10] | 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 with the Project Special Forces (SPF) team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | [11] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must ensure that Microsoft Structured Query Language (SQL) Server and Oracle Database are implemented with VA-approved baselines. |
|
Note: |
At the time of writing, version 10.5.3 is the most current version, released 01/30/2023. |