Enterprise Secure Chat

General Information

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website:	Go to site
Description:	Enterprise Secure Chat (ESChat) operates on and across all wireless carriers, providing intercarrier interoperability. ESChat can operate as a standalone broadband solution with smartphone and Internet of Things (IoT) devices, or it can be integrated with Project 25 (P25) Inter Radio Frequency Subsystem Interface (ISSI), Digital Mobile Radio (DMR) Air Interface Standard (AIS), or any Land Mobile Radio (LMR) Radio Over Internet Protocol (RoIP). This entry covers the Desktop Edition of this technology and not any mobile versions. Please note that the implementation of mobile technology applications that operate on Mobile Operating Systems must be reviewed and approved by the Mobile Technology and Endpoint Security Engineering Team: https://dvagov.sharepoint.com/sites/OITMT/SitePages/MTHome.aspx The TRM decisions in this entry only apply to technologies and versions owned, operated, managed, patched, and version-controlled by VA. This includes technologies deployed as software installations on VMs within VA-controlled cloud environments (e.g., VA Enterprise Cloud (VAEC)). Cloud services provided by the VAEC, which are listed in the VAEC Service Catalog, and those controlled and managed by an external Cloud Service Provider (i.e., SaaS) are not in the purview of the TRM. For more information on the use of cloud services and cloud-based products within VA, including VA private clouds, please see the Enterprise Cloud Solutions Office (ECSO) Portal at: https://dvagov.sharepoint.com/sites/OITECSO
Technology/Standard Usage Requirements:	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 Security Officer (ISO), 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.
Section 508 Information:	This technology has not been assessed by the Section 508 Office. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. For additional information or assistance regarding Section 508, please contact the Section 508 Office at Section508@va.gov
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v24.5
Decision Date:	05/01/2024 at 19:32:15 UTC
Aliases:	ESChat
Introduced By:	TRM Request
Vendor Name:	ESChat

Vendor Release Information

The Vendor Release table provides the known releases for the TRM Technology, obtained from the vendor (or from the release source).

Version	Release Date	Vendor End of Life Date	Vendor Desupport Date
14.x	03/20/2020

Current Decision Matrix (03/26/2024)

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 Security Officer (ISO), 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 VA IT 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. Any major.minor version that is not listed in the VA Decision Matrix is considered unapproved for use.

Legend:

White	Approved: The technology/standard has been approved for use.
Yellow	Approved 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	Unapproved: 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	Divest: 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 unapproved may be found on the Decision tab for the specific entry.
Black	Prohibited: The technology/standard is not (currently) permitted to be used under any circumstances.
Blue	Planning/Evaluation Constraint: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 approved 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 approved 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.

<Past

CY2028

CY2029

CY2030

Future>

Release

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

14.x

Approved w/Constraints
[1, 2, 3, 4, 5, 6]

Decision Constraints


[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 approved java environments available. See Category tab for details. Users must ensure that Google Chrome, Firefox, and Microsoft Edge are implemented with VA-approved 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 approved 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.

Note:

At the time of writing, version 14.0.989 is the most current version, released 03/20/2024.

References

The following reference(s) are associated with this entry:
Type	Name	Source	Description
*NOTE: Vendor provided information is subject to the accuracy of the manufacturer.

Technology Components

Note: This list may not be complete. No component, listed or unlisted, may be used outside of the technology in which it is released. The usage decision for a component is found in the Decision and Decision Constraints.
Name	Description
No components have been identified for this entry.

VA Categories View the VA Categorization Framework

Domain Area	Category	Customer Guidance	Category Locked By ELT Date
Network and Telecommunications Wireless and Mobile Networks	Radio and Satellite

Operating Systems Supported by the Technology

Windows Client - Approved w/Constraints
Windows Server - Approved w/Constraints

Technologies/Standards Relationships

Runtime Dependencies:

Microsoft Edge. - (required for some configurations)
Open Java Development Kit (OpenJDK) - (required for some configurations)

Comparable Technologies:

No comparable entries have been identified.

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

At the time of writing, no National Institute of Standards and Technology (NIST) vulnerabilities had been reported and no VA Cyber Security Operations Center (CSOC) bulletins had been issued for the latest versions of this technology.
This is a well-documented technology.
This technology may improve productivity for specific staff whose responsibilities include providing intercarrier interoperability.
At the time of writing, this technology provides functionality not available through other approved TRM options.

Adoption Risks

The technology requires the purchase of licenses from vendor, which could potentially lead to vendor lock-in.
The potential exists to store Personally Identifiable Information (PII), Protected Health Information (PHI) and/or VA Sensitive data and proper security standards must be followed in these cases.
Due to the rapid release schedule of this technology, the VA may be unable to update to the most recent patch and may require a deployment model requiring the use of specific versions.
This technology has a free trial period, which carries the potential for the disruption of service delivery and inaccurate financial planning.
This technology involves the use Universal Serial Bus (USB) connections and proper security precautions must be taken when used.
A vulnerability exists because ESChat PC Client for Windows v14.0.989 is not FIPS 140-2 or its successor certified.
A vulnerability exists because Windows Defender blocked the installation of ESChat PC Client for Windows v14.0.989 noting that the publisher was unknown.
A vulnerability exists because ESChat PC Client for Windowsv14.0.989 installs two .exe files without a digital signature. This prevents the verification of the control`s publisher and assurance that it has not been tampered with since being published.
ESChat PC Client for Windows v14.0.989 installs OpenJDK v22.0.0.0 which is Opensource software and is listed as Unapproved on the VA Technical Reference Model (TRM).
A vulnerability exists because the ESChat subscription service is hosted on Amazon AWS or in a private cloud using the customer’s own hardware.
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. Discrepancy between version numbers has been known to cause problems with version control across the enterprise resulting in software being mistakenly removed from systems.
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.

Architectural Benefits

This technology supports AES Encryption.

Architectural Risks

This technology is not portable as it runs only on Windows platforms.
This technology includes cloud-based functionality which has potential information security risks.

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (03/26/2024)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (03/26/2024)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

EMAIL UPDATES