FIPS 201 SDK

FIPS 201 SDK
The PIVCheck FIPS 201 API provides an interface between a user-provided application and FIPS 201- and CAC-compliant smart cards. The API exposes all of the functionality currently available in PIVCheck Desktop and PIVCheck Mobile Edition. Using the SDK for the API, you can develop a custom application that communicates with PIV, TWIC, CAC, and GSC-IS smart cards. The SDK is available via license for use by Codebench strategic development partners that have in-house software development resources experienced in programming with MS Visual C/C++, MS Visual C# and MS Visual Basic, or Java. The API is available for the following frameworks:
  • Microsoft .NET 2.0 or greater for Windows PCs
  • Microsoft Compact Framework 2.0 or greater for Windows CE devices
  • Unmanaged C
  • Java and unmanaged C (via JNI)
With just a few lines of code, the SDK enables a user application to perform operations such as:
  • Verify the card's PIN
  • Capture and match fingerprints with templates on PIV cards
  • CHUID and biometric signature support with support for RSA and ECDSA
  • Verify PIV and CAC card authenticity using PKI-AUTH or PKI-CAK with RSA and ECC support
  • Validate PIV card revocation status using MS CAPI, MS CNG, OCSP, or SCVP
  • Extract all data elements from the PIV card
Typical applications that can be developed using the API are:
  • Visitor management
  • PIV card data harvesting for PACS registration
  • Spot-checking TWICs
The PIVCheck FIPS 201 SDK contains various .DLL files that interface with the hardware and network services, instructions for functions and sample applications. For physical access control (PACS) integration, the FIPS 201 SDK Plus option provides the ability to provision the credential in a PACS and configures it for subsequent re-validation, if desired.

The SDK is not available for use outside of the U.S. and its territories. Portions consist of redistributable libraries from third parties and open source developers. Some contain strong encryption. Products derived from this SDK may be subject to U.S. Department of Commerce, Bureau of Industrial Security export controls. For more information about export controls, visit http://www.bis.doc.gov.