YubiHSM 2 can be used as a comprehensive cryptographic toolbox for a wide range of open source and commercial applications. The most common use case being hardware-based digital signature generation and verification.
YubiHSM 2 offers a compelling option for secure generation, storage and management of digital keys including essential capabilities to generate, write, sign, decrypt, hash and wrap keys.
Enhance Protection for Cryptographic Keys
YubiHSM 2 offers a compelling option for secure generation, storage and management of keys. Key protection is done in the secure on-chip hardware isolated from operations on the server. Most common use cases involve protecting of the certificate authorities (CAs) root key. YubiHSM 2 capabilities include: generate, write, sign, decrypt, hash and wrapping keys.
Enable Hardware based Cryptographic Operations
YubiHSM 2 can be used as a comprehensive cryptographic toolbox for low-volume operations in conjunction with a huge set of open source and commercial applications spanning many different products and services. Most common use case involve on-chip hardware based processing for signature generation and verification.
Secure Microsoft Active Directory Certificate Services
YubiHSM 2 can provide hardware backed keys for your Microsoft-based PKI implementation. Deploying YubiHSM 2 to your Microsoft Active Directory Certificate services not only protects the CA root keys but also protects all signing and verification services using the root key.
Secure key storage and operations
Create, import, and store keys, then perform all crypto operations in the HSM hardware to prevent theft of keys while at rest or in use. This protects against both logical attacks against the server, such as zero-day exploits or malware, and physical theft of a server or its hard drive.
Extensive cryptographic capabilities
YubiHSM 2 supports hashing, key wrapping, asymmetric signing and decryption operations including advanced signing using ed25519. Attestation is also supported for asymmetric key pairs generated on-device.
Secure session between HSM and application
The integrity and privacy of commands and data in transit between the HSM and applications are protected using a mutually authenticated, integrity and confidentiality protected tunnel.
Role-based access controls for key management and key usage
All cryptographic keys and other objects in the HSM belong to one or more security domains. Access rights are assigned for each authentication key at creation time which allow a specific set of cryptographic or management operations to be performed per security domain. Admins assign rights to authentication keys based on its use case, such as a event monitoring app that needs the ability to read all audit logs in the HSM, or a Registration Authority that needs to issue (sign) end user digital certificates, or a domain security admin who needs to create and delete crypto keys.
16 concurrent connections
Multiple applications can establish sessions with a YubiHSM to perform cryptographic operations. Sessions can be automatically terminated after inactivity or be long-lived to improve performance by eliminating session creation time.
To increase the flexibility of deployments, the YubiHSM 2 can be made available for use over the network by applications on other servers. This can be especially advantageous on a physical server that is hosting multiple virtual machines.
Easily manage multiple deployed YubiHSMs remotely for the entire enterprise – eliminate on-call staff complexity and travel expense.
Unique “Nano” form factor, low-power usage
The Yubico “Nano” form factor allows the HSM to be inserted completely inside a USB-A port so it’s completely concealed – no external parts that protrude out of the server back or front chassis. It uses minimal power, max of 30mA, for cost-savings on your power budget.
M of N wrap key Backup and Restore
Backing up and deploying cryptographic keys on multiple HSMs is a critical component of an enterprise security architecture, but it’s a risk to allow a single individual to have that ability. The YubiHSM supports setting M of N rules on the wrap key used to export keys for backup or transport, so that multiple administrators are required to import and decrypt a key to make it usable on additional HSMs. For example in an enterprise, the Active Directory root CA private key might be key wrapped for 7 administrators (M=7) and at least 4 of them (N=4) are required to import and unwrap (decrypt) the key in the new HSM.
Interfaces via YubiHSM KSP, PKCS#11, and native libraries
Crypto enabled applications can leverage the YubiHSM via Yubico’s Key Storage Provider (KSP) for Microsoft’s CNG or industry-standard PKCS#11. Native libraries are also available on Windows, Linux and macOS to enable more direct interaction with the device’s capabilities.
Tamper evident Audit Logging
The YubiHSM internally stores a log of all management and crypto operation events that occur in the device and that log can be exported for monitoring and reporting. Each event (row) in the log is hash chained with the previous row and signed so that it’s possible to determine if any events are modified or deleted.
Modell: YUBI HSM 2
|● Mutual authentication and secure channel between applications and the YubiHSM 2 ● M of N unwrap key restore via YubiHSM Setup Tool
|Asymmetric key pairs generated on-device may be attested using a device-specific Yubico attestation key and certificate, or using your own keys and certificates imported into the HSM.
|Specifications Cryptographic interfaces: ● PKCS#11 API version 2.40 ● Yubico Key Storage Provider (KSP) to access Microsoft CNG. The KSP is provided as 64-bit and 32-bit DLLs ● Full access to device capabilities through Yubico’s YubiHSM Core Libraries (C, Python) RSA: ● 2048, 3072, and 4096 bit keys (with e=65537) ● Signing using PKCS#1v1.5 and PSS ● Decryption using PKCS#1v1.5 and OAEP Elliptic Curve Cryptography (ECC): ● Curves: secp224r1, secp256r1, secp256k1, secp384r1, secp521r, bp256r1, bp384r1, bp512r1, Ed25519 ● Signing: ECDSA (all except Ed25519), EdDSA (Ed25519 only) ● Derivation: ECDH (all except Ed25519)
|SHA-256, SHA-384, SHA-512, SHA-1
|YUBI HSM 2
|NIST-approved AES-CCM Wrap
|Import and export with 128, 196, and 256 bit keys
|● All data stored as objects. 256 object slots, 126KB max total ● Stores up to 127 rsa2048 or 93 rsa3072 or 68 rsa4096 or 255 of any elliptic curve type, assuming only one authentication key is present ● Object Types : Authentication keys (used to establish sessions); Asymmetric private keys; Opaque binary data objects (e.g. x509 certificates); Wrap keys; HMAC keys
|On-chip True Random Number Generator (TRNG) used to sow NIST SP 800-90A Rev.1 AES-256 CTR_DRBG
|YUBI HSM 2
|● Universal Serial Bus (USB) 1.x Full Speed (12Mbit/s) Peripheral with bulk interface
|The accompanying Software Development Kit includes performance tools that can be used for additional measurements. Example metrics from an otherwise unoccupied YubiHSM 2: ● RSA-2048-PKCS1-SHA256: ~139ms ● RSA-3072-PKCS1-SHA384: ~504ms ● RSA-4096-PKCS1-SHA512: ~852ms ● ECDSA-P224-SHA1: ~64ms ● ECDSA-P256-SHA256: ~73ms ● ECDSA-P384-SHA384: ~120ms ● ECDSA-P521-SHA512: ~210ms ● EdDSA-25519-32Bytes: ~105ms ● EdDSA-25519-64Bytes: ~121ms ● EdDSA-25519-128Bytes: ~137ms ● EdDSA-25519-256Bytes: ~168ms ● EdDSA-25519-512Bytes: ~229ms ● EdDSA-25519-1024Bytes: ~353ms ● AES-(128|192|256)-CCM-Wrap: ~10ms ● HMAC-SHA-(1|256): ~4ms ● HMAC-SHA-(384|512): ~243ms YubiHSM 2.1
|● Form factor: nano designed for confined spaces such as internal USB ports in servers