Windows Secure Copy Protocol (WinSCP)

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:	WinSCP is an open source file transfer client for Windows that supports Securer File Transfer Protocol (SFTP), Secure Copy Protocol (SCP) and File Transfer Protocol (FTP).
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 been assessed by the Section 508 Office and found non-conformant. 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. Please see reference tab for more information concerning product versions.
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v24.3
Decision Date:	03/11/2024 at 14:14:25 UTC
Aliases:	network file transfer, WinSCP
Introduced By:	Extended Tool List (ETL)
Vendor Name:	WinSCP

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
4.3.x	02/23/2011
5.1.x	09/24/2012
5.5.x	12/19/2013
5.7.x	02/20/2015
5.9.x	07/22/2016
5.11.x	09/05/2017
5.13.x	12/17/2017
5.15.x	04/11/2019
5.17.x	02/18/2020
5.17.8+	10/15/2020
5.19.x	06/07/2021
5.21.x	06/24/2022
6.1.x	09/19/2023
6.3.x	02/21/2024

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

CY2023

CY2024

CY2025

Future>

Release

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

4.3.x

Unapproved

5.1.x

Unapproved

5.5.x

Unapproved

5.7.x

Unapproved

5.9.x

Unapproved

5.11.x

Unapproved

5.13.x

Unapproved

5.15.x

Unapproved

5.17.x

Unapproved

5.17.8+

Unapproved

5.19.x

Divest
[16, 17, 18, 19, 20]

Divest
[16, 17, 19, 20, 21]

Unapproved

5.21.x

Approved w/Constraints
[16, 17, 18, 19, 20]

Divest
[16, 17, 18, 19, 20]

Divest
[16, 17, 19, 20, 21]

Divest
[16, 17, 19, 20, 21, 22]

Unapproved

6.1.x

Unapproved

Approved w/Constraints
[16, 17, 18, 19, 20]

Approved w/Constraints
[16, 17, 19, 20, 21]

Divest
[16, 17, 19, 20, 21, 22]

Unapproved

6.3.x

Unapproved

Approved w/Constraints
[16, 17, 19, 20, 21, 22]

Decision Constraints


[1]	The FTP features of this software may not be used as the FTP protocol, which is no longer approved for use on the VA network without a waiver. This product must remain patched to the latest available version to mitigate any possible future security vulnerabilities.

[2]	The FTP features of this software may not be used as the FTP protocol is no longer approved for use on the VA network without a waiver.

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

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

[5]	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 ISO can advise on the ESCCB review process.

[6]	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]	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]	The File Transfer Protocol (FTP) features of this software may not be used as the FTP protocol is no longer approved for use on the VA network without a waiver. See memo: Prohibited Use of File Transfer Protocol (FTP) and Telnet Services (VAIQ 7615193).

[9]	The File Transfer Protocol (FTP) features of this software may not be used as the FTP protocol is no longer approved for use on the VA network without a waiver. See memo: Prohibited Use of File Transfer Protocol (FTP) and Telnet Services (VAIQ 7615193). Ensure use of a FIPS 140-2 validated cryptographic module to secure VA sensitive data in applications and devices that utilize WinSCP. When establishing a master password for the WinSCP, ensure that all of the VA password requirements are met with regard to length and complexity. VA Handbook 6500 Control IA-5: Authenticator Management sets a standard of at least 8 non-blank characters. They must contain characters from three (3) of the following four (4) categories: English upper case characters English lower case characters Base-10 digits Non-alphanumeric special characters. Six of the characters must not occur more than once in the password.

[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]	The File Transfer Protocol (FTP) features of this software may not be used as the FTP protocol is no longer approved for use on the VA network without a waiver. See memo: Prohibited Use of File Transfer Protocol (FTP) and Telnet Services (VAIQ 7615193). Ensure use of a FIPS 140-2 validated cryptographic module to secure VA sensitive data in applications and devices that utilize WinSCP When establishing a master password for the WinSCP, ensure that all of the VA password requirements are met with regard to length and complexity. VA Handbook 6500 Control IA-5: Authenticator Management sets a standard of at least 8 non-blank characters. They must contain characters from three (3) of the following four (4) categories: English upper case characters English lower case characters Base-10 digits Non-alphanumeric special characters. Six of the characters must not occur more than once in the password.

[12]	The File Transfer Protocol (FTP) features of this software may not be used as the FTP protocol is no longer approved for use on the VA network without a waiver. See memo: Prohibited Use of File Transfer Protocol (FTP) and Telnet Services (VAIQ 7615193). Ensure use of a Federal Information Processing Standard (FIPS) 140-2 validated cryptographic module to secure VA sensitive data in applications and devices that utilize WinSCP When establishing a master password for the WinSCP, ensure that all of the VA password requirements are met with regard to length and complexity. VA Handbook 6500 Control IA-5: Authenticator Management sets a standard of at least eight (8) non-blank characters. They must contain characters from three (3) of the following four (4) categories: English upper case characters English lower case characters Base-10 digits Non-alphanumeric special characters. Six of the characters must not occur more than once in the password.

