Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 24.7

PuTTY-CAC (Common Access Card)

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:	PuTTY-CAC (Common Access Card) is a Windows terminal emulation technology that supports the Secure Shell (SSH) protocol to access remote systems. This is a modified version of PuTTY SC (Smart Card), which supports SmartCard authentication such as the Department of Defense Common Access Card (DoD CAC) and other x.509 certificates. PuTTY-CAC allows system owners to administer and manage network resources without being physically present at the device location. To differentiate between PuTTY and PuTTY-CAC, the putty.exe file is included as a part of PuTTY-CAC. It also includes a configuration item under Secure Shell (SSH) called Microsoft Crypto Application Programming Interface (CAPI).
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 19:17:21 UTC
Aliases:	terminal emulator
Introduced By:	TRM Request
Vendor Name:	Dan Risacher

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
0.62	09/18/2012
0.65	08/14/2015
0.66	12/29/2015
0.68	03/20/2017
0.69	04/29/2017
0.70	04/03/2018
0.71	03/21/2019
0.73	04/02/2020
0.74	06/30/2020
0.75	05/11/2021
0.76	07/17/2021
0.77	06/23/2022
0.78	11/06/2022
0.79	08/26/2023
0.80	12/18/2023
0.81	04/15/2024

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

CY2022

CY2023

CY2024

Future>

Release

0.62

Prohibited

Unapproved

0.65

Unapproved

0.66

Unapproved

0.68

Unapproved

0.69

Unapproved

0.70

Unapproved

0.71

Unapproved

0.73

Unapproved

0.74

Divest
[4, 7, 15, 17]

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

Unapproved

0.75

Approved w/Constraints
[4, 7, 15, 17]

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

Divest
[18, 19, 20, 21, 22]

Divest
[19, 20, 21, 22, 23]

Divest
[19, 20, 21, 22, 23, 24]

Unapproved

0.76

Approved w/Constraints
[4, 7, 15, 17]

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

Divest
[18, 19, 20, 21, 22]

Divest
[19, 20, 21, 22, 23]

Divest
[19, 20, 21, 22, 23, 24]

Unapproved

0.77

Unapproved

Approved w/Constraints
[4, 7, 15, 17]

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

Divest
[18, 19, 20, 21, 22]

Divest
[19, 20, 21, 22, 23]

Divest
[19, 20, 21, 22, 23, 24]

Unapproved

0.78

Unapproved

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

Divest
[18, 19, 20, 21, 22]

Divest
[19, 20, 21, 22, 23]

Divest
[19, 20, 21, 22, 23, 24]

0.79

Unapproved

Approved w/Constraints
[18, 19, 20, 21, 22]

Approved w/Constraints
[19, 20, 21, 22, 23]

Approved w/Constraints
[19, 20, 21, 22, 23, 24]

Divest
[19, 20, 21, 22, 23, 24]

0.80

Unapproved

0.81

Unapproved

Approved w/Constraints
[19, 20, 21, 22, 23, 24]

Decision Constraints


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

[2]	Enterprise Security Solutions Services (ESSS) conducted a pre-assessment and security requirements verification of PuTTY-CAC. It is advised that if this product is used within the Department of Veterans Affairs (VA), the following constraints be applied: Terminal emulation software is used to access and manage IT resources such as servers and networking devices which contain sensitive information. All internal servers will use FIPS 140-2 (or its successor) validated server certificates for inter-server and server-to-user communications as stated in VA Handbook 6500, IA-3: Device Identification and Authentication control. In the event this product is used within VA due to specific mission requirement, a Risk Based Decision (RBD) must be submitted through established VA process for approval. System owners should consider conducting a security review and audit of the PuTTY-CAC source code to ensure that otherwise unknown vulnerabilities are addressed or mitigated, if any exist. In addition, system owners should make every effort to use Attachmate, the VA standard emulation software, if technically possible.

[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]	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]	Enterprise Security Solutions Services (ESSS) conducted a pre-assessment and security requirements verification of PuTTY-CAC. It is advised that if this product is used within the Department of Veterans Affairs (VA), the following constraints be applied: Terminal emulation software is used to access and manage IT resources such as servers and networking devices which contain sensitive information. All internal servers will use Federal Information Processing Standard (FIPS) 140-2 (or its successor) validated server certificates for inter-server and server-to-user communications as stated in VA Handbook 6500, IA-3: Device Identification and Authentication control. In the event this product is used within VA due to specific mission requirement, a Risk Based Decision (RBD) must be submitted through established VA process for approval. System owners must conduct a security review and audit of the PuTTY-CAC source code to ensure that otherwise unknown vulnerabilities are addressed or mitigated, if any exist. In addition, system owners must make every effort to use Attachmate, the VA standard emulation software, if technically possible.

[6]	Enterprise Security Solutions Services (ESSS) conducted a pre-assessment and security requirements verification of PuTTY-CAC. It is advised that if this product is used within the Department of Veterans Affairs (VA), the following constraints be applied: Terminal emulation software is used to access and manage IT resources such as servers and networking devices which contain sensitive information. All internal servers will use Federal Information Processing Standard (FIPS) 140-2 (or its successor) validated server certificates for inter-server and server-to-user communications as stated in VA Handbook 6500, IA-3: Device Identification and Authentication control. System owners must conduct a security review and audit of the PuTTY-CAC source code to ensure that otherwise unknown vulnerabilities are addressed or mitigated, if any exist. In addition, system owners must make every effort to use Attachmate, the VA standard emulation software, if technically possible.

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

