Primus HSM - Attestation and Audit (Device, User, Key)

The attestation feature enables cryptographic evidence of all relevant attributes and allows an auditor to verify it at any time and without physical presence. The attestation is delivered by signed export files of the relevant data, key attributes, HSM configuration, diagnostics, logs, for the device and users. The signed attestation files can be verified by the underlying chain of trust, which goes back to the Securosys root certificate that is inherent in any Primus HSM.

Attestation support

Attestation is currently only supported by the JCE API.

Certificate Chain Overview of Primus HSM Attestation

Based on the above scheme different signed XML attestation files can be exported, including the full chain of trust.

Level	Attestation File	Evidence	User / Interface
Device	Config attestation	- Syslog configuration - Network configuration - Device & Partition configuration - Management setup - Roles / Users	SO / Management
	State attestation	- Hardware model - Software version - Operation mode (FIPS/CC) - Cluster size	SO / Management
	Log attestation	- System status - Key creation - Key usage - Configuration changes - Logins	SO / Management
User	User attestation	- Relevant device configuration - User configuration - User state - User logs	SO, PSO / Management
	Key attestation	- Key in HSM - Key attributes, flags, parameters, usage	API / Data Interface

To ensure a certificate and signatures chain of trust, the Securosys Root key and certificate are initially imported into the device. The device then creates its own intermediary Device key, and its certificate is signed by the root key. The intermediary Device key is then used to sign Attestation and Timestamp keys, created for each Partition via the client API (JCE). The Audit key is generated (protected by the KEK) and its certificate is signed by the intermediary Device key.

• The Attestation key is used to verify the key origin (i.e. that a key has been generated on the particular HSM) and key attributes.
• The Timestamp key is used for generating qualified signatures and applications with time-based key attributes.
• The Audit key is used for signing device and user attestation data for audits (logs, security configuration, device state and digital seal).

The root certificate is available at our Securosys Support Portal, allowing any user to verify and audit the chain of certificates.

This way, digital identity applications can automatically generate identities for users or devices and verify key operations with those identities without a necessity to employ additional procedures or external authorities while guaranteeing their origin and hardware protection and at a virtually zero marginal costs and a limitless scale needed for IoT and personal identity applications.

Attestation requires appropriate licensing. User attestation is supported with HSM firmware v2.11+, Device attestation with HSM firmware v2.10+, key attestation and timestamp functionality with HSM v2.8+.

Factory Reset

Factory Reset deletes all intermediate keys (Device, Audit, and Partition specific keys) and a tamper event disables access!
The User Client may use several Attestation and/or Timestamp keys per Partition.

The following parties are involved in a general audit and attestation procedure:

• HSM operation (SO role)
• Organization (HSM user, signing service operator)
• Qualified Trust Service Provider (Issuer of certificate for code signing or qualified signing / sealing of documents)
• Auditor

Audit and Attestation Procedure

For HSM Audit and Attestation configuration and parameters see Primus HSM User Guide Chapter Audit and Attestation.
For a full walk-through and step-by-step guide with included parameters refer to the Audit and Attestation documentation.