GNU Privacy Guard (GnuPG)

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:	GNU Privacy Guard (GnuPG) is a free implementation of the OpenPGP (Pretty Good Privacy) standard as defined by Request for Comment (RFC) 4880. This technology provides command-line utilities to encrypt and/or sign data and communications. Additionally, the technology provides encryption key management, access to public key directories, and authentication using Secure Shell. This technology also provides support for Secure/Multipurpose Internet Mail Extensions (S/MIME).
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.12
Decision Date:	12/21/2023 at 12:33:37 UTC
Aliases:	GPG
Introduced By:	TRM Request
Vendor Name:	GnuPG.org

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
1.4.x	10/04/2013
2.0.22	10/04/2013
2.0.28	06/02/2015
2.0.30	03/31/2016
2.1.x	05/15/2017
2.2.x	07/28/2017
2.3.x	04/07/2021
2.4.x	12/16/2022

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

CY2017

CY2018

CY2019

Future>

Release

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

1.4.x

Unapproved

2.0.22

Divest
[3, 4, 5, 6]

Divest
[3, 4, 5, 7]

Divest
[4, 5, 7, 8]

Unapproved

2.0.28

Approved w/Constraints
[3, 4, 5, 6]

Approved w/Constraints
[3, 4, 5, 7]

Divest
[3, 4, 5, 7]

Divest
[4, 5, 7, 8]

Divest
[5, 7, 8]

Unapproved

2.0.30

Approved w/Constraints
[3, 4, 5, 6]

Approved w/Constraints
[3, 4, 5, 7]

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

Approved w/Constraints
[5, 7, 8]

Divest
[5, 7, 8]

Unapproved

2.1.x

Unapproved

Approved w/Constraints
[3, 4, 5, 7]

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

Approved w/Constraints
[5, 7, 8]

Divest
[5, 7, 8]

2.2.x

Unapproved

Approved w/Constraints
[5, 7, 8]

2.3.x

Unapproved

2.4.x

Unapproved

Decision Constraints


[1]	Use of this technology is restricted to projects which require interoperability with external VA partners to encrypt/decrypt data files. Projects may not use the email encryption, decryption,or message signing functionality. Further, projects must use version 2.0.22 or greater of this technology and ensure that all patches and updates are applied in accordance with VA Handbook 6500 policy to mitigate known and future security vulnerabilities, or additional mitigating controls must be documented in an approved System Security Plan (SSP). Additionally, projects using this technology must meet Veterans Affairs (VA) Directive 6500 and implement Federal Information Processing Standards (FIPS 199) for all laptop devices and National Institute of Standards and Technology Special Publication 800-53 for all desktop devices when VA sensitive information is involved.

[2]	Use of this technology is restricted to projects which require interoperability with external VA partners to encrypt/decrypt data files. Projects may not use the email encryption, decryption,or message signing functionality. Further, projects must use version 2.0.22 or greater of this technology.

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

[6]	Use of this technology is restricted to projects which require interoperability with external VA partners to encrypt and decrypt data files. Projects may not use the email encryption, decryption, or message signing functionality. Further, projects must use version 2.0.22 or greater of this technology.

[7]	Use of this technology is restricted to projects which require interoperability with external VA partners to encrypt and decrypt data files. Projects must not use the email encryption, decryption, or message signing functionality. Further, projects must use version 2.0.22 or greater of this technology.

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

Note:

At the time of writing, version 2.4.3 is the most current version, released 07/04/2023.

References

The following reference(s) are associated with this entry:
Type	Name	Source	Description
Vendor Provided*	Release notes for GNU Privacy Guard (GnuPG)		This links points to the GNU Privacy Guard (GnuPG) release notes.
*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
Security Network Security	Encryption

Open Source

This entry is available as an open source technology.

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:

No runtime dependencies have been identified.

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

This technology will increase the security posture of the Department by encrypting signed data.
This technology is available at no cost through open source licensing and supports VA`s open source initiative.
This technology is well-documented.

Adoption Risks

There are known Common Vulnerabilities and Exposures (CVEs) associated with this technology. Please see https://nvd.nist.gov/vuln/search for more details.
There is no indication based on either the vendor documentation or the Cryptographic Module Validation Program (CMVP) that this technology is Federal Information Processing Standard (FIPS) 140-2 compliant.
This technology can potentially use Data Encryption Standard (DES), an unapproved technology.
As open-source software, this product may be left without clearly defined support options which may result in suboptimal enterprise level support.
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.
There are other approved solutions that provide similar functionality available on the TRM. The use of several similar solutions may increase organization requirements for support and maintenance.
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.

Architectural Benefits

This technology is portable as it runs on multiple TRM-approved operating systems.
This technology supports AES Encryption.

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

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

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (12/19/2023)

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

EMAIL UPDATES