| | | | [1] | Under the advisement and direction of the Enterprise Systems Engineering (ESE) Enterprise Video Teleconferencing Network (EVTN) team, this technology may only be used in support of the VHA OIA Innovation Project # 669. Upon completion of this pilot program, a final decision on the applicability and deployment of this program will be considered. No further expansion or use of this technology is permitted unless a waiver has been granted to the project team that wishes to use the technology. | | | [2] | As of April 23, 2015, per the Deputy CIO of Architecture, Strategy and Design (ASD), all technologies in use by the VA require an assessment by the VA Section 508 office. Section 508 of the Rehabilitation Act Amendments of 1998 is a federal law that sets the guidelines for technology accessibility. A VA Section 508 assessment of this technology has not been completed at the time of publication. Therefore, as of April 23, 2015 only users of this technology who have deployed the technology to the production environment, or have project design and implementation plans authorized, may continue to operate this technology. In the case of a project that has implemented, or been authorized for a specific site or number of users, and that project needs to expand operations to other sites or to an increased user base, it may do so as long as the project stays on the existing version of the technology that was authorized or implemented as of April 22, 2015. Use of this technology in all other cases is prohibited.
| | | [3] | Under the advisement and direction of the Enterprise Systems Engineering (ESE) Enterprise Video Teleconferencing Network (EVTN) team this technology may only be used in support of the VHA OIA Innovation Project #669. Upon completion of this pilot program a final decision on the applicability and deployment of this program will be considered. No further expansion or use of this technology is permitted unless a waiver has been granted to the project team that wishes to use the technology. | | | [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] | Under the advisement and direction of the Enterprise Systems Engineering (ESE) Enterprise Video Teleconferencing Network (EVTN) team this technology may only be used in support of the VHA OIA Innovation Project #669. Upon completion of this pilot program a final decision on the applicability and deployment of this program will be considered. No further expansion or use of this technology is permitted unless a waiver has been granted to the project team that wishes to use the technology.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
The Initial Product Review notes the security constraints listed below:
It is imperative to utilize a FIPS 140-2 validated cryptographic module to secure VA sensitive data in transit and when it is stored on endpoint devices. In addition, it is mandated to conduct a Privacy Impact Assessment (PIA) on information technology systems that collect, maintain, or disseminate personally identifiable information (PII) as stated in VA Handbook 6500, VA Directive 6508 - Privacy Impact Assessments, and VA Handbook 6508.1 - Privacy Impact Assessment (PIA).
Applications or systems should only process VA sensitive data after they have undergone and completed the VA`s formal Assessment Authorization (A&A) process. Coordination with various VA teams (i.e., Network Operations, Telehealth Services) is crucial to ensure that deliveries of VA core services are not impacted.
The following should be considered to secure the Vidyo infrastructure:
- Employ a mechanism for identity verification to ensure participants of the videoconference connection are who they say they are
- Enforce password that meets VA minimum requirements
- Ensure encryption keys are secured properly and only authorized staff have access to them
- Ensure recorded video conferences and conversation histories are securely saved on VA authorized and authorized systems
- Servers must adhere to hardening standards located at the VA Baseline Configuration Management website
- The system should keep access and usage logs for auditing purposes
- Employ continuous vulnerability monitoring for all components associated with Vidyo
It is advised that a security policy addressing the use of this product on wireless connections and/or mobile devices be created prior to usage. The implementing organization could craft something based upon the Rules of Behavior as outlined in VA Handbook 6500 Appendix D. A logon banner as directed in VA Handbook 6500 Appendix F `AC-8 System Use Notification` will need to be in place and must be displayed at each session logon. | | | [6] | Due to potential information security risks, cloud based technologies may not be used without an Enterprise Security Change Control Board (ESCCB) approval. 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] | 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] | 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). | | | [9] | 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. | | | [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] | Under the advisement and direction of the Enterprise Systems Engineering (ESE) Enterprise Video Teleconferencing Network (EVTN) team this technology may only be used in support of the Veterans Health Administration (VHA) Office of Information and Analytics (OIA) Innovation Project #669. Upon completion of this pilot program a final decision on the applicability and deployment of this program will be considered. No further expansion or use of this technology is permitted unless a waiver has been granted to the project team that wishes to use the technology.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
The Initial Product Review notes the security constraints listed below:
It is imperative to utilize a Federal Information Processing Standards (FIPS) 140-2 validated cryptographic module to secure VA sensitive data in transit and when it is stored on endpoint devices. In addition, it is mandated to conduct a Privacy Impact Assessment (PIA) on information technology systems that collect, maintain, or disseminate personally identifiable information (PII) as stated in VA Handbook 6500, VA Directive 6508 - Privacy Impact Assessments, and VA Handbook 6508.1 - Privacy Impact Assessment (PIA).
Applications or systems should only process VA sensitive data after they have undergone and completed the VA`s formal Assessment Authorization (A&A) process. Coordination with various VA teams (i.e., Network Operations, Telehealth Services) is crucial to ensure that deliveries of VA core services are not impacted.
The following should be considered to secure the Vidyo infrastructure:
- Employ a mechanism for identity verification to ensure participants of the videoconference connection are who they say they are
- Enforce password that meets VA minimum requirements
- Ensure encryption keys are secured properly and only authorized staff have access to them
- Ensure recorded video conferences and conversation histories are securely saved on VA authorized and authorized systems
- Servers must adhere to hardening standards located at the VA Baseline Configuration Management website
- The system should keep access and usage logs for auditing purposes
- Employ continuous vulnerability monitoring for all components associated with Vidyo
It is advised that a security policy addressing the use of this product on wireless connections and/or mobile devices be created prior to usage. The implementing organization could craft something based upon the Rules of Behavior as outlined in VA Handbook 6500 Appendix D. A logon banner as directed in VA Handbook 6500 Appendix F `AC-8 System Use Notification` will need to be in place and must be displayed at each session logon. | | | [12] | Under the advisement and direction of the Enterprise Systems Engineering (ESE) Enterprise Video Teleconferencing Network (EVTN) team this technology may only be used in support of the Veterans Health Administration (VHA) Office of Information and Analytics (OIA) Innovation Project #669. Upon completion of this pilot program a final decision on the applicability and deployment of this program will be considered. No further expansion or use of this technology is permitted unless a waiver has been granted to the project team that wishes to use the technology.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
The Initial Product Review notes the security constraints listed below:
It is imperative to utilize a Federal Information Processing Standards (FIPS) 140-2 validated cryptographic module to secure VA sensitive data in transit and when it is stored on endpoint devices. In addition, it is mandated to conduct a Privacy Impact Assessment (PIA) on information technology systems that collect, maintain, or disseminate personally identifiable information (PII) as stated in VA Handbook 6500, VA Directive 6508 - Privacy Impact Assessments, and VA Handbook 6508.1 - Privacy Impact Assessment (PIA).
Applications or systems should only process VA sensitive data after they have undergone and completed the VA`s formal Assessment Authorization (A&A) process. Coordination with various VA teams (i.e., Network Operations, Telehealth Services) is crucial to ensure that deliveries of VA core services are not impacted.
The following should be considered to secure the Vidyo infrastructure:- Employ a mechanism for identity verification to ensure participants of the videoconference connection are who they say they are
- Enforce password that meets VA minimum requirements
- Ensure encryption keys are secured properly and only authorized staff have access to them
- Ensure recorded video conferences and conversation histories are securely saved on VA authorized and authorized systems
- Servers must adhere to hardening standards located at the VA Baseline Configuration Management website
- The system should keep access and usage logs for auditing purposes
- Employ continuous vulnerability monitoring for all components associated with Vidyo
It is advised that a security policy addressing the use of this product on wireless connections and/or mobile devices be created prior to usage. The implementing organization could craft something based upon the Rules of Behavior as outlined in VA Handbook 6500 Appendix D. A logon banner as directed in VA Handbook 6500 Appendix F `AC-8 System Use Notification` will need to be in place and must be displayed at each session logon. | | | [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] |
Per the Initial Product Review, users must abide by the following constraints:
-
It is imperative to utilize a FIPS 140-2 validated cryptographic module to secure VA sensitive data in transit and when it is stored on endpoint devices. In addition, it is mandated to conduct a Privacy Impact Assessment (PIA) on information technology systems that collect, maintain, or disseminate personally identifiable information (PII) as stated in VA Handbook 6500, VA Directive 6508 - Privacy Impact Assessments, and VA Handbook 6508.1 - Privacy Impact Assessment (PIA).
-
Applications or systems should only process VA sensitive data after they have undergone and completed the VA`s formal Assessment and Authorization (A&A) process. Coordination with various VA teams (i.e., Network Operations, Telehealth Services) is crucial to ensure that deliveries of VA core services are not impacted.
-
The following should be considered to secure the Vidyo infrastructure:
employ a mechanism for identity verification to ensure participants of the videoconference connection are who they say they are,
enforce password that meets VA minimum requirements,
ensure encryption keys are secured properly and only authorized staff have access to them,
ensure recorded video conferences and conversation histories are securely saved on VA authorized and authorized systems,
servers must adhere to hardening standards located at the VA Baseline Configuration Management website,
the system should keep access and usage logs for auditing purposes and
employ continuous vulnerability monitoring for all components associated with Vidyo
-
It is advised that a security policy addressing the use of this product on wireless connections and/or mobile devices be created prior to usage. The implementing organization could craft something based upon the Rules of Behavior as outlined in VA Handbook 6500 Appendix D. A logon banner as directed in VA Handbook 6500 Appendix F “AC-8 System Use Notification” will need to be in place and must be displayed at each session logon.
| | | [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] | 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 authorized and the user should take the proper steps to decline those installations. | | | [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. |
|
