Overview
CSPid is a virtual smartcard that maintains a central repository for private keys and X.509 certificates. It provides a secure environment for cryptographic operations that applications can access via Java, PKCS#11, or Microsoft CAPI. It is available for, and compatible between, all destop version of Windows, Linux/x86, and Solaris/SPARC.
The “Key” Benefits of CSPid
CSPid
- provides a common, operating system independent credential store that may be shared by all security-enabled applications
- simplifies enterprise-wide credential management; users need not replicate keys among applications, and may effortlessly migrate credentials between workstations
- provides administrative controls over user credentials; allows PKI enrollment, key rollover, credential backup, and other key management tasks to be automated in a user-transparent manner
- provides superior protection for private keys and overcomes password change/reset issues with Internet Explorer and Mozilla
- reduces help desk costs and PKI training requirements
CSPid 1.1 Architecture Diagram
CSPid stores a user’s credentials in a single encrypted file on any designated storage device (e.g., a local hard drive, a network share, a flash drive, or any other removable memory device). That credential store may be opened by CSPid on any platform once its owner has entered their password.
In this way CSPid allows users to effortlessly migrate their public and private keys to any workstation in an OS-independent manner, without the need to physically replicate those keys. (The fewer persistent copies of a user’s private key that are created, the less likely it is to be compromised.)
CSPid’s programmable interface simplifies certificate lifecycle management. By giving security officers control over employee credentials throughout their enterprise, it reduces help desk costs and PKI training requirements.
Security officers can configure CSPid to force password change at designated intervals, prohibit password reuse, and enforce password quality requirements on cryptographic keys. These security policy settings are then enforced for all connected applications, including Microsoft IE and Mozilla (which do not provide such controls by themselves).
|