[8]	This technology should only be used when required by a Veterans Affairs (VA) business partner for an approved VA Project. Use of this technology must comply with ESCCB requirements which include: Signed Interconnection Agreements/Memorandum of Understanding agreements (MOU/ISA) with each external business partner, compliance with VA Handbook 6500, and must implement appropriate National Institute of Standards and Technology (NIST) Federal Information Processing Standards (FIPS) requirements for all devices interacting with this technology. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. As of January 27th, 2017, Risk-based Decisions (RBD) will be handled per VAIQ # 7769667. 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 and ensure privacy of information compliance protections are in place.

[9]	Version .74 is approved only for test and evaluation while the required baseline and/or hardening guide and other steps that are required for full production use in the Initial Product Review (IPR) are completed. More information follows and is in the referenced IPR. In collaboration with Information Security Operations and Services (ITOPS), the ISSE team recommends the following to address risks associated with PuTTY-CAC and are needed for full TRM production approval: • Development of a clear policy on the use of open source software should be prioritized to rein in issues related to open source vulnerabilities management or incompatible licenses. • Ownership for the review, version management, configuration, and usage tracking of the software needs to be identified. • Responsible entity will ensure only approved packages are installed, and will collaborate with other teams to address any other security related issues. • Hardening Guide/Instructions or training on the proper installation and configuration of PuTTY-CAC should be developed and maintained. • Keep a complete and accurate inventory list of PuTTY-CAC software and provide an authoritative source for downloading approved versions. • Restrict requests to whitelist open source software(s) in TRM to authorized personnel with a business justification for its use within the enterprise. • Ensure patches to PuTTY are managed in accordance with VA enterprise patch management processes. • Prohibit the use of the traditional PuTTY which does not use PIV keys.

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

[12]	Configuration baseline and deployment standards for this technology that are maintained by Infrastructure Operations in ITOPS must be followed and adhered to unless an appropriate waiver is granted. See the reference section for more information. Users must only use the versions that have been approved via the IPR or Baseline. Any version prior to the latest approved version is unapproved and should not be used.

[13]	This technology should only be used when required by a Veterans Affairs (VA) business partner for an approved VA Project. Use of this technology must comply with ESCCB requirements which include: Signed Interconnection Agreements/Memorandum of Understanding agreements (MOU/ISA) with each external business partner, compliance with VA Handbook 6500, and must implement appropriate National Institute of Standards and Technology (NIST) Federal Information Processing Standards (FIPS) requirements for all devices interacting with this technology. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. As of January 27th, 2017, Risk-based Decisions (RBD) will be handled per VAIQ # 7769667. 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 and ensure privacy of information compliance protections are in place.

[14]	This technology should only be used when required by a Veterans Affairs (VA) business partner for an approved VA Project. Use of this technology must comply with ESCCB requirements which include: Signed Interconnection Agreements/Memorandum of Understanding agreements (MOU/ISA) with each external business partner, compliance with VA Handbook 6500, and must implement appropriate National Institute of Standards and Technology (NIST) Federal Information Processing Standards (FIPS) requirements for all devices interacting with this technology. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. As of January 27th, 2017, Risk-based Decisions (RBD) will be handled per VAIQ # 7769667. 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 and ensure privacy of information compliance protections are in place.

[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]	Configuration baseline and deployment standards for this technology that are maintained by Infrastructure Operations in ITOPS must be followed and adhered to unless an appropriate waiver is granted. See the reference section for more information. Only the versions that have been approved via the IPR or Hardening Guide shall be used. See the reference section for information.

[17]	Per the Initial Product Review, users must abide by the following constraints: PuTTY-CAC will require use of FIPS 140-2 (or its successor) certified encryption for network communication where applicable Solution Delivery Business Systems Engineering has created a hardening guide for PuTTY-CAC and must be used to configure the product. https://vaww.vashare.oit.va.gov/sites/itops/svcs/sma/BCM/Supporting_Documents/Putty-CAC%20Security%20Hardening%20Guide.pdf#search=putty PuTTY-CAC is an open source software which may not include vendor support. It is imperative that the product be obtained from trusted sources. This product must remain patched and operated in accordance with Federal and Department security and privacy policies and guidelines.

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

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

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

[22]	Per the Initial Product Review, users must abide by the following constraints: . PuTTY-CAC will require use of FIPS 140-2 (or its successor) certifiedencryption for network communication where applicable. Solution Delivery Business Systems Engineering has created a hardening guide for PuTTY-CAC and must be used to configure the product. https://dvagov.sharepoint.com/sites/OITBCM/supporting_documents/putty-cac%20security%20hardening%20guide.pdf#search=putty PuTTY-CAC must be included on the list of applications for continuous monitoring for published vulnerabilities, updates, and patches. ISSO’s and administrators must monitor the CVE details website for any new security vulnerabilities. PuTTY-CAC is an open-source software which may not include vendor support. It is imperative that the product be obtained from trusted sources.

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

[24]	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 0.81 is the most current version, released 04/15/2024.

A standard configuration of this technology was developed by the DDE team. At the time of writing, the standard version is 0.79.0.0 and version 0.81.0 is under testing and evaluation for four weeks from 07/09/2024..

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
Microsoft Crypto Application Programming Interface (CAPI)	The Microsoft Windows platform specific Cryptographic Application Programming Interface (also known variously as CryptoAPI, Microsoft Cryptography API, MS-CAPI or simply CAPI) is an application programming interface included with Microsoft Windows operating systems that provides services to enable developers to secure Windows-based applications using cryptography


Application Technology Development Tools	Software Change and Configuration Management Tools

- The information contained on this page is accurate as of the Decision Date (07/10/2024 at 19:17:21 UTC).

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/09/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 Risks

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

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

EMAIL UPDATES