<Past |
Future> |
8.0 (Win) |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
8.0 Patch 1 (Win) |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
8.0 Patch 2 (Win) |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
8.0 Patch 3 (Win) |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
8.0 Patch 4 (Win) |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
8.0 Patch 5 (Win) |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
8.0 Patch 6 (Win) |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
8.0 Patch 7 (Win) |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
8.0 Patch 8 (Win) |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
8.0 Patch 9 (Win) |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
8.0 Patch 10 (Win) |
Approved w/Constraints [6, 9, 12, 14] |
Approved w/Constraints [6, 9, 12, 14] |
Approved w/Constraints [6, 9, 12, 14] |
Approved w/Constraints [6, 9, 12, 14] |
Approved w/Constraints [6, 9, 12, 14] |
Approved w/Constraints [6, 9, 12, 14] |
Approved w/Constraints [6, 9, 12, 14] |
Approved w/Constraints [6, 9, 12, 14] |
Divest [6, 15, 16, 17, 18, 19] |
Divest [6, 15, 16, 17, 18, 19] |
Divest [6, 15, 16, 17, 18, 19] |
Divest [6, 15, 16, 17, 18, 19] |
8.0 Patch 11 (Win) |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
8.0 Patch 12 (Win) |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
8.0 Patch 13 (Win) |
Approved w/Constraints [1, 6, 9, 12, 14] |
Approved w/Constraints [1, 6, 9, 12, 14] |
Approved w/Constraints [1, 6, 9, 12, 14] |
Approved w/Constraints [1, 6, 9, 12, 14] |
Approved w/Constraints [1, 6, 9, 12, 14] |
Approved w/Constraints [1, 6, 9, 12, 14] |
Approved w/Constraints [1, 6, 9, 12, 14] |
Approved w/Constraints [1, 6, 9, 12, 14] |
Divest [6, 15, 16, 17, 18, 19] |
Divest [6, 15, 16, 17, 18, 19] |
Divest [6, 15, 16, 17, 18, 19] |
Divest [6, 15, 16, 17, 18, 19] |
8.0 Patch 15 (Win) |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
8.0 Patch 5 (RHEL) |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
8.0 Patch 9 (RHEL) |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
8.0 Patch 10 (RHEL) |
Approved w/Constraints [6, 9, 12, 14] |
Approved w/Constraints [6, 9, 12, 14] |
Approved w/Constraints [6, 9, 12, 14] |
Approved w/Constraints [6, 9, 12, 14] |
Approved w/Constraints [6, 9, 12, 14] |
Approved w/Constraints [6, 9, 12, 14] |
Approved w/Constraints [6, 9, 12, 14] |
Approved w/Constraints [6, 9, 12, 14] |
Divest [6, 15, 16, 17, 18, 19] |
Divest [6, 15, 16, 17, 18, 19] |
Divest [6, 15, 16, 17, 18, 19] |
Divest [6, 15, 16, 17, 18, 19] |
8.0 Patch 11 (RHEL) |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
10.1.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [6, 15, 16, 17, 18, 19] |
Approved w/Constraints [6, 15, 16, 17, 18, 19] |
Approved w/Constraints [6, 15, 16, 17, 18, 19] |
Approved w/Constraints [6, 15, 16, 17, 18, 19] |
| | [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] | Only instances of this technology that have been deployed as of 10/1/2011 may continue to use this technology. This technology will receive a full assessment and decision. | | [3] | Product must remain patched and operated in accordance with Federal and Department security and privacy policies and guidelines. Configuration and deployment standards for this software are defined and maintained by the Client Services organization within VA Enterprise Systems Engineering, which must be followed and adhered to unless an appropriate waiver is granted. | | [4] | 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.
| | [5] | Configuration and deployment standards for this software are defined and maintained by the Client Services organization within VA Enterprise Systems Engineering must be followed and adhered to unless an appropriate waiver is granted. | | [6] | Use of this technology is limited to VA staff charged with ensuring the security of the VA network infrastructure. VA staff performing analysis with this technology need to work closely with system owners and agree on security scanning rules, such as the assets scanned, along the schedule and frequency of those scans. | | [7] | In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004 , VA Directive 6517, and VA Directive 6513. The local ISO can advise on the ESCCB review process. | | [8] | Configuration and deployment standards for this software are defined and maintained by the Client Services organization within VA Enterprise Systems Engineering must be followed and adhered to unless an appropriate waiver is granted.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period. | | [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] | In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004 , VA Directive 6517, and VA Directive 6513. The local ISO can advise on the ESCCB review process. | | [11] | Configuration and deployment standards for this software are defined and maintained by the Desktop and Device Engineering organization within VA Solution Delivery (SD) must be followed and adhered to unless an appropriate waiver is granted.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period. | | [12] | 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. | | [13] | Configuration and deployment standards for this software are defined and maintained by the Desktop and Device Engineering organization within VA Solution Delivery (SD) must be followed and adhered to unless an appropriate waiver is granted.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period. | | [14] | Configuration and deployment standards for this software are defined and maintained by the Desktop and Device Engineering organization within VA Solution Delivery (SD) must be followed and adhered to unless an appropriate waiver is granted.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period. | | [15] | Configuration and deployment standards for this software are defined and maintained by the Desktop and Device Engineering organization within VA Solution Delivery (SD) must be followed and adhered to unless an appropriate waiver is granted.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
This technology can potentially use Secure Sockets Layer (SSL), an unapproved protocol.
Users must not utilize Citrix XenApp, as it is at the time of writing, unapproved in the TRM.
Users must Divest the use of VMware ThinApp with this technology.
Users must not utilize Hyper-V Server, as it is at the time of writing, prohibited in the TRM.
Users must utilize approved internet browsers, as Microsoft Internet Explorer has reached End of Life status. See Category Tab for details.
Users must ensure that Microsoft Structured Query Language (MS SQL), VMware vSphere and Apache Hypertext Transfer Protocol (HTTP) servers are implemented with VA-approved baselines. (Refer to the ‘Category’ tab under ‘Runtime Dependencies’). | | [16] | Users should check with their supervisor, Information System Security Officer (ISSO) 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. | | [17] | 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 ISSO (Information System Security Officer) can provide assistance in reviewing the NIST vulnerabilities. | | [18] | 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 System Security Officer (ISSO) 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). | | [19] | This technology has received one or more VA security bulletins that provide specific guidance on vulnerability patching and mitigation. It is the responsibility of VA system owners to ensure that the appropriate mitigations are taken to address all known and future discovered vulnerabilities with this product. See the Reference tab for more information on security bulletins related to this product. |
|
Note: |
At the time of writing, version 10.1.10 is the most current version, released 10/26/2022.
The versioning schema of this technology changed with the release of version 10. |