<Past |
Future> |
1.0.x |
Approved w/Constraints [1, 2, 3, 5, 6, 7] |
Approved w/Constraints [1, 2, 3, 5, 6, 8] |
Approved w/Constraints [1, 2, 3, 5, 6, 8] |
Approved w/Constraints [1, 2, 3, 5, 6, 8] |
Approved w/Constraints [1, 3, 6, 8, 9, 10] |
Approved w/Constraints [1, 3, 6, 8, 9, 10] |
Approved w/Constraints [1, 3, 6, 8, 9, 10] |
Approved w/Constraints [1, 3, 6, 8, 10, 11] |
Approved w/Constraints [1, 3, 6, 10, 11, 12] |
Divest [3, 6, 10, 11, 12, 13, 14] |
Divest [3, 6, 10, 11, 12, 13, 14] |
Divest [3, 6, 10, 11, 12, 13, 14] |
1.1.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Divest [3, 6, 10, 11, 12, 13, 14] |
Divest [3, 6, 10, 11, 12, 13, 14] |
Divest [3, 6, 10, 11, 12, 13, 14] |
1.2.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Divest [3, 6, 10, 11, 12, 13, 14] |
Divest [3, 6, 10, 11, 12, 13, 14] |
Divest [3, 6, 10, 11, 12, 13, 14] |
1.3.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Divest [3, 6, 10, 11, 12, 13, 14] |
Divest [3, 6, 10, 11, 12, 13, 14] |
Divest [3, 6, 10, 11, 12, 13, 14] |
1.4.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Divest [3, 6, 10, 11, 12, 13, 14] |
Divest [3, 6, 10, 11, 12, 13, 14] |
Divest [3, 6, 10, 11, 12, 13, 14] |
1.5.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Divest [3, 6, 10, 11, 12, 13, 14] |
Divest [3, 6, 10, 11, 12, 13, 14] |
Divest [3, 6, 10, 11, 12, 13, 14] |
1.6.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Divest [3, 6, 10, 11, 12, 13, 14] |
Divest [3, 6, 10, 11, 12, 13, 14] |
Divest [3, 6, 10, 11, 12, 13, 14] |
1.7.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Divest [3, 6, 10, 11, 12, 13, 14] |
Divest [3, 6, 10, 11, 12, 13, 14] |
Divest [3, 6, 10, 11, 12, 13, 14] |
1.8.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Divest [3, 6, 10, 11, 12, 13, 14] |
Divest [3, 6, 10, 11, 12, 13, 14] |
Divest [3, 6, 10, 11, 12, 13, 14] |
1.9.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Divest [3, 6, 10, 11, 12, 13, 14] |
Divest [3, 6, 10, 11, 12, 13, 14] |
Divest [3, 6, 10, 11, 12, 13, 14] |
1.10.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Divest [3, 6, 10, 11, 12, 13, 14] |
Divest [3, 6, 10, 11, 12, 13, 14] |
Divest [3, 6, 10, 11, 12, 13, 14] |
1.11.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Divest [3, 6, 10, 11, 12, 13, 14] |
Divest [3, 6, 10, 11, 12, 13, 14] |
Divest [3, 6, 10, 11, 12, 13, 14] |
1.12.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Divest [3, 6, 10, 11, 12, 13, 14] |
Divest [3, 6, 10, 11, 12, 13, 14] |
Divest [3, 6, 10, 11, 12, 13, 14] |
1.13.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Divest [3, 6, 10, 11, 12, 13, 14] |
Divest [3, 6, 10, 11, 12, 13, 14] |
Divest [3, 6, 10, 11, 12, 13, 14] |
1.14.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Divest [3, 6, 10, 11, 12, 13, 14] |
Divest [3, 6, 10, 11, 12, 13, 14] |
Divest [3, 6, 10, 11, 12, 13, 14] |
1.15.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Divest [3, 6, 10, 11, 12, 13, 14] |
Divest [3, 6, 10, 11, 12, 13, 14] |
Divest [3, 6, 10, 11, 12, 13, 14] |
1.16.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Divest [3, 6, 10, 11, 12, 13, 14] |
Divest [3, 6, 10, 11, 12, 13, 14] |
Divest [3, 6, 10, 11, 12, 13, 14] |
1.17.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Divest [3, 6, 10, 11, 12, 13, 14] |
Divest [3, 6, 10, 11, 12, 13, 14] |
Divest [3, 6, 10, 11, 12, 13, 14] |
1.18.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Divest [3, 6, 10, 11, 12, 13, 14] |
Divest [3, 6, 10, 11, 12, 13, 14] |
Divest [3, 6, 10, 11, 12, 13, 14] |
1.19.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Divest [3, 6, 10, 11, 12, 13, 14] |
Divest [3, 6, 10, 11, 12, 13, 14] |
Divest [3, 6, 10, 11, 12, 13, 14] |
1.20.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Divest [3, 6, 10, 11, 12, 13, 14] |
Divest [3, 6, 10, 11, 12, 13, 14] |
Divest [3, 6, 10, 11, 12, 13, 14] |
1.21.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Divest [3, 6, 10, 11, 12, 13, 14] |
Divest [3, 6, 10, 11, 12, 13, 14] |
Divest [3, 6, 10, 11, 12, 13, 14] |
1.22.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Divest [3, 6, 10, 11, 12, 13, 14] |
Divest [3, 6, 10, 11, 12, 13, 14] |
Divest [3, 6, 10, 11, 12, 13, 14] |
1.23.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Divest [3, 6, 10, 11, 12, 13, 14] |
Divest [3, 6, 10, 11, 12, 13, 14] |
Divest [3, 6, 10, 11, 12, 13, 14] |
1.24.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Divest [3, 6, 10, 11, 12, 13, 14] |
Divest [3, 6, 10, 11, 12, 13, 14] |
Divest [3, 6, 10, 11, 12, 13, 14] |
1.25.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [3, 6, 10, 11, 12, 13, 14] |
Approved w/Constraints [3, 6, 10, 11, 12, 13, 14] |
Approved w/Constraints [3, 6, 10, 11, 12, 13, 14] |
| | [1] | This technology requires using a Universal Service Bus (USB) technology to transfer data into the records. As such, proper precautions need to be taken to protect data.
Users must ensure that FireFox, Google Chrome, Microsoft .Net Framework, and Microsoft Internet Explorer (IE) are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) | | [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] | 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. | | [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 Project Special Forces (SPF) team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | [5] | 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. | | [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 Project Special Forces (PSF) team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | [8] | 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). | | [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 ISSO (Information System Security Officer) to ensure compliance with VA Handbook 6500. | | [10] | 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. | | [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 ISSO (Information System Security Officer) to ensure compliance with both VA Handbook 6500 and VA Directive 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, visit the Product Marketplace.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | [13] | This technology requires using a Universal Service Bus (USB) technology to transfer data into the records. As such, proper precautions need to be taken to protect data.
Users must ensure that FireFox, Google Chrome, and Microsoft Edge are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) | | [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. |
|
Note: |
At the time of writing, version 1.25.4 is the most current version. |