21.x |
Approved w/Constraints [1, 3, 6, 7, 8, 9] |
Approved w/Constraints [1, 3, 6, 7, 8, 9] |
Approved w/Constraints [1, 3, 6, 7, 8, 9] |
Approved w/Constraints [1, 3, 6, 7, 9, 10] |
Approved w/Constraints [3, 6, 9, 10, 11, 12] |
Approved w/Constraints [3, 6, 9, 10, 11, 12] |
Approved w/Constraints [3, 6, 9, 10, 11, 12] |
Authorized w/ Constraints [3, 6, 9, 10, 11, 12] |
Authorized w/ Constraints (DIVEST) [3, 6, 9, 10, 12, 13, 14] |
Authorized w/ Constraints (DIVEST) [3, 6, 9, 10, 12, 13, 14] |
Authorized w/ Constraints (DIVEST) [3, 6, 9, 10, 12, 13, 14] |
Authorized w/ Constraints (DIVEST) [3, 6, 9, 10, 12, 13, 14] |
22.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints [3, 6, 9, 10, 12, 13, 14] |
Authorized w/ Constraints [3, 6, 9, 10, 12, 13, 14] |
Authorized w/ Constraints [3, 6, 9, 10, 12, 13, 14] |
Authorized w/ Constraints [3, 6, 9, 10, 12, 13, 14] |
| | [1] | Users must Divest the use of Internet Explorer with this technology. Other authorized internet browsers are available. See Category Tab for details.
Users must ensure that Microsoft .NET Framework, Microsoft Internet Explorer (IE), Firefox, and Google Chrome are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
This technology can potentially use Secure Sockets Layer (SSL), an unapproved protocol. | | [3] | 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. | | [6] | 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. | | [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 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). | | [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 ISSO (Information System 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 ISSO (Information System Security Officer) can advise on the ESCCB review process. | | [10] | 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. | | [11] | Users must ensure that Microsoft Edge, Firefox, and Google Chrome are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
This technology can potentially use Secure Sockets Layer (SSL), an unapproved protocol. | | [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, visit the Product Marketplace. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | [13] | Users must ensure that Microsoft Edge, Firefox, and Google Chrome are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Users must not utilize Secure Sockets Layer (SSL), as it, at the time of writing, requires a POA&M. | | [14] | 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. |
|