<Past |
Future> |
7.2.x |
Divest [1, 2, 3, 4] |
Divest [1, 2, 4, 5] |
Divest [1, 2, 4, 5] |
Divest [1, 2, 4, 5] |
Divest [1, 4, 5, 6] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
7.3.x |
Divest [1, 2, 3, 4] |
Divest [1, 2, 4, 5] |
Divest [1, 2, 4, 5] |
Divest [1, 2, 4, 5] |
Divest [1, 4, 5, 6] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
7.4.x |
Approved w/Constraints [1, 2, 3, 4] |
Approved w/Constraints [1, 2, 4, 5] |
Approved w/Constraints [1, 2, 4, 5] |
Approved w/Constraints [1, 2, 4, 5] |
Approved w/Constraints [1, 4, 5, 6] |
Approved w/Constraints [1, 4, 5, 6] |
Approved w/Constraints [1, 4, 5, 6] |
Approved w/Constraints [1, 4, 5, 6] |
Divest [4, 6, 7, 8, 9, 10] |
Divest [4, 6, 7, 8, 9, 10] |
Unapproved |
Unapproved |
7.5.x |
Approved w/Constraints [1, 2, 3, 4] |
Approved w/Constraints [1, 2, 4, 5] |
Approved w/Constraints [1, 2, 4, 5] |
Approved w/Constraints [1, 2, 4, 5] |
Approved w/Constraints [1, 4, 5, 6] |
Approved w/Constraints [1, 4, 5, 6] |
Approved w/Constraints [1, 4, 5, 6] |
Approved w/Constraints [1, 4, 5, 6] |
Divest [4, 6, 7, 8, 9, 10] |
Divest [4, 6, 7, 8, 9, 10] |
Unapproved |
Unapproved |
7.9.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
8.0.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
8.1.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
8.2.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Divest [4, 6, 7, 8, 9, 10] |
Divest [4, 6, 7, 8, 9, 10] |
Unapproved |
Unapproved |
| | [1] | Users must ensure that Microsoft .NET Framework is implemented with VA-approved baselines. | | [2] | Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, extra vigilance should be applied to ensure the versions remain properly patched to mitigate known and future vulnerabilities. The local ISO can provide assistance in reviewing the NIST vulnerabilities. | | [3] | 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). | | [4] | 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. | | [5] | 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). | | [6] | Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, extra vigilance should be applied to ensure the versions remain properly patched to mitigate known and future vulnerabilities. The local ISSO (Information System Security Officer) can provide assistance in reviewing the NIST vulnerabilities. | | [7] | 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. | | [8] | 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. | | [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, visit the Product Marketplace.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | [10] | 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 8.2.1 is the most current version, released 01/09/2024. |