<Past |
Future> |
1.2.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
1.3.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
1.4.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
1.5.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
1.6.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
1.7.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
1.8.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.0.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.1.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.2.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.3.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.4.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.5.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.6.x |
Divest [2, 5, 12, 13, 15, 16, 17, 18] |
Divest [2, 5, 12, 13, 15, 16, 17, 18] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.7.x |
Divest [2, 5, 12, 13, 15, 16, 17, 18] |
Divest [2, 5, 12, 13, 15, 16, 17, 18] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.8.x |
Divest [2, 5, 12, 13, 15, 16, 17, 18] |
Divest [2, 5, 12, 13, 15, 16, 17, 18] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.9.x |
Divest [2, 5, 12, 13, 15, 16, 17, 18] |
Divest [2, 5, 12, 13, 15, 16, 17, 18] |
Divest [2, 5, 12, 13, 15, 16, 17, 18] |
Divest [2, 5, 12, 13, 15, 16, 17, 18] |
Divest [2, 5, 12, 13, 15, 16, 17, 18] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.10.x |
Divest [2, 5, 12, 13, 15, 16, 17, 18] |
Divest [2, 5, 12, 13, 15, 16, 17, 18] |
Divest [2, 5, 12, 13, 15, 16, 17, 18] |
Divest [2, 5, 12, 13, 15, 16, 17, 18] |
Divest [2, 5, 12, 13, 15, 16, 17, 18] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.11.x |
Divest [2, 5, 12, 13, 15, 16, 17, 18] |
Divest [2, 5, 12, 13, 15, 16, 17, 18] |
Divest [2, 5, 12, 13, 15, 16, 17, 18] |
Divest [2, 5, 12, 13, 15, 16, 17, 18] |
Divest [2, 5, 12, 13, 15, 16, 17, 18] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.12.x |
Divest [2, 5, 12, 13, 15, 16, 17, 18] |
Divest [2, 5, 12, 13, 15, 16, 17, 18] |
Divest [2, 5, 12, 13, 15, 16, 17, 18] |
Divest [2, 5, 12, 13, 15, 16, 17, 18] |
Divest [2, 5, 12, 13, 15, 16, 17, 18] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.20.x |
Divest [2, 5, 12, 13, 15, 16, 17, 18] |
Divest [2, 5, 12, 13, 15, 16, 17, 18] |
Divest [2, 5, 12, 13, 15, 16, 17, 18] |
Divest [2, 5, 12, 13, 15, 16, 17, 18] |
Divest [2, 5, 12, 13, 15, 16, 17, 18] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.21.x |
Approved w/Constraints [2, 5, 12, 13, 15, 16, 17, 18] |
Divest [2, 5, 12, 13, 15, 16, 17, 18] |
Divest [2, 5, 12, 13, 15, 16, 17, 18] |
Divest [2, 5, 12, 13, 15, 16, 17, 18] |
Divest [2, 5, 12, 13, 15, 16, 17, 18] |
Divest [2, 5, 12, 13, 15, 16, 17, 18] |
Divest [2, 5, 12, 13, 15, 16, 17, 18] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.22.x |
Unapproved |
Approved w/Constraints [2, 5, 12, 13, 15, 16, 17, 18] |
Approved w/Constraints [2, 5, 12, 13, 15, 16, 17, 18] |
Approved w/Constraints [2, 5, 12, 13, 15, 16, 17, 18] |
Approved w/Constraints [2, 5, 12, 13, 15, 16, 17, 18] |
Approved w/Constraints [2, 5, 12, 13, 15, 16, 17, 18] |
Approved w/Constraints [2, 5, 12, 13, 15, 16, 17, 18] |
Approved w/Constraints [2, 5, 12, 13, 15, 16, 17, 18] |
Approved w/Constraints [2, 5, 12, 13, 15, 16, 17, 18] |
Approved w/Constraints [2, 5, 12, 13, 15, 16, 17, 18] |
Approved w/Constraints [2, 5, 12, 13, 15, 16, 17, 18] |
Approved w/Constraints [2, 5, 12, 13, 15, 16, 17, 18] |
| | [1] | 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 approved and the user should take the proper steps to decline those installations. | | [2] | Use of this technology is limited to VA staff charged with ensuring the security of the VA network infrastructure. VA staff performing analysis with this technology need to work closely with system owners and agree on security scanning rules, such as the assets scanned, along the schedule and frequency of those scans. | | [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] | Users must ensure that Microsoft .NET Framework is implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) | | [5] | 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] | 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. | | [7] | Users must ensure that Microsoft .NET Framework is implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
This technology can utilize commercial cloud storage options (Google Drive, Microsoft OneDrive, Dropbox, ect.) These services are prohibited in the VA and these options must not be utilized. | | [8] | 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. | | [9] | 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). | | [10] | This technology can utilize commercial cloud storage options (Google Drive and Dropbox). These services are prohibited in the VA and these options must not be utilized. | | [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 VA Handbook 6500. | | [12] | Users should check with their supervisor, Information System Security Officer (ISSO) 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 approved and the user should take the proper steps to decline those installations. | | [13] | 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. | | [14] | This technology can utilize commercial cloud storage options (Google Drive and Dropbox). These services are unapproved in the VA and these options must not be utilized. | | [15] | 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. | | [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 both VA Handbook 6500 and VA Directive 6500. | | [17] | This technology should not be utilizing commercial storage options, such as Google Drive and Dropbox, as they are unapproved in the VA. | | [18] | 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). |
|
Note: |
At the time of writing, version 2.22.0 is the most current version, released 04/09/2024. |