4.x |
Approved w/Constraints [7, 12, 13, 14, 15, 16] |
Approved w/Constraints [7, 12, 13, 14, 15, 16] |
Approved w/Constraints [7, 12, 13, 14, 15, 16] |
Approved w/Constraints [7, 13, 14, 15, 17, 18] |
Approved w/Constraints [7, 13, 15, 17, 18, 19] |
Approved w/Constraints [7, 13, 15, 17, 18, 19] |
Approved w/Constraints [7, 13, 15, 17, 18, 19] |
Approved w/Constraints [7, 13, 15, 17, 18, 19] |
Approved w/Constraints [7, 13, 15, 17, 18, 19] |
Approved w/Constraints [7, 13, 15, 17, 18, 19] |
Approved w/Constraints [7, 13, 15, 17, 18, 19] |
Approved w/Constraints [7, 13, 15, 17, 18, 19] |
| | [1] | This Technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population. | | [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] | 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] | Version 4.x is approved only for test and evaluation without the use of PHI/PII/VA Sensitive data while the required baseline and/or hardening guide and other steps that are required for full production use outlined in the Initial Product Review (IPR) are completed. More information is in the referenced IPR.
| | [5] | 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. | | [6] | 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). | | [7] | 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. | | [8] | 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. | | [9] | 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. | | [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] | 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). | | [12] | Users must ensure that Firefox, Google Chrome, Microsoft .NET Framework, and Microsoft Internet Explorer (IE) are implemented within VA-approved baselines.
Per the Initial Product Review, users must abide by the following constraints:
- The product must be used with the VA approved implementation standard with
specific hardening guidance regarding the secure implementation of the
product. Please reference the implementation standard for CineMassive Video
Wall.
- CineNet Pro will require a 3rd party FIPS 140-2 certified solution for any data
containing PHI/PII or VA sensitive information.
- Users must ensure their use of this technology is consistent with VA policies,
procedures, and standards, including, but not limited to, VA Handbooks 6102
and 6500; VA Directives 6004, and 6513; and National Institute of Standards
and Technology (NIST) standards, including Federal Information Processing
Standards (FIPS).
| | [13] | 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. | | [14] | 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). | | [15] | 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. | | [16] | 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. | | [17] | Users must ensure that Firefox and Google Chrome are implemented within VA-approved baselines.
Users must utilize approved internet browsers, as Microsoft Internet Explorer has reached End of Life status. See Category Tab for details.
Per the Initial Product Review, users must abide by the following constraints:
- The product must be used with the VA approved implementation standard with
specific hardening guidance regarding the secure implementation of the
product. Please reference the implementation standard for CineMassive Video
Wall. https://dvagov.sharepoint.com/sites/OITBCM/supporting_documents/cinemas
sive%20video%20wall%20
%20enterprise%20implementation%20standard.pdf
- Haivision Command 360 will require a 3rd party FIPS 140-2 certified solution for any data
containing PHI/PII or VA sensitive information.
- Users must ensure their use of this technology is consistent with VA policies,
procedures, and standards, including, but not limited to, VA Handbooks 6102
and 6500; VA Directives 6004, and 6513; and National Institute of Standards
and Technology (NIST) standards, including Federal Information Processing
Standards (FIPS).
| | [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 ISSO (Information System Security Officer) to ensure compliance with both VA Handbook 6500 and VA Directive 6500. | | [19] | 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). |
|