[13]	The File Transfer Protocol (FTP) features of this software must not be used as the FTP protocol is prohibited for use on the VA network. (For further information see: VA Policy Memo VAIQ 7615193 on Prohibited Use of File Transfer Protocol (FTP) and Telnet Services). Ensure use of a Federal Information Processing Standard (FIPS) 140-2 validated cryptographic module to secure VA sensitive data in applications and devices that utilize WinSCP When establishing a master password for the WinSCP, ensure that all of the VA password requirements are met with regard to length and complexity. VA Handbook 6500 Control IA-5: Authenticator Management sets a standard of at least eight (8) non-blank characters. They must contain characters from three (3) of the following four (4) categories: English upper case characters English lower case characters Base-10 digits Non-alphanumeric special characters. Six of the characters must not occur more than once in the password.

[14]	Per the Initial Product Review, users must abide by the following constraints: The File Transfer Protocol (FTP) features of this software must not be used as the FTP protocol is prohibited for use on the VA network. (For further information see: VA Policy Memo VAIQ 7615193 on Prohibited Use of File Transfer Protocol (FTP) and Telnet Services). Ensure use of a FIPS 140-2 validated cryptographic module to secure VA sensitive data in applications and devices that utilize WinSCP. When establishing a master password for the WinSCP, ensure that VA password requirements are met with regard to length and complexity. Ensure that user passwords meet the mandate required by the VA Handbook 6500. It is advised the device to be tested to meet the minimum password-based complexity for VA as follows: Passwords must contain at least: fourteen (14) alpha-numeric characters one upper and lower case letter one special character (ex: ,!@#). The product must remain patched, updated and operated in accordance with Federal and Department security and privacy policies and guidelines.

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

[16]	This technology has received one or more VA security bulletins that provide specific guidance on vulnerability patching and mitigation. It is the responsibility of VA system owners to ensure that the appropriate mitigations are taken to address all known and future discovered vulnerabilities with this product. See the Reference tab for more information on security bulletins related to this product.

[17]	Per the Initial Product Review, users must abide by the following constraints: Ensure use of a FIPS 140-2 certified cryptographic module to secure VA sensitive data in applications and devices that utilize WinSCP When establishing a master password for the WinSCP, ensure that VA password requirements are met with regard to length and complexity. Ensure that user passwords meet the mandate required by the VA Handbook 6500. It is advised the device to be tested to meet the minimum password-based complexity for VA as follows: Password must contain at least 14 non-blank characters. Password must contain at least fourteen (14) alpha-numeric characters with upper and lower case, numbers, and special characters (e.g. ,!@#). The product must remain patched, updated and operated in accordance with Federal and Department security and privacy policies and guidelines. The File Transfer Protocol (FTP) features of this software must not be used as the FTP protocol is prohibited for use on the VA network. (For further information see: VA Policy Memo VAIQ 7615193 on Prohibited Use of File Transfer Protocol (FTP) and Telnet Services)

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

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

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

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

[22]	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 6.3.1 is the most current version, released 02/21/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
Platforms and Storage Operating Systems	OS Tools

Open Source

This entry is available as an open source technology.

Operating Systems Supported by the Technology

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

Technologies/Standards Relationships

Runtime Dependencies:

No runtime dependencies have been identified.

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

This is a well-documented technology.
This technology is available at no cost through open source licensing and supports VA`s open source initiative.
This technology may improve productivity for specific staff whose responsibilities include transfer files between a local and remote computer.

Adoption Risks

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 potentially use File Transfer Protocol (FTP), an unapproved protocol.
There are known Common Vulnerabilities and Exposures (CVEs) associated with this technology. Please see https://nvd.NIST.gov/vuln/search for more details.
WinSCP can protect stored passwords (using AES cipher), but its master password must be configured and enabled. VA has stringent requirements for password complexity that must be met.
There are published vulnerabilities that affect older versions up to 5.17.10 of this software.
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.
There are Threat & Assessment Analysis Portal (TAAP) bulletins associated with this technology.
WinSCP does not have a Federal Information Processing Standards (FIPS) 140-2 certification; however it supports secure communications over SSH-1 and SSH-2 and may use other FIPS 140-2 certified technologies.
As open-source software, this product may be left without clearly defined support options which may result in suboptimal enterprise level support.

Architectural Benefits

This technology is compatible with multiple other Technical Reference Model (TRM) technologies and standards used by the organization.

Architectural Risks

This technology is not portable as it runs only on Windows platforms.

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/05/2024)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Open Source

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/05/2024)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Open Source

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