<Past |
Future> |
9.x |
Approved w/Constraints [2, 4] |
Approved w/Constraints [2, 4, 5] |
Approved w/Constraints [2, 4, 5] |
Approved w/Constraints [2, 4, 5] |
Approved w/Constraints [2, 4, 5] |
Divest [2, 4, 5] |
Divest [2, 4, 5] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
10.0x |
Approved w/Constraints [2, 4] |
Divest [2, 4, 5] |
Divest [2, 4, 5] |
Divest [2, 4, 5] |
Divest [2, 4, 5] |
Divest [2, 4, 5] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
10.5x |
Approved w/Constraints [2, 4] |
Divest [2, 4, 5] |
Divest [2, 4, 5] |
Divest [2, 4, 5] |
Divest [2, 4, 5] |
Divest [2, 4, 5] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
11.0x |
Approved w/Constraints [1, 2, 4] |
Approved w/Constraints [2, 4, 5] |
Divest [2, 4, 5] |
Divest [2, 4, 5] |
Divest [2, 4, 5] |
Divest [2, 4, 5] |
Divest [2, 4, 5] |
Divest [2, 4, 5] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
11.5x |
Approved w/Constraints [1, 2, 4] |
Approved w/Constraints [2, 4, 5] |
Approved w/Constraints [2, 4, 5] |
Approved w/Constraints [2, 4, 5] |
Divest [2, 4, 5] |
Divest [2, 4, 5] |
Divest [2, 4, 5] |
Divest [2, 4, 5] |
Divest [2, 4, 6] |
Divest [2, 4, 6] |
Unapproved |
Unapproved |
11.6x |
Unapproved |
Approved w/Constraints [2, 4, 5] |
Approved w/Constraints [2, 4, 5] |
Approved w/Constraints [2, 4, 5] |
Approved w/Constraints [2, 4, 5] |
Approved w/Constraints [2, 4, 5] |
Approved w/Constraints [2, 4, 5] |
Approved w/Constraints [2, 4, 5] |
Approved w/Constraints [2, 4, 6] |
Approved w/Constraints [2, 4, 6] |
Approved w/Constraints [2, 4, 6] |
Approved w/Constraints [2, 4, 6] |
12.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [2, 4, 6] |
Approved w/Constraints [2, 4, 6] |
Approved w/Constraints [2, 4, 6] |
Approved w/Constraints [2, 4, 6] |
| | [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] | 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. | | [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] | 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. | | [5] | 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). | | [6] | 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). |
|
Note: |
At the time of writing, version 12.6(1) is the most current version, released 05/10/2021. |