<Past |
Future> |
1.10.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
1.11.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
1.16.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
1.21.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
1.23.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
1.24.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
1.28.x |
DIVEST [13, 14, 15, 16] |
DIVEST [13, 14, 15, 16] |
DIVEST [13, 14, 15, 16] |
DIVEST [4, 13, 15, 16, 17, 18] |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
1.29.x |
DIVEST [13, 14, 15, 16] |
DIVEST [13, 14, 15, 16] |
DIVEST [13, 14, 15, 16] |
DIVEST [4, 13, 15, 16, 17, 18] |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
1.30.x |
DIVEST [13, 14, 15, 16] |
DIVEST [13, 14, 15, 16] |
DIVEST [13, 14, 15, 16] |
DIVEST [4, 13, 15, 16, 17, 18] |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
1.31.x |
DIVEST [13, 14, 15, 16] |
DIVEST [13, 14, 15, 16] |
DIVEST [13, 14, 15, 16] |
DIVEST [4, 13, 15, 16, 17, 18] |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
1.32.x |
DIVEST [13, 14, 15, 16] |
DIVEST [13, 14, 15, 16] |
DIVEST [13, 14, 15, 16] |
DIVEST [4, 13, 15, 16, 17, 18] |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
1.33.x |
DIVEST [13, 14, 15, 16] |
DIVEST [13, 14, 15, 16] |
DIVEST [13, 14, 15, 16] |
DIVEST [4, 13, 15, 16, 17, 18] |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
1.34.x |
DIVEST [13, 14, 15, 16] |
DIVEST [13, 14, 15, 16] |
DIVEST [13, 14, 15, 16] |
DIVEST [4, 13, 15, 16, 17, 18] |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
1.35.x |
DIVEST [13, 14, 15, 16] |
DIVEST [13, 14, 15, 16] |
DIVEST [13, 14, 15, 16] |
DIVEST [4, 13, 15, 16, 17, 18] |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
1.36.x |
DIVEST [13, 14, 15, 16] |
DIVEST [13, 14, 15, 16] |
DIVEST [13, 14, 15, 16] |
DIVEST [4, 13, 15, 16, 17, 18] |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
1.37.x |
DIVEST [13, 14, 15, 16] |
DIVEST [13, 14, 15, 16] |
DIVEST [13, 14, 15, 16] |
DIVEST [4, 13, 15, 16, 17, 18] |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
1.38.x |
Approved w/Constraints [13, 14, 15, 16] |
Approved w/Constraints [13, 14, 15, 16] |
Approved w/Constraints [13, 14, 15, 16] |
DIVEST [4, 13, 15, 16, 17, 18] |
DIVEST [4, 15, 16, 17, 18, 19] |
DIVEST [15, 16, 17, 18, 19] |
DIVEST [15, 16, 17, 18, 19] |
Authorized w/ Constraints (DIVEST) [15, 16, 17, 18, 19] |
Authorized w/ Constraints (DIVEST) [15, 16, 17, 18, 19] |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
1.39.x |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [4, 13, 15, 16, 17, 18] |
Approved w/Constraints [4, 15, 16, 17, 18, 19] |
DIVEST [15, 16, 17, 18, 19] |
DIVEST [15, 16, 17, 18, 19] |
Authorized w/ Constraints (DIVEST) [15, 16, 17, 18, 19] |
Authorized w/ Constraints (DIVEST) [15, 16, 17, 18, 19] |
Authorized w/ Constraints (DIVEST) [15, 16, 17, 18, 19] |
Authorized w/ Constraints (DIVEST) [15, 16, 17, 18, 19] |
Authorized w/ Constraints (POA&M) |
2.5.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
DIVEST [15, 16, 17, 18, 19] |
DIVEST [15, 16, 17, 18, 19] |
Authorized w/ Constraints (DIVEST) [15, 16, 17, 18, 19] |
Authorized w/ Constraints (DIVEST) [15, 16, 17, 18, 19] |
Authorized w/ Constraints (DIVEST) [15, 16, 17, 18, 19] |
Authorized w/ Constraints (DIVEST) [15, 16, 17, 18, 19] |
Authorized w/ Constraints (POA&M) |
4.1.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
DIVEST [15, 16, 17, 18, 19] |
DIVEST [15, 16, 17, 18, 19] |
Authorized w/ Constraints (DIVEST) [15, 16, 17, 18, 19] |
Authorized w/ Constraints (DIVEST) [15, 16, 17, 18, 19] |
Authorized w/ Constraints (DIVEST) [15, 16, 17, 18, 19] |
Authorized w/ Constraints (DIVEST) [15, 16, 17, 18, 19] |
Authorized w/ Constraints (POA&M) |
5.12.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
DIVEST [15, 16, 17, 18, 19] |
DIVEST [15, 16, 17, 18, 19] |
Authorized w/ Constraints (DIVEST) [15, 16, 17, 18, 19] |
Authorized w/ Constraints (DIVEST) [15, 16, 17, 18, 19] |
Authorized w/ Constraints (DIVEST) [15, 16, 17, 18, 19] |
Authorized w/ Constraints (DIVEST) [15, 16, 17, 18, 19] |
Authorized w/ Constraints (POA&M) |
5.16.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [15, 16, 17, 18, 19] |
Approved w/Constraints [15, 16, 17, 18, 19] |
Authorized w/ Constraints [15, 16, 17, 18, 19] |
Authorized w/ Constraints [15, 16, 17, 18, 19] |
Authorized w/ Constraints [15, 16, 17, 18, 19] |
Authorized w/ Constraints [15, 16, 17, 18, 19] |
Authorized w/ Constraints [15, 16, 17, 18, 19] |
| | [1] | Known security vulnerabilities must be properly remediated prior to product deployment. Product must remain properly patched per Federal and Department standards in order to mitigate known and future security vulnerabilities.
Users may not use the comments and notes function for any type of Personally Identifiable Information (PII), Protected Health Information (PHI) or VA sensitive information since those functions are stored outside the VA and are not protected. | | [2] | Users may not use the comments and notes function for any type of Personally Identifiable Information (PII), Protected Health Information (PHI) or VA sensitive information since those functions are stored outside the VA and are not protected. | | [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] | 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. | | [5] | Users may not use the comments and notes function for any type of Personally Identifiable Information (PII)/Protected Health Information (PHI) or VA sensitive information since those functions are stored outside the VA and are not protected. | | [6] | 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 authorized and the user should take the proper steps to decline those installations. | | [7] | 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. | | [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 ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | [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 Project Special Forces (SPF) team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | [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 ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | [11] | 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). | | [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 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). | | [13] | 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). | | [14] | 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. | | [15] | 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 authorized and the user should take the proper steps to decline those installations. | | [16] | 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. | | [17] | 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. | | [18] | 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. | | [19] | 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 5.16.8 is the most current version released. |