1.4.x |
Approved w/Constraints [1, 2, 5, 6, 7] |
Approved w/Constraints [1, 2, 5, 6, 7] |
Approved w/Constraints [1, 2, 5, 6, 7] |
Approved w/Constraints [1, 2, 5, 6, 7] |
Approved w/Constraints [1, 2, 5, 6, 7] |
Approved w/Constraints [1, 2, 5, 6, 7] |
Approved w/Constraints [1, 2, 5, 6, 7] |
Approved w/Constraints [1, 2, 5, 6, 7] |
Approved w/Constraints [1, 2, 5, 6, 7] |
Approved w/Constraints [1, 2, 5, 6, 7] |
Approved w/Constraints [1, 2, 5, 6, 7] |
Approved w/Constraints [1, 2, 5, 6, 7] |
| | [1] | 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’)
Users must Divest the use of Internet Explorer with this technology. Other approved internet browsers are available. See Category Tab for details. | | [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] | 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. | | [4] | 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). | | [5] | 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. | | [6] | 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. | | [7] | 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). |
|