Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 25.4

SmartSync Pro

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:	SmartSync Pro is an all-inclusive backup and synchronization solution, intended for broad range of individual and corporate PC users. SmartSync Pro is a universal full-featured solution to back up and synchronize data to the local drive, Universal Serial Bus (USB), Compact Disk/ Digital Video Disc (CD/DVD), Network-Attached Storage (NAS), network volumes, File Transfer Protocol (FTP), Web Distributed Authoring and Versioning (WebDAV), Amazon Simple Storage Service (Amazon S3), Google Drive, DropBox and other cloud services. 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 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.
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.10
Decision Date:	10/31/2024 at 16:35:39 UTC
Introduced By:	TRM Request
Vendor Name:	SmartSync Software

Vendor Release Information

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

You must be logged into the RSAA website prior to clicking the Attestation URLs or the URLs won't open.

Major versions and minor versions of that Major released on or after 09/14/2022 are NOT EXEMPT. Major Versions released before 09/14/2022 are EXEMPT as well as minor versions of that Major regardless of release date.

Version	Release Date	Vendor End of Life Date	Vendor Desupport Date
7.x	01/11/2023
8.x	01/18/2024

Current Decision Matrix (10/29/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 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	Authorized w/ Constraints (POA&M): 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	Authorized w/ Constraints (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 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	Authorized w/ Constraints (PLANNING/EVALUATION): 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 Authorized w/ Constraints (POA&M).

<Past

CY2024

CY2025

CY2026

Future>

Release

7.x

DIVEST
[4, 7, 11, 12, 13, 14, 15, 16]

Unapproved

Authorized w/ Constraints (POA&M)

8.x

Unapproved

Authorized w/ Constraints
[4, 7, 11, 12, 13, 14, 15, 16]

Note:

At the time of writing, version 8.0 is the most current version, released 01/18/2024.

Decision Constraints


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

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

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

[12]	In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004 , VA Directive 6517, and VA Directive 6513. The local ISSO (Information System Security Officer) can advise on the ESCCB review process.

[13]	Users must not utilize the none of the following services: Google Drive, DropBox, and Microsoft OneDrive. This is because none of these services are authorized to store VA information and patient data. 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. If free trialware is utilized, the software must be purchased or removed at the end of the trial period. Users should not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM. Users should not utilize the File Transfer Protocol (FTP), as it is unapproved for use on the TRM. Per the Initial Product Review, users must abide by the following constraints: System owners should deploy FIPS 140-2 (or its successor) certified solution to ensure VA sensitive data containing PII/PHI is protected. Due to potential information security risks, SaaS/PaaS solutions must complete the Veterans-Focused Integration Process Request (VIPR) process where a collaborative effort between Demand Management (DM), Enterprise Program Management Office Information Assurance (EPMO IA), Digital Transformation Center (DTC), Enterprise Cloud Solutions Office (ECSO), Chief Technology Officer (CTO), and stakeholders determines the SaaS/PaaS category during the Discovery Phase. All SaaS and Non-AWS or Azure (VAEC) PaaS assets are routed to EPMO IA for Analysis and Approval to Operate (ATO) with technical oversight, acquisition, production, and sustainment provided by DTC. SSL is no longer considered a secure connection and should be replaced by TLS v1.2 or higher. System owners should ensure TLS is being used instead of the default SSL protocol. The product should be configured to use Secure File Transfer Protocol (SFTP) as this is the authorized solution in the VA Technical Reference Model. SmartSync Pro shall be configured to meet minimum password-based authentication standards per VA Knowledge Service Control IA-5(1). VA currently is standardized to centrally control and enforce security policies regarding the use of removable devices (e.g., USB flash drives) and media (e.g., DVDs/CDs) to prevent data loss and theft, thwart malware intrusion, and protect data. Care must be taken to ensure that if external Flash/USB drive or CD/DVD is to be used for backup, only devices listed on the FIPS 140-2 Validated Removable Storage Device List shall be used.

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

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

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
Platforms and Storage Storage	Long Term Backup

Operating Systems Supported by the Technology

Windows Client - Authorized w/ Constraints
Windows Server - Authorized w/ Constraints

Technologies/Standards Relationships

Runtime Dependencies:

No runtime dependencies have been identified.

Optional Dependencies:

No optional dependencies have been identified.

Comparable Technologies:

FreeFileSync - Authorized w/ Constraints

Companion Technologies/Supported Standards:

Secure File Transfer Protocol (SFTP) - Authorized w/ Constraints
Secure Sockets Layer (SSL) - Authorized w/ Constraints (POA&M)

General Analysis

Adoption Benefits

This is a well-documented technology.
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 technology may improve productivity for specific staff whose responsibilities include syncing files and data across multiple systems.
This technology utilizes built-in Authentication and Authorization (A&A) capabilities.
There are minimal other TRM-authorized technologies that provide the same functionality.

Adoption Risks

This technology is available as freeware. If commercial support is not purchased, the product will be without clearly defined support options which may result in suboptimal enterprise level support
This technology involves the use Universal Serial Bus (USB) connections and proper security precautions must be taken when used.
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.
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 may transmit data over the VA Wide Area Network (WAN).
This technology may utilize external data connections.
Although this vendor utilizes Federal Information Processing (FIPS) 140-2 encryption, there is no indication based on the vendor documentation or the Cryptographic Module Validation Program (CMVP) that this technology is Federal Information Processing Standards (FIPS) 140-2 certified.
The product can back up and synchronize data to cloud services Amazon S3, Google Drive, DropBox, and others.
This technology can potentially use Secure Sockets Layer (SSL), an unapproved protocol.
The product uses FTP over Secure Socket Layer (SSL) protocol instead of Secure File Transfer Protocol (SFTP) which uses Secure Shell (SSH).
The products password protection must be configurable to meet VA standards for complexity, as defined in VA Handbook 6500 (IA-5).
Data can be backed up and synchronized to external Flash/USB drive or CD/DVD.
This technology can potentially use File Transfer Protocol (FTP), an unapproved protocol.
The product is not Federal Information Processing standards (FIPS) 140-2 (or its successor) certified. It uses AES 256-bit encryption.
The product uses https (SSL) connection for WebDAV. SSL is considered no longer a secure connection and should be replaced by TLS v1.2 or higher.

Architectural Benefits

This technology supports AES Encryption.

Architectural Risks

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

- The information contained on this page is accurate as of the Decision Date (10/31/2024 at 16:35:39 UTC).

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 25.4

General Information

Vendor Release Information

Current Decision Matrix (10/29/2024)

Decision Constraints

References

Technology Components

VA Categories

View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Optional 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 25.4

General Information

Vendor Release Information

Current Decision Matrix (10/29/2024)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Optional Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

EMAIL UPDATES

VA Categories

View the VA Categorization Framework