<Past |
Future> |
29.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
30.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
31.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
32.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
33.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
39.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
40.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
41.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
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] |
Divest [17, 24, 27, 28, 29, 30, 32, 33, 34, 35] |
Divest [17, 24, 27, 28, 29, 30, 32, 33, 34, 35] |
Divest [17, 24, 27, 28, 29, 30, 32, 33, 34, 35] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
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] |
Divest [17, 24, 27, 28, 29, 30, 32, 33, 34, 35] |
Divest [17, 24, 27, 28, 29, 30, 32, 33, 34, 35] |
Divest [17, 24, 27, 28, 29, 30, 32, 33, 34, 35] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
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] |
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] |
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] |
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] |
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] |
Approved w/Constraints [17, 24, 27, 28, 29, 30, 32, 33, 34, 35] |
| | [1] | Product may only be used to JOIN web based conferences scheduled by non-organization users (e.g. vendor partners). Once the WebEx meeting has concluded, users should uninstall the WebEx Meeting Manager software installed on the client system to ensure that only the latest version of the downloaded software is used for each external WebEx meeting. VA users MAY 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 whom have not obtained proper Department user credentials in compliance with Federal and Department security and privacy requirements. | | [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] | 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 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] | Due to potential information security risks, cloud based versions of this product are not permitted without a waiver signed by the Deputy CIO of ASD based upon a recommendation from the Architecture and Engineering Review Board (AERB). In addition, cloud based features of this software may not be used without an Enterprise Security Change Control Board (ESCCB) approval to ensure that confidential organization and/or PII/PHI data are not compromised (ref: VA Directive 6004, VA Directive 6517 and VA Directive 6513). Use of public cloud storage requires documented Federal Risk and Authorization Management Program (FedRAMP) compliance and a Memorandum of Understanding / Interconnection Security Agreement (MOU/ISA) between the vendor and VA prior to ESCCB review. | | [6] | 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. | | [7] | 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. | | [8] | 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). | | [9] | This product may only be used to JOIN web based conferences scheduled by non-organization users (e.g. vendor partners). Once the WebEx meeting has concluded, users should uninstall the WebEx Meeting Manager software installed on the client system to ensure that only the latest version of the downloaded software is used for each external WebEx meeting. VA users MAY 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 whom have not obtained proper Department user credentials in compliance with Federal and Department security and privacy requirements. | | [10] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must ensure that they are using a current version of the Oracle Java Runtime Environment.
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 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. | | [11] | This technology must not be downloaded from the Windows App Store.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must run this technology on a TRM-approved version of the Oracle Java Development Kit.
Users must use the baselined version of Microsoft Internet Explorer and FireFox. Please visit these entries, linked on the category tab, for more information.
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. | | [12] | 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. | | [13] | 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. | | [14] | This technology must not be downloaded from the Windows App Store.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must run this technology on a TRM-approved version of the Oracle Java Development Kit.
Users must use the baselined version of Microsoft Internet Explorer and FireFox. Please visit these entries, linked on the category tab, for more information.
Use of WebEx endpoint software on the VA network that is NOT connecting to the VA SaaS Enterprise WebEx cloud service is limited to JOINING external web-based training sessions scheduled by non-organization users (e.g. vendor partners).
The VA Enterprise Software-as-a-Service (SaaS) implementation must be used through a provided link directing the user to the FedRAMP platform. This VA sponsored service MAY be used to host VA meetings.
No other WebEx platform outside of the approved VA FedRAMP solution is authorized for hosting VA conferences. | | [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] | This technology must not be downloaded from the Windows App Store.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must run this technology on a TRM-approved version of the Oracle Java Development Kit.
Users must ensure that Firefox and Microsoft Internet Explorer (IE) are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
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.
- 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 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.
- 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. | | [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. | | [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 ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | [19] | 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. | | [20] | 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). | | [21] | 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). | | [22] | This technology should only be used when required by a Veterans Affairs (VA) business partner for an approved 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 ISO (Information 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 ISO can advise on the ESCCB review process and ensure privacy of information compliance protections are in place. | | [23] | This technology must not be downloaded from the Windows App Store.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must run this technology on a TRM-approved version of the Oracle Java Development Kit.
Users must Divest the use of Internet Explorer with this technology. Other approved internet browsers are available. See Category Tab for details.
Users must ensure that Firefox, Google Chrome, and Microsoft Internet Explorer (IE) are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
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.
- 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 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.
- 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. | | [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. | | [25] | 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). | | [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-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
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.
- 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 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.
- 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 approved 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 approved 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. | | [31] | 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. | | [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-approved 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 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. 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. |
|
Note: |
At the time of writing, version 44.3.0.28993 (Windows & macOS) is the most current version, released 03/12/2024. A standard configuration of this technology is being developed by the DDE team. At the time of writing, version 44.2.0.29005 is under testing and development for six weeks from 03/21/2024. |