<Past |
Future> |
2.0.x |
Divest [3, 4, 5, 8] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
10.x |
Divest [3, 4, 5, 8] |
Divest [3, 4, 5, 8] |
Divest [3, 4, 5, 8] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
13.x |
Approved w/Constraints [3, 4, 5, 8] |
Approved w/Constraints [3, 4, 5, 8] |
Approved w/Constraints [3, 4, 5, 8] |
Divest [3, 4, 5, 9, 10] |
Divest [3, 4, 5, 9, 10] |
Divest [4, 5, 9, 10, 11] |
Divest [4, 5, 9, 10, 11] |
Divest [4, 5, 9, 10, 11] |
Divest [4, 5, 9, 10, 11] |
Unapproved |
Unapproved |
Unapproved |
16.0.x |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [3, 4, 5, 9, 10] |
Approved w/Constraints [3, 4, 5, 9, 10] |
Approved w/Constraints [4, 5, 9, 10, 11] |
Approved w/Constraints [4, 5, 9, 10, 11] |
Approved w/Constraints [4, 5, 9, 10, 11] |
Approved w/Constraints [4, 5, 9, 10, 11] |
Approved w/Constraints [4, 5, 9, 10, 11] |
Approved w/Constraints [4, 5, 9, 10, 11] |
Approved w/Constraints [4, 5, 9, 10, 11] |
| | [1] | This Technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population. | | [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] | This product is Class 2 or Class 3 VA-designed and built Local Software OR is a commercially-licensed software product purchased or leased that will run in a VA VISTA environment or integrate with Class 1 National VISTA Software. Presence of this software on the One-VA TRM does not equate to designation as a Class 1 National Software product and MUST NOT be assumed to comply with all VA programming standards, namespacing and interface control agreement standards, data management standards, documentation standards, information assurance standards, security standards and 508 compliance standards. As a Class 2 or Class 3 product, it MUST NOT be assumed to having been released into production through all OI&T product release and sustainment process controls for project management; requirements, development and testing management; and configuration, change, and release management necessary to satisfy OI&T process and product compliance. The OI&T Enterprise Program Management Office does not endorse nor support Class 2 and Class 3 products and does not support data usage or application programmer interfaces (APIs) between Class 1 National Software products and Class 2 or Class 3 products. Class 2 or Class 3 products must restrict their interfaces to Class 1 National Software to use of publicly-supported APIs ONLY. VA Directive 6402, Modifications to Standardized National Software, dictates the policy for Class 2 and Class 3 products and modifications to Class 1 National Software products. Local enhancements to, or modifications of, Class 1 Protected National Software (as listed in the Directive), in part or in whole, is PROHIBITED. Local enhancements to, or modifications of, Non-Protected Class 1 National Software is allowed ONLY with an approved waiver by the Software Modification Waiver Committee (SMWC). Class 2 and Class 3 software that does not modify the Class 1 National Software in any way must still adhere to namespacing and interface control agreement standards as well as National Field Operations Processes. | | [4] | Users must ensure that Google Chrome 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] | This Technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population. Contact your local CIO office if more information is needed in regards to the use of this technology. | | [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 ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | [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] | 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. | | [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. | | [11] | This product is Class 2 or Class 3 VA-designed and built Local Software OR is a commercially-licensed software product purchased or leased that will run in a VA VISTA environment or integrate with Class 1 National VISTA Software. Presence of this software on the One-VA TRM does not equate to designation as a Class 1 National Software product and MUST NOT be assumed to comply with all VA programming standards, namespacing and interface control agreement standards, data management standards, documentation standards, information assurance standards, security standards and 508 compliance standards. As a Class 2 or Class 3 product, it MUST NOT be assumed to having been released into production through all OI&T product release and sustainment process controls for project management; requirements, development and testing management; and configuration, change, and release management necessary to satisfy OI&T process and product compliance. The OI&T Enterprise Program Management Office does not endorse nor support Class 2 and Class 3 products and does not support data usage or application programmer interfaces (APIs) between Class 1 National Software products and Class 2 or Class 3 products. Class 2 or Class 3 products must restrict their interfaces to Class 1 National Software to use of publicly-supported APIs ONLY. VA Directive 6402, Modifications to Standardized National Software, dictates the policy for Class 2 and Class 3 products and modifications to Class 1 National Software products. Local enhancements to, or modifications of, Class 1 Protected National Software (as listed in the Directive), in part or in whole, is PROHIBITED. Local enhancements to, or modifications of, Non-Protected Class 1 National Software is allowed ONLY with an approved waiver by the Software Modification Waiver Committee (SMWC). Class 2 and Class 3 software that does not modify the Class 1 National Software in any way must still adhere to namespacing and interface control agreement standards as well as National Field Operations Processes. |
|
Note: |
At the time of writing, version 16.0.9 is the most current version, released 09/28/2023. |