| Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to,
VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information
Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users
should check with their supervisor, Information System Security Officer (ISSO), Facility Chief Information Officer (CIO), or local Office of Information and Technology
(OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation. |
| The VA Decision Matrix displays the current and future VAIT
position regarding different releases of a TRM entry. These decisions are
based upon the best information available as of the most current date. The consumer of this information has the
responsibility to consult the organizations responsible for the desktop, testing, and/or production environments
to ensure that the target version of the technology will be supported.
|
|
|
| Legend: |
| White |
Authorized: The technology/standard has been authorized for use.
|
| Yellow |
Authorized w/ Constraints: The technology/standard can be used within the specified constraints located
below the decision matrix in the footnote[1] and on the General tab.
|
| Gray |
Unauthorized, Conditions Required[a]
: This technology or standard can be used only if a POA&M review is conducted and signed by
the Authorizing Official Designated Representative (AODR) as designated by the Authorizing Official (AO) or designee
and based upon a recommendation from the POA&M Compliance Enforcement,
has been granted to the project team or organization that wishes to use the technology.
|
| Orange |
Unauthorized, Conditions Required[b]
: VA has decided to divest itself on the use of the technology/standard.
As a result, all projects currently utilizing the technology/standard must plan to eliminate their use of
the technology/standard. Additional information on when the entry is projected to become unauthorized may be
found on the Decision tab for the specific entry.
|
| Black |
Unauthorized: The technology/standard is not (currently) permitted to be used under any circumstances.
|
| Blue |
Unauthorized, Conditions Required[c]
: The period of time 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. If a customer would like to use this technology, please work with
your local or Regional OI&T office and contact the appropriate evaluation office
displayed in the notes below the decision matrix. The Local or Regional OI&T
office should submit an
inquiry to the TRM
if they require further assistance or if the evaluating office is not listed in the notes below.
|
|
| Release/Version Information: |
|
VA decisions for specific versions may include a ‘.x’ wildcard, which denotes a decision that pertains to a range of multiple versions.
|
|
For example, a technology authorized with a decision for 7.x would cover any version of 7.(Anything) - 7.(Anything). However, a 7.4.x decision
would cover any version of 7.4.(Anything), but would not cover any version of 7.5.x or 7.6.x on the TRM.
|
|
VA decisions for specific versions may include ‘+’ symbols; which denotes that the decision for the version specified also includes versions greater than
what is specified but is not to exceed or affect previous decimal places.
|
|
For example, a technology authorized with a decision for 12.6.4+ would cover any version that is greater than 12.6.4, but would not exceed the .6 decimal ie: 12.6.401
is ok, 12.6.5 is ok, 12.6.9 is ok, however 12.7.0 or 13.0 is not.
|
| Any major.minor version that is not listed in the VA Decision Matrix is considered Unauthorized, Conditions Required
[a]
. |
|
<Past |
Future> |
| 14.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints
[1, 2, 3, 4, 5, 6] |
Approved w/Constraints
[1, 2, 3, 4, 5, 6] |
Authorized w/ Constraints
[1, 2, 3, 4, 5, 6] |
Authorized w/ Constraints
[1, 2, 3, 4, 5, 6] |
Authorized w/ Constraints
[1, 2, 3, 4, 5, 6] |
Authorized w/ Constraints (DIVEST)
[2, 3, 4, 5, 6, 7] |
Authorized w/ Constraints (DIVEST)
[2, 3, 4, 5, 6, 7] |
| 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
[2, 3, 4, 5, 6, 7] |
Authorized w/ Constraints
[2, 3, 4, 5, 6, 7] |
| Note: |
At the time of writing, version 16.0 (1044) is the most current version, released 02/24/2025. |
| | | | [1] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
This technology requires using a Universal Service Bus (USB) technology to transfer data into the records. As such, proper precautions need to be taken to protect data.
This technology should not be used with Open Java Development Kit (OpenJDK) as it is unapproved for use at this time. There are other authorized java environments available. See Category tab for details.
Users must ensure that Google Chrome, Firefox, and Microsoft Edge are implemented with VA-authorized baselines. (Refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Per the Security Assessment Review, users must abide by the following constraints:
- ESChat PC Client for Windows will require a 3rd party FIPS 140-2 or its successor certified solution for any data containing PHI/PII or VA sensitive information.
- System Owners/Administrators need to be aware that Windows Defender blocks the installation of the product. Once the file is downloaded, the unblock option must be checked in the file properties to allow installation.
- To mitigate, an administrator shall monitor the .exe files used by the application with a file integrity checker to ensure no
unauthorized changes occur.
- To mitigate, the vendor must maintain all third-party components during the entire product lifecycle, including responding to vulnerabilities discovered in third-party components used in the product.
- To mitigate, the ISSO shall educate and prohibit users from using the integrated cloud service capability until the VA Cloud Security
Requirements have been met and the affected A&A package has been appropriately updated.
- To mitigate, an administrator shall verify that the version of the software that they are requesting is the same version number that shows up on the installed systems Programs and Features.
- To mitigate, an administrator shall contact the vendor to request a hash to use to verify the validity of the downloaded installer file as well as the installed executable and ensure that these files are validated before use.
| | | [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 ISSO (Information System Security Officer) to ensure compliance with both VA Handbook 6500 and VA Directive 6500. | | | [3] | 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. | | | [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] | 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). | | | [6] | 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. | | | [7] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
This technology requires using a Universal Service Bus (USB) technology to transfer data into the records. As such, proper precautions need to be taken to protect data.
This technology should not be used with Open Java Development Kit (OpenJDK) as it requires a POA&M. There are other authorized java environments available. See Category tab for details.
Users must ensure that Google Chrome, Firefox, and Microsoft Edge are implemented with VA-authorized baselines. (Refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Per the Security Assessment Review, users must abide by the following constraints:
- A vulnerability exists because ESChat PC Client for Windows v14.0.989 is not FIPS 140-2 or its successor certified. To mitigate, ESChat PC Client for Windows will require a 3rd party FIPS 140-2 or its successor certified solution for any data containing PHI/PII or VA sensitive information.
- A vulnerability exists because Windows Defender blocked the installation of ESChat PC Client for Windows v14.0.989 noting that the publisher was unknown. The test engineer had to check the “Unblock” box in the Security section of the installer file’s properties menu to allow the application to install. To mitigate, System Owners/Administrators need to be aware that Windows Defender blocks the installation of the product. Once the file is downloaded, the unblock option must be checked in the file properties to allow installation.
- A vulnerability exists because ESChat PC Client for Windows v14.0.989 installs two .exe files without a digital signature. This prevents the verification of the controls publisher and assurance that it has not been tampered with since being published. To mitigate, an administrator shall monitor the .exe files used by the application with a file integrity checker to ensure no unauthorized changes occur.
- A vulnerability exists because ESChat PC Client for Windows v14.0.989 includes OpenJDK v22.0.0.0, an open-source software that is not approved in the VA Technical Reference Model (TRM). OpenJDK is a third-party component incorporated into ESChat PC Client for Windows. To mitigate, the vendor must maintain all third-party components during the entire product lifecycle, including responding to vulnerabilities discovered in third-party components used in the product.
- A vulnerability exists because the ESChat subscription service is hosted on Amazon AWS or in a private cloud using the customer’s own hardware. To mitigate, the ISSO shall educate and prohibit users from using the integrated cloud service capability until the VA Cloud Security Requirements have been met and the affected A&A package has been appropriately updated.
- A vulnerability exists because The ESChat PC Client Setup Program is listed as version 2.14.0.989. while the installed application is listed as ESChat PC Client version 14.0.989. The discrepancy between version numbers has been known to cause problems with version control across the enterprise resulting in software being mistakenly removed from systems. To remediate, an administrator shall verify that the version of the software that they are requesting is the same version number that shows up on the installed systems Programs and Features.
- A vulnerability exists because Windows Defender warns that the download of the ESChatPCClientSetup.exe file may be harmful as the publisher is unknown due to the executable being unsigned. To remediate, an administrator shall contact the vendor to request a hash to use to verify the validity of the downloaded installer file as well as the installed executable and ensure that these files are validated before use.
|
|
