MOVEit Transfer

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:	MOVEit Transfer is an on-premises solution that supports the exchange of files and data between servers, systems, and applications within and between organizations, as well as between groups and individuals using a common shared folder and a simple browser for user access. MOVEit Transfer is designed to support the ease of access and secure file transfer that meets or exceeds an organization`s security and compliance requirements. Note: This technology was sold to Progress by Ipswitch in 2019. This product can be configured to log transfers in a tamper-evident Microsoft Structured Query Language (SQL) Server database or MySQL Database. Data can be secured in transit and at rest with Federal Information Processing Standards (FIPS) 140-2 validated Advanced Encryption Standard (AES)-256 cryptography. 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 v24.7
Decision Date:	07/10/2024 at 12:15:38 UTC
Aliases:	MOVEit Demilitarized Zone (DMZ), MOVEit File Transfer
Introduced By:	TRM Request
Vendor Name:	Progress

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
7.0
7.5	11/07/2012
8.0	08/28/2013
8.1	08/30/2014
8.2	11/10/2015
8.3	03/24/2016
2017 (9.0.x)
2018 SP1 (10.x)	05/25/2018
2019 (11.0)	03/19/2019
2021 (13.x)	04/28/2021	11/09/2023	05/10/2024
2022.x	04/28/2022	11/09/2024	05/10/2025
2023.x	05/09/2023	10/31/2025	05/01/2026
2023.0.11+
2023.1.6+
2024.x	05/22/2024
2024.0.2+	06/11/2024

Current Decision Matrix (07/03/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

CY2019

CY2020

CY2021

Future>

Release

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

7.5

Divest
[5, 6, 7, 8]

Unapproved

8.0

Divest
[5, 6, 7, 8]

Unapproved

8.1

Divest
[5, 6, 7, 8]

Unapproved

8.2

Divest
[5, 6, 7, 8]

Unapproved

8.3

Approved w/Constraints
[5, 6, 7, 8]

Divest
[5, 6, 7, 8]

Unapproved

2017 (9.0.x)

Approved w/Constraints
[5, 6, 7, 8]

Divest
[5, 6, 7, 9]

Unapproved

2018 SP1 (10.x)

Approved w/Constraints
[5, 6, 7, 8]

Divest
[5, 6, 7, 9]

Unapproved

2019 (11.0)

Unapproved

Approved w/Constraints
[5, 6, 7, 9]

Approved w/Constraints
[7, 9, 10, 11]

2021 (13.x)

Unapproved

2022.x

Unapproved

2023.x

Unapproved

2023.0.11+

Unapproved

2023.1.6+

Unapproved

2024.x

Unapproved

2024.0.2+

Unapproved

Decision Constraints


[1]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period.

[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]	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]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. This technology supports the use of data transfer via FTP, SSH and SFTP. Data transfer must occur over SSH or SFTP.

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

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

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

[8]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. This product can be configured with a MySQL Database, which currently has TRM constraints due to its many known security issues. If MySQL is selected for use with this product, these factors must be considered especially when an instance of this product will be considered a Moderate or High-Risk system (Refer to MySQL Database TRM entry for more details).

[9]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. This technology must use the latest version of Java Runtime Environment (JRE) - Oracle. Users must ensure that Firefox, Google Chrome, Microsoft .NET Framework, Microsoft Internet Explorer (IE), Microsoft Internet Information Services (IIS), Microsoft Structured Query Language (SQL) Server, and Safari 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 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).

Note:

At the time of writing, version 2024.0.2 is the most current version, released 06/11/2024.

Due to security vulnerabilities, users are permitted to use minor releases and patches X.X and later as identified by the ‘+’ versioning.

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
MOVEit DMZ File Transfer Protocol (FTP) Server	The MOVEit DMZ File Transfer Protocol (FTP) server provides both FTP over Secure Socket Layer (SSL) and insecure (regular) FTP services. SSL client certificate support is also available. FTP access is provided to the same underlying folder and file structure made available through MOVEit DMZ`s Secure Shell (SSH) and the Web Interface.
MOVEit DMZ Secure Shell (SSH) Server	MOVEit DMZ Secure Shell (SSH) Server provides both File Transfer Protocol (FTP) over SSH and Secure Copy (SCP2) services. SSH access is provided to the same underlying folder and file structure made available through MOVEit DMZ`s SSH and Web Interface. SSH telnet access is NOT provided by this server.
MOVEit EZ	MOVEit EZ is a Windows-based file transfer client that automatically transfers files on a scheduled basis to an from MOVEit Transfer and MOVEit Cloud.

VA Categories View the VA Categorization Framework

Domain Area	Category	Customer Guidance	Category Locked By ELT Date
Collaboration and Electronic Workplace Productivity Software	Miscellaneous Productivity Tools and Utilities

Operating Systems Supported by the Technology

Windows Server - Approved w/Constraints

Technologies/Standards Relationships

Runtime Dependencies:

Java Runtime Environment (JRE) - Oracle
Microsoft .NET Framework
Microsoft Edge. - (required for some configurations)
Microsoft Internet Information Services (IIS)
Microsoft Structured Query Language (SQL) Server - (required for some configurations)
My Structured Query Language (MySQL) Database - Commercial Editions - (required for some configurations)
Safari - (required for some configurations)

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

This vendor stated that this technology is Federal Information Processing Standard (FIPS) 140-2 compliant.
At the time of writing, there are a limited number of TRM options providing this functionality. The addition of this technology will provide end users with multiple viable options.
This is a well-documented technology.
This technology supports Multi-Factor Authentication for improved access control.

Adoption Risks

The technology requires the purchase of licenses from vendor, which could potentially lead to vendor lock-in.
This technology can integrate with and alter database technologies.
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 product can be configured with a MySQL Commercial Edition Database, which currently has TRM constraints limiting its use to Red Hat Enterprise Linux (RHEL) only due to its many known security issues on other platforms.
There are Threat & Assessment Analysis Portal (TAAP) bulletins associated with this technology.
There are known Common Vulnerabilities and Exposures (CVEs) associated with this technology. Please see <a href = "https://nvd.NIST.gov/vuln/search" target="_blank">https://nvd.NIST.gov/vuln/search</a> for more details.
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 has a free trial period, which carries the potential for the disruption of service delivery and inaccurate financial planning.
This technology relies on Java Runtime Environment (JRE) - Oracle, which has a rapid release and update schedule.
This technology can potentially use Secure Sockets Layer (SSL), an unapproved protocol.
This technology can potentially use File Transfer Protocol (FTP), an unapproved protocol.

Architectural Benefits

This technology supports AES Encryption. (Ensure that Advanced Encryption Standard is under Supported Standards in Category tab)
This technology is compatible with virtual machines, therefore consistent with the enterprise Server Virtualize First Policy (VAIQ 7266972 08-27-2012). (Add Virtualization and Consolidation of Servers (Server Virtualize First) to Supported Standards)
This technology supports encrypted transfer over Secure File Transfer Protocol (SFTP) and Secure Sockets Layer (SSL) protocols and uses Federal Information Processing Standards (FIPS) 140-2 validated Advanced Encryption Standard (AES) cryptography.

Architectural Risks

This technology is not portable as it runs only on Windows platforms.
This technology does not use a VA-preferred database to store data.

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 (07/03/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 (07/03/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