<Past |
Future> |
29.x |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
30.x |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
31.x |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
32.x |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
33.x |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
39.x |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
40.x |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
41.x |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
42.x |
Approved w/Constraints [17, 24, 26, 27, 28, 29, 30, 32, 33] |
DIVEST [17, 24, 27, 28, 29, 30, 32, 33, 34, 35] |
DIVEST [17, 24, 27, 28, 29, 30, 32, 33, 34, 35] |
Authorized w/ Constraints (DIVEST) [17, 24, 27, 28, 29, 30, 32, 33, 35, 36] |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
43.x |
Unapproved |
DIVEST [17, 24, 27, 28, 29, 30, 32, 33, 34, 35] |
DIVEST [17, 24, 27, 28, 29, 30, 32, 33, 34, 35] |
Authorized w/ Constraints (DIVEST) [17, 24, 27, 28, 29, 30, 32, 33, 35, 36] |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
44.x |
Unapproved |
Approved w/Constraints [17, 24, 27, 28, 29, 30, 32, 33, 34, 35] |
Approved w/Constraints [17, 24, 27, 28, 29, 30, 32, 33, 34, 35] |
Authorized w/ Constraints [17, 24, 27, 28, 29, 30, 32, 33, 35, 36] |
Authorized w/ Constraints (DIVEST) [17, 24, 27, 28, 29, 30, 32, 33, 35, 36] |
Authorized w/ Constraints (DIVEST) [17, 24, 27, 28, 29, 30, 32, 33, 35, 37] |
Authorized w/ Constraints (DIVEST) [17, 24, 27, 28, 29, 30, 32, 33, 35, 37] |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
45.x |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints [17, 24, 27, 28, 29, 30, 32, 33, 35, 36] |
Authorized w/ Constraints [17, 24, 27, 28, 29, 30, 32, 33, 35, 37] |
Authorized w/ Constraints [17, 24, 27, 28, 29, 30, 32, 33, 35, 37] |
Authorized w/ Constraints [17, 24, 27, 28, 29, 30, 32, 33, 35, 37] |
Authorized w/ Constraints [17, 24, 27, 28, 29, 30, 32, 33, 35, 37] |
Authorized w/ Constraints [17, 24, 27, 28, 29, 30, 32, 33, 35, 37] |
Authorized w/ Constraints [17, 24, 27, 28, 29, 30, 32, 33, 35, 37] |
Authorized w/ Constraints [17, 24, 27, 28, 29, 30, 32, 33, 35, 37] |
Note: |
At the time of writing, version 45.6.0.32551 (Windows & macOS) is the most current version, released 06/06/2025. A standard configuration of this technology is being developed by the DDE team. At the time of writing, the standard version is 45.2.0.31800. |
| | [17] | 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. | | [24] | 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. | | [26] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must ensure that Firefox and Google Chrome are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Per the Initial Product Review, users must abide by the following constraints:
- Only the VA authorized 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 authorized VA FedRAMP solution is authorized for hosting VA 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”.
- Webex Meetings must be configured to only store information on the VA FedRAMP Webex Meetings instance.
- Only the FedRAMP authorized VA authorized 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.
- Per VA Handbook 6500 Appendix D, Department of Veteran Affairs National Rules of Behavior, Section f (3) (page 68. D-10). It 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. The National Institute of Standards and Technology (NIST) National Vulnerability Database should be referenced for vulnerabilities, and the product should be continuously monitored for security vulnerabilities.
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. | | [27] | 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 authorized and the user should take the proper steps to decline those installations. | | [28] | 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. | | [29] | 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. | | [30] | This technology should only be used when required by a Veterans Affairs (VA) business partner for an authorized VA Project. Use of this technology must comply with ESCCB requirements which include: Signed Interconnection Agreements/Memorandum of Understanding agreements (MOU/ISA) with each external business partner, compliance with VA Handbook 6500, and must implement appropriate National Institute of Standards and Technology (NIST) Federal Information Processing Standards (FIPS) requirements for all devices interacting with this technology. 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 and National Institute of Standards and Technology (NIST) standards. As of January 27th, 2017, Risk-based Decisions (RBD) will be handled per VAIQ # 7769667. 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 can advise on the ESCCB review process and ensure privacy of information compliance protections are in place. | | [32] | 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. | | [33] | 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). | | [34] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must ensure that Microsoft Edge, Firefox, and Google Chrome are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Per the Initial Product Review, users must abide by the following constraints:
- This product is listed on the Digital VA Product Marketplace. Please review the entry to ensure all security guidance is followed, and to submit a request for approval to use
- The referenced cryptographic module should not be included by Federal Agencies in new procurements. Agencies may make a risk determination on
whether to continue using this module based on their own assessment of where and how it is used.
- Only the Digital VA Marketplace or FedRAMP authorized VA authorized 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. The National Institute of Standards and Technology (NIST) National Vulnerability Database should be referenced for vulnerabilities, and the product should be continuously monitored for security vulnerabilities.
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. | | [35] | The Federal Information Processing standards (FIPS) 140-2 certification status of this technology was not able to be verified. This technology will require a 3rd party FIPS 140-2 or 140-3 certified solution for any data containing PHI/PII or VA sensitive information, where applicable. More information regarding the Cryptographic Module Validation Program (CMVP) can be found on the NIST website. | | [36] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must ensure that Microsoft Edge, Firefox, and Google Chrome are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Per the Initial Product Review, users must abide by the following constraints:
- This product is listed on the Digital VA Product Marketplace. Please review the entry to ensure all security guidance is followed, and to submit a request for approval to use
- The referenced cryptographic module should not be included by Federal Agencies in new procurements. Agencies may make a risk determination on whether to continue using this module based on their own assessment of where and how it is used.
- Only the Digital VA Marketplace or FedRAMP authorized VA authorized 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. The National Institute of Standards and Technology (NIST) National Vulnerability Database should be referenced for vulnerabilities, and the product should be continuously monitored for security vulnerabilities.
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. | | [37] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must ensure that Microsoft Edge, Firefox, and Google Chrome are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Per the Initial Product Review, users must abide by the following constraints:
- Webex Meetings is a SaaS web conferencing solution. This product is listed on the Digital VA Product Marketplace. Please review the entry to ensure all security guidance is followed, and to submit a request for approval to use
- The FIPS Certificate for this product #2984 is in a Historical status. The referenced cryptographic module should not be included by Federal Agencies in new procurements. Agencies may make a risk determination on whether to continue using this module based on their own assessment of where and how it is used.
- Webex Meetings can be accessed through an external link and/or the Webex Meetings Desktop Application can be downloaded upon a meeting acceptance. Only the Digital VA Marketplace or FedRAMP authorized VA authorized 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.
- Webex Meetings offers a free version with limited functionality. 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.
- There are multiple published vulnerabilities that affect many versions of this software. Ensure that the latest version is installed. The National Institute of Standards and Technology (NIST) National Vulnerability Database should be referenced for vulnerabilities, and the product should be continuously monitored for security vulnerabilities.
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. |
|