<Past |
Future> |
2.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Wbs31 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Wbs32 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Wbs33 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Wbs39.x |
Divest [3, 4, 9, 12, 13] |
Divest [3, 4, 9, 12, 13] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Wbs40.x |
Divest [3, 4, 9, 12, 13] |
Divest [3, 4, 9, 12, 13] |
Divest [3, 4, 9, 13, 14] |
Divest [3, 4, 9, 13, 14] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Wbs41.x |
Approved w/Constraints [3, 4, 9, 12, 13] |
Approved w/Constraints [3, 4, 9, 12, 13] |
Approved w/Constraints [3, 4, 9, 13, 14] |
Approved w/Constraints [3, 4, 9, 13, 14] |
Approved w/Constraints [3, 4, 9, 13, 14] |
Approved w/Constraints [3, 4, 9, 13, 15] |
Approved w/Constraints [3, 4, 9, 13, 15] |
Approved w/Constraints [3, 4, 9, 13, 15] |
Divest [9, 15, 16, 17, 18, 19] |
Divest [9, 15, 16, 17, 18, 19] |
Divest [9, 15, 16, 17, 18, 19] |
Divest [9, 15, 16, 17, 19, 20] |
Wbs42.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Divest [9, 15, 16, 17, 18, 19] |
Divest [9, 15, 16, 17, 18, 19] |
Divest [9, 15, 16, 17, 18, 19] |
Divest [9, 15, 16, 17, 19, 20] |
Wbs43.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [9, 15, 16, 17, 18, 19] |
Approved w/Constraints [9, 15, 16, 17, 18, 19] |
Approved w/Constraints [9, 15, 16, 17, 18, 19] |
Approved w/Constraints [9, 15, 16, 17, 19, 20] |
| | [1] | Due to several NIST security vulnerabilities, product must remain properly patched in order to mitigate known and future vulnerabilities. Freeware may only be downloaded directly from the offering vendor`s site, not from public freeware repositories, to avoid possible addition of adware or malware. Downloaded software should always be scanned for viruses prior to installation. | | [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] | 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. | | [4] | 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. | | [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] | This technology must only be used to replay WebEx conferences recorded and made available by non-organization users (e.g. vendor partners).
Veterans Affairs (VA) users must not schedule WebEx conferences, but instead should leverage the organization`s teleconferencing solution of choice, Microsoft Lync for VA hosted conferences. Teleconferencing should not be used to share desktop(s), transfer user control, or view/modify data with users outside the firewall who have not obtained proper Department user credentials in compliance with Federal and Department security and privacy requirements. | | [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] | This technology must only be used to replay WebEx conferences recorded and made available by non-organization users (e.g. vendor partners).
Veterans Affairs (VA) users must not schedule WebEx conferences, but instead should leverage the organization`s teleconferencing solution of choice, Microsoft Lync for VA hosted conferences. Teleconferencing should not be used to share desktop(s), transfer user control, or view/modify data with users outside the firewall who have not obtained proper Department user credentials in compliance with Federal and Department security and privacy requirements. | | [9] | Use of this technology on the VA network is limited to JOINING external web-based training sessions scheduled by non-organization users (e.g. vendor partners) until a full deployment of this technology is acquired.
Once the Software-as-a-Service (SaaS) implementation is in place, the SaaS must be used through a provided link directing the user to the FedRAMP platform, and it may be used to host meetings.
No other platform outside of the approved VA FedRAMP solution is authorized for hosting conferences. | | [10] | 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). | | [11] | 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). | | [12] | 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). | | [13] | 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. | | [14] | 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 (PSF) team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | [15] | 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 VA OIT Product Engineering team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | [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] | 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. | | [18] | 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 ISSO (Information System Security Officer) to ensure compliance with VA Handbook 6500. | | [19] | 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. | | [20] | 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 ISSO (Information System Security Officer) to ensure compliance with both VA Handbook 6500 and VA Directive 6500. |
|
Note: |
At the time of writing, version 43.2.0.25211 is the most current version, released 02/13/2023. |