<Past |
Future> |
11.1.x |
Divest [1, 3] |
Divest [1, 3, 4] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
11.5.x |
Divest [1, 3] |
Divest [1, 3, 4] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
11.6.x |
Approved w/Constraints [1, 3] |
Divest [1, 3, 4] |
Divest [1, 3, 4] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
11.7.x |
Approved w/Constraints [1, 3] |
Divest [1, 3, 4] |
Divest [1, 3, 4] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
11.8.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
11.9.x |
Approved w/Constraints [1, 3] |
Divest [1, 3, 4] |
Divest [1, 3, 4] |
Divest [1, 3, 4] |
Divest [1, 3, 4] |
Divest [1, 3, 4] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
12.0.x |
Unapproved |
Approved w/Constraints [1, 3, 4] |
Approved w/Constraints [1, 3, 4] |
Approved w/Constraints [1, 3, 4] |
Approved w/Constraints [1, 3, 4] |
Divest [1, 3, 4] |
Divest [1, 3, 4] |
Divest [1, 3, 4] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
12.6.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [1, 3, 4] |
Approved w/Constraints [1, 3, 4] |
Approved w/Constraints [1, 3, 4] |
Approved w/Constraints [1, 3, 5, 6] |
Approved w/Constraints [1, 3, 5, 6] |
Approved w/Constraints [1, 3, 5, 6] |
Approved w/Constraints [1, 3, 5, 6] |
12.6.4+ |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
12.7.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [1, 3, 5, 6] |
Approved w/Constraints [1, 3, 5, 6] |
Approved w/Constraints [1, 3, 5, 6] |
Approved w/Constraints [1, 3, 5, 6] |
12.7.3+ |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
12.8.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [1, 3, 5, 6] |
Approved w/Constraints [1, 3, 5, 6] |
Approved w/Constraints [1, 3, 5, 6] |
Approved w/Constraints [1, 3, 5, 6] |
12.8.4+ |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
12.9.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [1, 3, 5, 6] |
Approved w/Constraints [1, 3, 5, 6] |
12.9.3+ |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
14.0.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
14.2.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
14.3.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| | [1] | 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. | | [2] | 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. | | [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] | 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). | | [5] | Per the Initial Product Review, users must abide by the following constraints:
- Cisco Jabber for Windows has been identified as vulnerable to Local Information Disclosure Vulnerabilities, CVE-2017-12284 and CSCve14401. This has been resolved for the latest version. System owners must ensure that version 11.8(4.52954) or higher of the product is used.
- Due to potential information security risks, SaaS/PaaS solutions must complete the Veterans-Focused Integration Process Request (VIPR) process where a collaborative effort between Demand Management (DM), Enterprise Program Management Office Information Assurance (EPMO IA), Project Special Forces (PSF), Enterprise Cloud Solutions Office (ECSO), Chief Technology Officer (CTO), and stakeholders determines the SaaS/PaaS category during the Discovery Phase. All SaaS and Non-AWS/Azure (VAEC) PaaS assets are routed to EPMO IA for Analysis and Approval to Operate (ATO) with technical oversight, acquisition, production, and sustainment provided by PSF.
| | [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 14.3.1 is the most current version, released 03/24/2024.
A standard configuration of this technology was developed by the DDE team. At the time of writing, the standard version is 14.0.1.55914 and version 14.3.1.58554 is under testing and development for six weeks from 07/05/2024. |