<Past |
Future> |
17.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
18.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
19.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
20.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
21.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
22.x |
Divest [2, 14, 16, 17, 18] |
Divest [2, 16, 17, 18, 19] |
Divest [2, 16, 17, 18, 19] |
Divest [2, 16, 17, 18, 19] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
23.x |
Approved w/Constraints [2, 14, 16, 17, 18] |
Divest [2, 16, 17, 18, 19] |
Divest [2, 16, 17, 18, 19] |
Divest [2, 16, 17, 18, 19] |
Divest [2, 16, 17, 18, 19] |
Divest [2, 16, 17, 18, 19] |
Divest [2, 16, 17, 18, 19] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
24.x |
Unapproved |
Approved w/Constraints [2, 16, 17, 18, 19] |
Approved w/Constraints [2, 16, 17, 18, 19] |
Approved w/Constraints [2, 16, 17, 18, 19] |
Approved w/Constraints [2, 16, 17, 18, 19] |
Approved w/Constraints [2, 16, 17, 18, 19] |
Approved w/Constraints [2, 16, 17, 18, 19] |
Approved w/Constraints [2, 16, 17, 18, 19] |
Approved w/Constraints [2, 16, 17, 18, 19] |
Approved w/Constraints [2, 16, 17, 18, 19] |
Approved w/Constraints [2, 16, 17, 18, 19] |
Approved w/Constraints [2, 16, 17, 18, 19] |
| | [1] | 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. | | [2] | 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. | | [3] | Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). | | [4] | 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. | | [5] | Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). | | [6] | 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. | | [7] | It is advised that if this product is used within the Department of Veterans Affairs (VA) that the following constraints be applied: 1. Ensure use of a FIPS 140-2 validated cryptographic module to secure VA sensitive data in applications and devices that use Nuance Clintegrity. 2. VA must require that the vendor provide security patching and updates for AdoptOpenJDK in a timely manner. 3. Extended support for Java SE 8 is available until March 2025, and the vendor must manage the Java version upgrade roadmap. | | [8] | Per the Initial Product Review, users must abide by the following constraints:
- Ensure use of a FIPS 140-2 validated cryptographic module to secure VA sensitive data in applications and devices that use Nuance Clintegrity.
- The vendor indicated that Nuance servers that run the Nuance Clintegrity software will be utilizing AdoptJDK on the vendors end. The vendor has ensured the VA that AdoptJDK will not be used on the client side. Additionally, the vendor has indicated that they will provide security patching and updates for AdoptJDK. The VA must require that the vendor provide security patching and updates in a timely manner.
- Extended support for Java SE 8 is available until March 2025, and the vendor must manage the Java version upgrade roadmap.
Users must ensure that Microsoft Internet Explorer (IE) and Microsoft Structured Query Language (SQL) Server are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) | | [9] | Per the Initial Product Review, users must abide by the following constraints:
- Ensure use of a FIPS 140-2 validated cryptographic module to secure VA sensitive data in applications and devices that use Nuance Clintegrity.
- The vendor indicated that Nuance servers that run the Nuance Clintegrity software will be utilizing AdoptJDK on the vendors end. The vendor has ensured the VA that AdoptJDK will not be used on the client side. Additionally, the vendor has indicated that they will provide security patching and updates for AdoptJDK. The VA must require that the vendor provide security patching and updates in a timely manner.
- Extended support for Java SE 8 is available until March 2025, and the vendor must manage the Java version upgrade roadmap.
Users must ensure that Microsoft Internet Explorer (IE) and Microsoft Structured Query Language (SQL) Server are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) | | [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] | Per the Initial Product Review, users must abide by the following constraints:
- Ensure use of a FIPS 140-2 validated cryptographic module to secure VA sensitive data in applications and devices that use Nuance Clintegrity.
- The vendor indicated that Nuance servers that run the Nuance Clintegrity software will be utilizing AdoptJDK on the vendors end. The vendor has ensured the VA that AdoptJDK will not be used on the client side. Additionally, the vendor has indicated that they will provide security patching and updates for AdoptJDK. The VA must require that the vendor provide security patching and updates in a timely manner.
- Extended support for Java SE 8 is available until March 2025, and the vendor must manage the Java version upgrade roadmap.
Users must ensure that Firefox, Google Chrome, Apache Tomcat, Adobe Acrobat Reader Document Cloud (DC), Microsoft Internet Explorer (IE) and Microsoft Structured Query Language (SQL) Server are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Microsoft Internet Explorer, a dependency of this technology, is in a Divested status at the time of writing. | | [12] | Per the Initial Product Review, users must abide by the following constraints:
- Ensure use of a FIPS 140-2 validated cryptographic module to secure VA sensitive data in applications and devices that use Nuance Clintegrity.
- The vendor indicated that Nuance servers that run the Nuance Clintegrity software will be utilizing AdoptOpenJDK on the vendors end. The vendor has ensured the VA that AdoptOpenJDK will not be used on the client side. Additionally, the vendor has indicated that they will provide security patching and updates for AdoptOpenJDK. The VA must require that the vendor provide security patching and updates in a timely manner.
- Extended support for Java SE 8 is available until March 2025, and the vendor must manage the Java version upgrade roadmap.
Users must ensure that Firefox, Google Chrome, Apache Tomcat, Adobe Acrobat Reader Document Cloud (DC), Microsoft Internet Explorer (IE) and Microsoft Structured Query Language (SQL) Server are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Users must Divest the use of Internet Explorer with this technology. Other approved internet browsers are available. See Category Tab for details.
AdoptOpenJDK is unapproved on the TRM and will not be used on the VA client side. | | [13] | 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. | | [14] | Users must ensure that Apache Tomcat, Citrix Virtual Apps and Desktops (CVAD) and Microsoft Structured Query Language (SQL) Server are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Users must utilize approved internet browsers, as Microsoft Internet Explorer has reached End of Life status. See Category Tab for details.
Users must not utilize AdoptOpenJDK, as it is at the time of writing, unapproved in the TRM.
Per the Initial Product Review, users must abide by the following constraints:
- Ensure use of a FIPS 140-2 certified cryptographic module to secure VA sensitive data in applications and devices that use Nuance Clintegrity.
- The vendor indicated that Nuance servers that run the Nuance Clintegrity software will be utilizing AdoptJDK on the vendors end. The vendor has ensured the VA that AdoptJDK will not be used on the client side. Additionally, the vendor has indicated that they will provide security patching and updates for AdoptJDK. The VA must require that the vendor provide security patching and updates in a timely manner.
- Extended support for Java SE 8 is available until March 2025, and the vendor has agreed to manage the Java version upgrade roadmap.
| | [15] | Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information System Security Officer (ISSO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). | | [16] | 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. | | [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] | Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 or its successor to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 or 140-3 compliant full disk encryption (FOE) must be implemented on the storage device where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information System Security Officer (ISSO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). By September 22, 2026, all FIPS 140-2 certificate validations will be placed on the Historical List, please refer to FIPS Transition Effort for further guidance and timeline of changes. | | [19] | Users must ensure that Firefox, Google Chrome, Microsoft Edge, Apache Tomcat, Citrix Virtual Apps and Desktops (CVAD) and Microsoft Structured Query Language (SQL) Server are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Users must not utilize AdoptOpenJDK, as it is at the time of writing, unapproved in the TRM.
Per the Initial Product Review, users must abide by the following constraints:
- Ensure use of a FIPS 140-2 certified cryptographic module to secure VA sensitive data in applications and devices that use Nuance Clintegrity.
- The vendor indicated that Nuance servers that run the Nuance Clintegrity software will be utilizing AdoptJDK on the vendors end. The vendor has ensured the VA that AdoptJDK will not be used on the client side. Additionally, the vendor has indicated that they will provide security patching and updates for AdoptJDK. The VA must require that the vendor provide security patching and updates in a timely manner.
- Extended support for Java SE 8 is available until March 2025, and the vendor has agreed to manage the Java version upgrade roadmap.
|
|
Note: |
At the time of writing, version 24.1.1 is the most current version. |