Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 24.11

OpenSC (Smart 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:	OpenSC (Smart Card) provides a set of libraries and utilities to work with smart cards. Its main focus is on cards that support cryptographic operations, and facilitate their use in security applications such as authentication, mail encryption and digital signatures. OpenSC implements the standard Application programming interfaces to smart cards, such as PKCS#11 Application programming interface, Windows Smart Card Minidriver and macOS Tokend.
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.9
Decision Date:	09/16/2024 at 14:58:55 UTC
Introduced By:	TRM Request
Vendor Name:	OpenSC (Smart Card)

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.

Version	Release Date	Vendor End of Life Date	Vendor Desupport Date
0.19	09/13/2018
0.20	12/29/2019
0.21.x	11/24/2020
0.22.x	08/10/2021
0.23.x	11/29/2022
0.24.x	12/13/2023
0.25.x	04/05/2024

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

CY2023

CY2024

CY2025

Future>

Release

0.19

Unapproved

Authorized w/ Constraints (POA&M)

0.20

DIVEST
[7, 8, 9, 10]

DIVEST
[7, 9, 10, 11]

Unapproved

Authorized w/ Constraints (POA&M)

0.21.x

DIVEST
[7, 8, 9, 10]

DIVEST
[7, 9, 10, 11]

Unapproved

Authorized w/ Constraints (POA&M)

0.22.x

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

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

DIVEST
[9, 10, 11, 12, 13]

Authorized w/ Constraints (DIVEST)
[9, 10, 11, 12, 13]

0.23.x

Unapproved

DIVEST
[9, 10, 11, 12, 13]

Authorized w/ Constraints (DIVEST)
[9, 10, 11, 12, 13]

0.24.x

Unapproved

DIVEST
[9, 10, 11, 12, 13]

Authorized w/ Constraints (DIVEST)
[9, 10, 11, 12, 13]

0.25.x

Unapproved

Approved w/Constraints
[9, 10, 11, 12, 13]

Authorized w/ Constraints
[9, 10, 11, 12, 13]

Decision Constraints


[1]	Users should ensure that they are using the VA-authorized version of OpenSSL (v1.0.2o) when utilizing this technology.

[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]	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 authorized and the user should take the proper steps to decline those installations.

[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 ensure that they are using the VA-authorized version of OpenSSL (v1.0.2o) when utilizing this technology. Per the Initial Product Review, users must abide by the following constraints: OpenSC must be run on VA standard desktops as it relies on the underlying operating system for encryption. The VA requires support for all software used on the VA network. Vendor or third-party support at an enterprise level is not free and must be acquired for any open source product to be deployed on the VA network. The OpenSC community has a mailing list as their main form of support. Per community: “But if you are using OpenSC as part of some other product, for example Red Hat Enterprise Linux, we as a Red Hat are able to provide commercial support for OpenSC deployments in RHEL. Similarly if you are using some particular hardware (ex. Nitrokey), they have engineers who are able to offer commercial support.” System administrators must ensure that the latest stable version of OpenSC is used. OpenSC must also be included in the list of continuously monitored software for vulnerabilities, patches, and upgrades.

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

[7]	Users must not use OpenVPN with this technology as it is prohibited for use at this time. Users must not use PuTTY or TrueCrypt with this technology as they are unapproved for use at this time. Users must ensure that Firefox and Google Chrome are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) Users must utilize authorized internet browsers, as Microsoft Internet Explorer has reached End of Life status. See Category Tab for details. Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM. This technology must use the latest TRM-authorized version of Java Development Kit (JDK) - Oracle. Per the Initial Product Review, users must abide by the following constraints: OpenSC must be run on VA standard desktops as it relies on the underlying operating system for encryption. The VA requires support for all software used on the VA network. Vendor or third-party support at an enterprise level is not free and must be acquired for any open source product to be deployed on the VA network. The OpenSC community has a mailing list as their main form of support. Per community: “But if you are using OpenSC as part of some other product, for example Red Hat Enterprise Linux, we as a Red Hat are able to provide commercial support for OpenSC deployments in RHEL. Similarly if you are using some particular hardware (ex. Nitrokey), they have engineers who are able to offer commercial support.” System administrators must ensure that the latest stable version of OpenSC is used. OpenSC must also be included in the list of continuously monitored software for vulnerabilities, patches, and upgrades.

[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 ISSO (Information System Security Officer) to ensure compliance with VA Handbook 6500.

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

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

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

[12]	Users must not utilize OpenVPN, as it is at the time of writing, unapproved in the TRM. Users must not use PuTTY or TrueCrypt with this technology as they are unapproved for use at this time. Users must ensure that Firefox and Google Chrome are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM. This technology must use the latest TRM-authorized version of Java Development Kit (JDK) - Oracle. Per the Initial Product Review, users must abide by the following constraints: OpenSC will require a 3rd party FIPS 140-2 (or its successor) certified solution for any data containing Personal Health Information (PHI) / Personally Identifiable Information (PII) or VA sensitive information. Regularly audit the use of OpenSC and its cryptographic modules. Engage in penetration testing and code reviews to find security flaws, particularly those related to data handling and cryptographic operations. Users should check with their supervisor, 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.

[13]	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.25.1 is the most current version, released 04/05/2024.

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
cardos-tool	cardos-tool displays information about Card OS-based security tokens or format them.
cryptoflex-tool	cryptoflex-tool is a utility for manipulating Schlumberger Cryptoflex data structures.
dnie-tool	dnie-tool displays information about DNIe (Spanish National eID card) based security tokens.
egk-tool	egk-tool displays information on the German electronic health card (elektronische Gesundheitskarte, eGK).
eidenv	eidenv is a utility for accessing visible data from electronic identity cards.
gids-tool	gids-tool is a smart card utility for GIDS (Generic Identity Device Specification) cards.
iasecc-tool	iasecc-tool displays information about IAS/ECC (Identification Authentication Signature – European Citizen Card) card.
netkey-tool	netkey-tool is an administrative utility for Netkey E4 cards.
npa-tool	npa-tool displays information on the German eID card (neuer Personalausweis, nPA).
openpgp-tool	openpgp-tool is a utility for accessing visible data OpenPGP (Pretty Good Privacy) smart cards and compatible tokens.
opensc-asn1	opensc-asn1 parses ASN.1 (Autonomous system number) data.
opensc-explorer	opensc-explorer is a generic interactive utility for accessing smart card and similar security token functions.
opensc-notify	opensc-notify monitors smart card events and send notifications.
opensc-tool	opensc-tool is a generic smart card utility.
piv-tool	piv-tool is a smart card utility for HSPD-12 ( Homeland Security Presidential Directive) PIV (Personal Identity Verification) cards.
pkcs11-tool	pkcs11-tool is a utility for managing and using PKCS (Public Key Cryptography Standards) #11 security tokens.
pkcs15-crypt	pkcs15-crypt performs crypto operations using PKCS (Public Key Cryptography Standards) #15 smart cards.
pkcs15-init	pkcs15-init is a smart card personalization utility.
pkcs15-tool	pkcs15-tool is a utility for manipulating PKCS (Public Key Cryptography Standards) #15 data structures on smart cards and similar security tokens.
sc-hsm-tool	sc-hsm-tool is a smart card utility for SmartCard-HSM (Hardware security module).
westcos-tool	westcos-tool utility for manipulating data structures on westcos smart cards.


Security Identity and Access Management	Authentication

General Analysis

Adoption Benefits

The technology has a comprehensive set of documentation.
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 working with smart cards.

Adoption Risks

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.
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.
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 other authorized solutions that provide similar functionality available on the TRM. The use of several similar solutions may increase organization requirements for support and maintenance.
This technology relies on Java Development Kit (JDK) - 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 PuTTY, an unapproved technology.
This technology can potentially use OpenVPN, an unapproved technology.
This technology can potentially use TrueCrypt, an unapproved technology.
IPR/SAR Adoption Risk - The product is not Federal Information Processing Standards (FIPS) 140-2 (or its successor) certified.
IPR/SAR Adoption Risk - The product has several vulnerabilities noted in the National Vulnerability Database (NVD).
IPR/SAR Adoption Risk - OpenSC is an open source software that is freely available to users and lacks enterprise level support.

Architectural Benefits

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

- The information contained on this page is accurate as of the Decision Date (09/16/2024 at 14:58:55 UTC).

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 24.11

General Information

Vendor Release Information

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

Optional 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.11

General Information

Vendor Release Information

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

Optional Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

EMAIL UPDATES

VA Categories

View the VA Categorization Framework