PKI Identification Tokens
FEITIAN PKI tokens keep X.509 digital certificates and private keys on a smart card chip, so the private key cannot be copied off the computer the way a software certificate file can. Organizations use them for certificate-based logon, digital signatures, email and file encryption, and VPN access. The range covers the ePass2003 USB-A token for mixed Windows, macOS and Linux fleets, the driverless ePass3003Auto, which installs its own middleware on Windows, and the StorePass2003, which adds 8 GB or 16 GB of flash storage. Supported middleware includes Microsoft Minidriver, CSP and PKCS#11.
How to Choose a PKI Token
- Low-touch Windows rollouts: the ePass3003Auto installs its own middleware the first time it is inserted.
- Mixed Windows, macOS and Linux fleets: the ePass2003 works with Microsoft Minidriver and OpenSC.
- Certificates plus secure file transport: the StorePass2003 adds 8 GB or 16 GB of flash memory.
- Check your PKI software: confirm that your certificate authority, VPN and signing tools support Minidriver or PKCS#11 before you buy in volume.
ePass2003 vs ePass3003Auto vs StorePass2003
| ePass2003 | ePass3003Auto | StorePass2003 | |
|---|---|---|---|
| Interface | USB-A | USB-A | USB-A |
| Chip | Common Criteria EAL5+ certified chip | 32-bit smart card chip, FIPS approved chip onboard | 16-bit smart card chip, Common Criteria EAL5+ certified |
| Certificate storage | 64 KB secure memory | 64 KB available for users (256 KB total) | 64 KB EEPROM plus 8 GB or 16 GB flash for files |
| Middleware | Microsoft Minidriver, CSP, CNG, PKCS#11, PC/SC, OpenSC | Built in: installs itself on Windows; CSP, PKCS#11 | Microsoft Minidriver, CSP, CAPI, CNG, PKCS#11, PC/SC |
| Operating systems | Windows, macOS, Linux, Chrome OS | Windows, macOS, Linux, Chrome OS | Windows (32 and 64 bit), macOS, Linux |
| Algorithms | RSA 1024/2048, ECDSA 192/256, AES 128/192/256, 3DES, SHA-1, SHA-2 | RSA 1024/2048, DES, 3DES, MD5, SHA-1 | RSA 1024/2048, ECDSA 192/256, DES/3DES, AES 128/192/256, SHA-1/SHA-256 |
| Best for | Mixed Windows, macOS and Linux fleets | Low-touch Windows rollouts | Certificates plus secure file transport |
Need a FIPS 140 validated PKI token? Ask sales@ftsafe.us which models and versions are available for your project.
What FEITIAN PKI Tokens Are Used For
- Document signing: sign PDFs and contracts with a certificate whose private key stays on the token, through Minidriver and CNG on Windows or PKCS#11 elsewhere.
- Code signing: keep the code signing key on the ePass2003 so builds can be signed only while the token is present.
- Email encryption: S/MIME encryption and signing with keys that never leave the chip.
- VPN and certificate logon: Windows smart card logon and certificate-based VPN access, with the token PIN as the second factor.
Where FEITIAN PKI Tokens Fit
PKI tokens are dedicated smart card devices for certificates, separate from FIDO2 security keys. Some security keys add a PIV applet for certificate login next to FIDO2 sign-in, which suits users who need both on one device. A dedicated PKI token suits certificate-heavy work: several certificates per user, OpenSC or PKCS#11 tools on Linux, driverless Windows rollouts with the ePass3003Auto, or files and certificates on one device with the StorePass2003. Compare PIV security keys if your users also need FIDO2.
Learn More
- PKI tokens for digital certificates: enrollment, storage and renewal
- How to choose enterprise security hardware
Frequently Asked Questions
How does a PKI token protect a digital certificate?
The token keeps the private key on its chip and performs signing and decryption there, so the key never sits on the computer where malware could copy it. The ePass3003Auto, for example, generates RSA key pairs on board, and its private key can never be retrieved. Users also need the token PIN, so a stolen token alone is not enough.
What middleware do FEITIAN PKI tokens use?
Applications reach a PKI token through middleware: on Windows that is usually the Microsoft Minidriver, CSP or CNG, and on other platforms PKCS#11 or OpenSC. The ePass2003 supports Minidriver and OpenSC across Windows, Linux and Mac, while the ePass3003Auto stores its middleware on the token and installs it automatically on Windows.
Which PKI token should I use for digital signing?
For document, email and code signing across Windows, macOS and Linux, the ePass2003 signs through Minidriver and CNG on Windows or PKCS#11 elsewhere, and the token must be present to sign. If signers also need to carry files securely, the StorePass2003 adds onboard digital signature and verification plus 8 GB or 16 GB of flash storage.
Which operating systems do FEITIAN PKI tokens support?
The ePass2003 and ePass3003Auto support Windows, Linux, macOS and Chrome OS. The StorePass2003 supports 32-bit and 64-bit Windows, Linux and macOS through its MiniDriver, CSP and PKCS#11 middleware.
Can you recommend a PKI token for data encryption?
For email, file and VPN encryption across Windows, macOS and Linux, the ePass2003 supports AES, 3DES, RSA and ECDSA and keeps the keys on the chip. For Windows-only rollouts where users should install nothing, the ePass3003Auto carries its own middleware. If users also move encrypted files, the StorePass2003 adds 8 GB or 16 GB of flash storage.
What should we do when a PKI token is lost?
Block the token, revoke its certificates through your certificate authority, and issue a replacement token to the user. If the token held encryption keys, restore them from your key escrow so old encrypted files and email stay readable. The same process applies to the ePass2003, ePass3003Auto and StorePass2003.









