<Past |
Future> |
5.1.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
5.2.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
6.1.x |
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 [4, 5, 7] |
Approved w/Constraints [4, 5, 7] |
Approved w/Constraints [4, 5, 7] |
Approved w/Constraints [4, 5, 7] |
Divest [2, 4, 7, 8, 9, 10] |
Divest [2, 4, 7, 8, 9, 10] |
Unapproved |
Unapproved |
6.2.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Divest [2, 4, 7, 8, 9, 10] |
Divest [2, 4, 7, 8, 9, 10] |
Unapproved |
Unapproved |
6.3.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Divest [2, 4, 7, 8, 9, 10] |
Divest [2, 4, 7, 8, 9, 10] |
Unapproved |
Unapproved |
6.4.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Divest [2, 4, 7, 8, 9, 10] |
Divest [2, 4, 7, 8, 9, 10] |
Unapproved |
Unapproved |
6.5.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Divest [2, 4, 7, 8, 9, 10] |
Divest [2, 4, 7, 8, 9, 10] |
Unapproved |
Unapproved |
6.6.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| | [1] | Only instances of this technology that have been deployed may continue to use this technology. No further expansion or use of this technology is permitted without a waiver from the Architecture and Engineering Review Board (AERB) and expressed authorization from the Assistant Secretary/Chief Information Officer or the Principal Deputy Assistant Secretary for the Office of Information and Technology. | | [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] | 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. | | [5] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period. | | [6] | 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. | | [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.
The user should not use the Secure Sockets Layer (SSL) protocols with this technology, SSL is unapproved at this time.
Users must ensure that Microsoft Structured Query Language (SQL) Server, Microsoft .NET Framework, Apache Tomcat, and Java Runtime Environment (JRE) - Oracle are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
This technology must use the latest TRM-approved version of Java Runtime Environment (JRE) - Oracle. | | [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). | | [10] | New installations or major expansions of this technology that transmit data over the VA Wide Area Network (WAN) must complete a WAN impact review (yourIT Service Portal:[SNOW Service Requests]) prior to implementation to ensure proper compliance to VA network design and usage requirements. |
|
Note: |
At the time of writing, version 6.6.02 is the most current version, released 02/08/2024. |