<Past |
Future> |
3.0.x |
Divest [10, 17, 18, 19, 20, 21, 22] |
Divest [10, 17, 18, 19, 20, 21, 22] |
Divest [10, 17, 18, 19, 20, 21, 22] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
40.x |
Divest [10, 17, 18, 19, 20, 21, 22] |
Divest [10, 17, 18, 19, 20, 21, 22] |
Divest [10, 17, 18, 19, 20, 21, 22] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
41.x |
Divest [10, 17, 18, 19, 20, 21, 22] |
Divest [10, 17, 18, 19, 20, 21, 22] |
Divest [10, 17, 18, 19, 20, 21, 22] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
42.x |
Divest [10, 17, 18, 19, 20, 21, 22] |
Divest [10, 17, 18, 19, 20, 21, 22] |
Divest [10, 17, 18, 19, 20, 21, 22] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
43.x |
Divest [10, 17, 18, 19, 20, 21, 22] |
Divest [10, 17, 18, 19, 20, 21, 22] |
Divest [10, 17, 18, 19, 20, 21, 22] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| | [1] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period. | | [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] | 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] | 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. | | [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] | This technology must only be used to integrate with TRM-approved technologies and must not be used in conjunction with unapproved solutions such as Slack.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Use of this technology is limited to JOINING external web-based training sessions scheduled by non-organization users (e.g. vendor partners). VA users must leverage the organization`s preferred teleconferencing solution, Skype for Business (Formerly Microsoft Lync), for internal hosted conferences. VA has selected Skype for Business as its preferred teleconferencing solution. No waiver or review is required for JOINING WebEx Teams meetings.
Any use of this technology to host a VA event must be authorized by a Strategic Technology Alignment Team (STAT) waiver. There are no exceptions to the required waiver process for any reason. The STAT Board must seek guidance and/or approval from the Enterprise Security Change Control Board (ESCCB) as needed when a waiver is granted to host conferences. | | [7] | 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. | | [8] | This technology must only be used to integrate with TRM-approved technologies..
If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Cloud deployment for this software must not be utilized as it is not FedRamp compliant.
Users must implement this technology with the approved baseline version of FireFox and Microsoft Internet Explorer.
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.
| | [9] | New installations or major expansions of this technology that transmit data over the VA Wide Area Network (WAN) must complete a WAN impact review (contact VA e-mail: [OIT ITOPS SD Engagement Requests]) prior to implementation to ensure proper compliance to VA network design and usage requirements. | | [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. | | [11] | This technology must only be used to integrate with TRM-approved technologies.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Cloud deployment for this software must not be utilized as it is not FedRamp compliant.
Users must implement this technology with the approved baseline version of Google Chrome, FireFox, and Microsoft Internet Explorer.
Only the VA approved FedRamp hosted instance of Webex Teams can be used within the VA and any non-VA version of Webex Teams should not be used to host VA meetings. No other WebEx platform outside of the approved VA FedRAMP solution is authorized for hosting VA conferences.
Use of WebEx endpoint software on the VA network that is NOT connecting to the VA FedRAMP Enterprise WebEx cloud service is limited to JOINING external web-based training sessions scheduled by non-organization users (e.g. vendor partners). Users in this scenario should not screen share or share any sensitive data on these 3rd party hosted conferences. | | [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] | 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. | | [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 Project Special Forces (SPF) team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | [16] | 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). | | [17] | 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). | | [18] | This technology must only be used to integrate with TRM-approved technologies.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Per the Initial Product Review, users must abide by the following constraints:
- Only the VA approved FedRamp hosted instance of Webex Meetings can be used within the VA and any non-VA version of Webex Meetings should not be used to host VA meetings. No other WebEx platform outside of the approved VA FedRAMP solution is authorized for hosting VA conferences.
- Use of WebEx endpoint software on the VA network that is NOT connecting to the VA FedRAMP Enterprise WebEx cloud service is limited to JOINING external web-based training sessions scheduled by non-organization users (e.g. vendor partners). Users in this scenario should not screen share or share any sensitive data on these 3rd party hosted conferences
- Per Cisco “The customer must ask Cisco Webex technical support to set FIPS
Mode on the customer’s Webex site and the host`s Windows platform must be
set to use FIPS mode”.
- Only the FedRAMP authorized VA approved Gov Cloud instance of the Webex
Meetings solution can be used to host conferences. Internal Webex Meetings must be conducted through a provided link directing the user to the VA Webex
website.
- VA Handbook 6500 Appendix D, Department of Veteran Affairs National Rules
of Behavior, Section f (3) (page 68. D-10) states the following:
`I will not download software from the Internet, or other public available
sources, offered as free trials, shareware, or other unlicensed software
to a VA-owned system`.
- Ensure that the latest version is installed.
| | [19] | 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. | | [20] | 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. | | [21] | 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. | | [22] | 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 ISSO (Information System Security Officer) can advise on the ESCCB review process. | | [23] | 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. | | [24] | 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, visit the Product Marketplace.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). |
|
Note: |
At the time of writing, version 43.3.0.25468 is the most current version, released 03/07/2023.
The versioning schema of this technology changed after WebEx Teams was integrated into WebEx. |