Splashtop On-Prem

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:	Splashtop On-Prem is an unattended and attended remote access and management utility used to control systems remotely. The computer the user wants to control will need to have the Streamer App installed, while any other computer on the network can access it with the Client App. Note: The vendor`s website may be inaccessible behind the VA firewall. The vendor offers several forms of this technology: Splashtop Enterprise (cloud-based), Business Access, Remote Support, etc. This entry covers solely the On-Prem technology as it is the one implemented on VA systems. This technology was formerly called Splashtop Enterprise On-Premise. 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: http://vaww.eie.va.gov/SysDesign/CS/MT/default.aspx
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 v23.10
Decision Date:	10/23/2023 at 14:32:46 UTC
Aliases:	Splashtop Enterprise On-Premise
Introduced By:	TRM Request
Vendor Name:	Splashtop Inc.

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
3.4.x (Mac/Win)	11/17/2020
3.5.x (Mac/Win)
2.6.x (Linux)	04/30/2020
3.5.x (Linux)

Current Decision Matrix (10/19/2023)

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

CY2021

CY2022

CY2023

Future>

Release

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

3.4.x (Mac/Win)

Approved w/Constraints
[1, 3, 4, 6, 7, 8]

Approved w/Constraints
[1, 6, 9, 10, 11, 12]

Divest
[6, 10, 12, 13, 14, 15]

3.5.x (Mac/Win)

Unapproved

Approved w/Constraints
[6, 10, 12, 13, 14, 15]

2.6.x (Linux)

Approved w/Constraints
[1, 3, 4, 6, 7, 8]

Approved w/Constraints
[1, 6, 9, 10, 11, 12]

Divest
[6, 10, 12, 13, 14, 15]

3.5.x (Linux)

Unapproved

Approved w/Constraints
[6, 10, 12, 13, 14, 15]

Decision Constraints


[1]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. Users must ensure that Google Chrome, Microsoft .NET Framework, and Microsoft Structured Query Language (SQL) Server are implemented within VA-approved baselines. 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. As stated in the security concerns section of this document, the vendor documents the procedure for enabling FIPS modules in its applications but cites the use of modules that are in a “Historical” status to make the configuration FIPS compliant. Splashtop On-Prem is currently not a part of the VA standard baseline configuration. Splashtop On-Prem should only be used when a VA approved tool does not meet the necessary requirements, and the use for more specialized tools are warranted. Unauthorized applications should not be installed or used on the VA network. Web Application Blocked (Restricted URL) The Department of Veterans Affairs (VA) Trusted Internet Connections (TICs) are for official VA use only. Misuse violates VA policy. Based on business justification, exceptions may be permitted. Please open an Incident Ticket via the VA`s ServiceNow ticketing system (https://yourit.va.gov) and assign it to TIC Gateway Operations Team – Assignment Group: IO.NETWORK.NOC.TICGATEWAY. Include a full description of the resource you attempted to access. Attach a screenshot of the entire block page message to the ticket. You can also contact the Enterprise Service Desk (ESD) at 855-673-4357. Include a full description of the resource you attempted to access including the following information: the requestor should contact the VA’s TIC Gateway Operations Team to find out why the site is inaccessible.

[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]	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 approved and the user should take the proper steps to decline those installations.

[4]	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.

[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]	New installations or major expansions of this technology that transmit data over the VA Wide Area Network (WAN) must complete a WAN impact review (yourIT Service Portal:[SNOW Service Requests]) prior to implementation to ensure proper compliance to VA network design and usage requirements.

[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]	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).

[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 VA Handbook 6500.

[10]	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.

[11]	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.

[12]	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).

[13]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. Users must ensure that Google Chrome and Microsoft Structured Query Language (SQL) Server are implemented within VA-approved baselines. 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. As stated in the security concerns section of this document, the vendor documents the procedure for enabling FIPS modules in its applications but cites the use of modules that are in a “Historical” status to make the configuration FIPS compliant. Splashtop On-Prem is currently not a part of the VA standard baseline configuration. Splashtop On-Prem should only be used when a VA approved tool does not meet the necessary requirements, and the use for more specialized tools are warranted. Unauthorized applications should not be installed or used on the VA network. Web Application Blocked (Restricted URL) The Department of Veterans Affairs (VA) Trusted Internet Connections (TICs) are for official VA use only. Misuse violates VA policy. Based on business justification, exceptions may be permitted. Please open an Incident Ticket via the VA`s ServiceNow ticketing system (https://yourit.va.gov) and assign it to TIC Gateway Operations Team – Assignment Group: IO.NETWORK.NOC.TICGATEWAY. Include a full description of the resource you attempted to access. Attach a screenshot of the entire block page message to the ticket. You can also contact the Enterprise Service Desk (ESD) at 855-673-4357. Include a full description of the resource you attempted to access including the following information: the requestor should contact the VA’s TIC Gateway Operations Team to find out why the site is inaccessible.

[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 both VA Handbook 6500 and VA Directive 6500.

[15]	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.

Note:

At the time of writing, version 3.5.8.3 is the most current version for MacOS and Windows, released 06/26/2023. Version 3.5.8.1 is the most current version for Linux, released 09/08/2023.

References

The following reference(s) are associated with this entry:
Type	Name	Source	Description

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
Splashtop Center	This component of Splashtop acts as a hub for connectivity and stores logs and information in a Microsoft SQL Server database. Center can create user accounts and set permissions for each account.
Splashtop Enterprise App (Client App)	The Splashtop Enterprise app makes it possible for users to connect their mobile device(s) to the target streamer/computer remotely.
Splashtop Gateway	Splashtop Gateway web portal is a web-based consol to configure and manage Splashtop On-Prem system.
Splashtop Software Updater	This utility ensures that all software and components of the system are up to date.
Splashtop Streamer	Splashtop Streamer streams audio and video to the mobile device and needs to be installed on all target computers that you want to be available for remote access.

VA Categories View the VA Categorization Framework

Domain Area	Category	Customer Guidance	Category Locked By ELT Date
Systems Management Systems Management Tools	Remote Desktop Management

Operating Systems Supported by the Technology

macOS - Approved w/Constraints
Red Hat Enterprise Linux (RHEL) - Approved w/Constraints
Windows Client - Approved w/Constraints
Windows Server - Approved w/Constraints

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

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 utilizes built-in Authentication and Authorization (A&A) capabilities.

Adoption Risks

Splashtop On-Prem is not FIPS140-2 validated/certified. Vendor documentation states that it can be configured to “enable FIPS modules” but the OpenSSL modules that the documentation says that they are using (OpenSSL FIPS Object Module 2.0, certificate numbers 1747, 2398, and 2473) are all in a “Historical” status stating that “The referenced cryptographic module should not be included by Federal Agencies in new procurements. Agencies may make a risk determination on whether to continue using this module based on their own assessment of where and how it is used.”
Splashtop On-Prem is currently not part of the VA standard baseline configuration.
This technology has a free trial period, which carries the potential for the disruption of service delivery and inaccurate financial planning.
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 may transmit data over the VA Wide Area Network (WAN).
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.
This technology can integrate with and alter database technologies.

Architectural Benefits

This technology can use a VA-preferred database.
This technology is compatible with virtual machines, therefore consistent with the enterprise Server Virtualize First Policy (VAIQ 7266972 08-27-2012).
This technology is able to integrate with Active Directory and allows Single Sign On (SSO) capabilities.
This technology is portable as it runs on multiple TRM-approved operating systems.

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 (10/19/2023)

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

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (10/19/2023)

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

EMAIL UPDATES