| | | | [1] | If free trial ware 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] | Due to potential information security risks, cloud based technologies may not be used without the approval of the VA Enterprise Cloud Services (ECS) Group. 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). | | | [4] | 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. | | | [5] | 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. | | | [6] | 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). | | | [7] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Teleconferencing must 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.
Users must not share any Protected Health Information, Personally Identifiable Information or VA sensitive information under any circumstances when using this technology.
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 zoom.us 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. | | | [8] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users should leverage enterprise solutions already in place such as Microsoft Teams as the organization`s preferred conferencing technology until an ATO is signed to approve Zoom services such as Zoom Federal or Zoom Healthcare.
Per CIO directive, for the duration of the national emergency, the Zoom client can be used with Zoom Healthcare services by VHA clinicians. See the entry justification for more information.
Per the Initial Product Review, users must abide by the following constraints:
-
Version 4 of Zoom Client for Meetings must not be used within the VA. Only version 5.0 or later of Zoom Client for Meetings must be used; however, the Client should not be used until Zoom has migrated to using AES 256 Galois/Counter Mode (GCM) encryption. Until the migration is complete, users should continue to conduct Zoom meetings via the web portal.
-
System administrators must ensure that the latest version of Zoom Client for Meetings is used. Additionally, Zoom Client for Meetings must be added to the list of applications for continuous monitoring for published vulnerabilities, updates, and patches.
-
Due to potential information security risks, SaaS 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.
-
Zoom should only be considered if a VA approved solution does not meet the necessary requirement, and the use for more specialized tools are warranted.
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’) | | | [9] | 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. | | | [10] | 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). | | | [11] | 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. | | | [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] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users should leverage enterprise solutions already in place such as Microsoft Teams as the organization`s preferred conferencing technology until an ATO is signed to approve Zoom services such as Zoom Federal or Zoom Healthcare.
Per CIO directive, for the duration of the national emergency, the Zoom client can be used with Zoom Healthcare services by VHA clinicians. See the entry justification for more information.
Per the Initial Product Review, users must abide by the following constraints:
-
Version 4 of Zoom Client for Meetings must not be used within the VA. Only version 5.0 or later of Zoom Client for Meetings must be used; however, the Client should not be used until Zoom has migrated to using AES 256 Galois/Counter Mode (GCM) encryption. Until the migration is complete, users should continue to conduct Zoom meetings via the web portal.
-
System administrators must ensure that the latest version of Zoom Client for Meetings is used. Additionally, Zoom Client for Meetings must be added to the list of applications for continuous monitoring for published vulnerabilities, updates, and patches.
-
Due to potential information security risks, SaaS 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.
-
Zoom should only be considered if a VA approved solution does not meet the necessary requirement, and the use for more specialized tools are warranted.
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’) | | | [14] | 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. | | | [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 (PSF) team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | | [16] | Users must Divest the use of Internet Explorer with this technology. Other approved internet browsers are available. See Category Tab for details.
Users should leverage enterprise solutions already in place such as Microsoft Teams as the organization`s preferred conferencing technology until an ATO is signed to approve Zoom services such as Zoom Federal or Zoom Healthcare.
Per CIO directive, for the duration of the national emergency, the Zoom client can be used with Zoom Healthcare services by VHA clinicians. See the entry justification for more information.
Per the Initial Product Review, users must abide by the following constraints:
-
Version 4 of Zoom Client for Meetings must not be used within the VA. Only version 5.0 or later of Zoom Client for Meetings must be used; however, the Client should not be used until Zoom has migrated to using AES 256 Galois/Counter Mode (GCM) encryption. Until the migration is complete, users should continue to conduct Zoom meetings via the web portal.
-
System administrators must ensure that the latest version of Zoom Client for Meetings is used. Additionally, Zoom Client for Meetings must be added to the list of applications for continuous monitoring for published vulnerabilities, updates, and patches.
-
Due to potential information security risks, SaaS 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.
-
Zoom should only be considered if a VA approved solution does not meet the necessary requirement, and the use for more specialized tools are warranted.
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’) | | | [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] | Users should leverage enterprise solutions already in place such as Microsoft Teams as the organization`s preferred conferencing technology until an ATO is signed to approve Zoom services such as Zoom Federal or Zoom Healthcare.
Per CIO directive, for the duration of the national emergency, the Zoom client can be used with Zoom Healthcare services by VHA clinicians. See the entry justification for more information.
Per the Security Assessment Review, users must abide by the following constraints:
-
Ensure the following mitigations are turned `ON` for all executables used by Zoom for Government version 5.x. Create an XML file with the contents listed below. Add multiple XML element sections for each executable used by the application. Change `Executable` to the name for each application executable.
After creation of the XML file, the administrator run `Windows PowerShell` with elevated privileges (run as administrator) and enter the following:Set-ProcessMitigation -PolicyFilePath The command will enable the following protections:DEP:Enable: ONASLR:BottomUp: ONForceRelocateImages: ONPayload:EnableExportAddressFilter: ONEnableExportAddressFilterPlus: ONEnableImportAddressFilter: ONEnableRopStackPivot: ON EnableRopCallerCheck: ONEnableRopSimExec: ON Exploit Protection mitigations in Windows must be configured for the following executables installed with Zoom for Government version 5.x:c:\ users\itlscanman\appdata\roaming\zoom\bin\airhost.exe c:\ users\itlscanman\appdata\roaming\zoom\bin\aomhost64.exe c:\ users\itlscanman\appdata\roaming\zoom\bin\cptcontrol.exec:\ users\itlscanman\appdata\roaming\zoom\bin\cpthost.exe c:\ users\itlscanman\appdata\roaming\zoom\bin\cptinstall.exe c:\ users\itlscanman\appdata\roaming\zoom\bin\cptservice.exe c:\ users\itlscanman\appdata\roaming\zoom\bin\installer.exec:\ users\itlscanman\appdata\roaming\zoom\bin\zcrashreport.exe c:\ users\itlscanman\appdata\roaming\zoom\bin\zcrashreport64.exe c:\ users\itlscanman\appdata\roaming\zoom\bin\zoom.exe c:\ users\itlscanman\appdata\roaming\zoom\bin\zoomdocconverter.exe c:\ users\itlscanman\appdata\roaming\zoom\bin\zoomoutlookimplugin.exe
September 27, 2022For Internal VA Use OnlyPage 9 of 25 c:\users\itlscanman\appdata\roaming\zoom\bin\zoomoutlookmapi.exe c:\ users\itlscanman\appdata\roaming\zoom\bin\zoomoutlookmapi64.exe c:\ users\itlscanman\appdata\roaming\zoom\bin\zoom_launcher.exec:\ users\itlscanman\appdata\roaming\zoom\bin\ztscoder.exe c:\ users\itlscanman\appdata\roaming\zoom\bin\zupdater.exe c:\ users\itlscanman\appdata\roaming\zoom\bin\zwebview2agent.exe c:\ users\itlscanman\appdata\roaming\zoom\uninstall\installer.exe
To verify the executables listed above are protected, run `WindowsPowerShell` with elevated privileges (run as administrator). Enter `Get-ProcessMitigation`. The settings listed above should be set to `ON` for each application executable.If application issues arise with mitigation settings applied, at a minimum, DEP and ASLR settings should be set to ON. Payload options can be set to OFF or `false` in the xml policy file.
-
Support and Feedback Data should be reviewed for sensitive information before submitting to vendor. To not include log file and system information, uncheck “include log file and system information” before submitting a report problem.
-
The administrator shall control the versioning of Zoom for Government version 5.x software and do not allow users to install unapproved versions.
-
The administrators shall disable all unauthorized firewall rules.
| | | [19] | Browser plug-ins and extensions may only be installed by VA IT Operations (ITOPS) and must be used with official VA browser installation packages that are managed by ITOPS. For installation, contact the National Service Desk [Mail Group: National Service Desk - Austin]. Browser extensions must be kept up to date with security patches and enhancements. | | | [20] | This product includes a Bluetooth capability. If that capability is leveraged, the implementer must conform to the Bluetooth Standard. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | | [21] | 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. | | | [22] | 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. | | | [23] | 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. | | | [24] | This product includes a Bluetooth capability. If that capability is leveraged, the implementer must conform to the Bluetooth Standard. 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. | | | [25] | 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. | | | [26] | 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). | | | [27] | 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. |
|
