- 23 Jan 2025
- 3 Minutes à lire
- SombreLumière
- PDF
OneSpan customer procedure
- Mis à jour le 23 Jan 2025
- 3 Minutes à lire
- SombreLumière
- PDF
Customers must adhere to the following key management procedures to be able to use the authenticator application:
- Generate the HSM-level BLOB storage key.
- Generate the KEK with Custodians Export.
- Generate the HSM-level DPX transport key.
- Export the HSM-level DPX transport key wrapped by the KEK.
- Distribute the encrypted HSM-level DPX transport key and the KEK to OneSpan.
Procedure 2 to 5 are only required in case of double-encrypted DPX-file import.
Generate the HSM-level BLOB storage key
To generate the HSM-level BLOB storage key
- Open the KMU (HSM) tool included in the Thales ProtectServer Protect Toolkit C.
- Under Select a token, log in on <Slot0> as User(password is required).
The slot ID may vary depending on the configuration.
- From the menu, select Options > Create > Secret Key.
- Select the Mechanism: Double DES, Triple DES, AES with key size 128 bits or AESwith key size 256 bits.
With these settings, vascoStorageKey backup is not possible. To allow backup, set Exportable to TRUE.
Generate the KEK with custodians export
The purpose of this key is to export the HSM-level DPX transport key generated in Generate the HSM-level DPX transport key.
Because this key is highly sensitive, it should be generated by a security officer.
- In the Key Managment Utility window, under Select a token, log in on <Slot0> as Security Officer (password is required).
- From the menu, select Options > Create > Generate Key Components.
- Select the Mechanism: Double DES, Triple DES, AES with key size 128 bits or AESwith key size 256 bits.
- Specify the number of KEK components (typically 2 or 3).
- Keep the key components and their KCVs safe.
- Repeat the previous steps for all further key components.
- In the Key Managment Utility window, verify the three keys are created.
Each component of the KEK must be kept safe by a key custodian. The KEK generation must be supervised by the security officer.
- In the Key Managment Utility window, under Select a token, log in on <Slot0> as User (password is required).
Generate the HSM-level DPX transport key
To generate the HSM-level DPX transport key
- In the Key Managment Utility window, from the Menu, select Options > Create > Secret Key.
- Select the Mechanism: Double DES, Triple DES, AES with key size 128 bits or AESwith key size 256 bits.
For security reasons, set Extractable to FALSE and Exportable to TRUE.
With this setup, only a security officer can create a key that can export this HSM-level DPX transport key.
When the key is generated, in the Key Managment Utility window, right-click on vascoTransportKey.
- From the shortcut menu, select View KCV.
During this operation, the security officer in charge of the export ceremony must verify that Extractable is set to FALSE, and Exportable is set to TRUE. Otherwise, the HSM-level DPX transport key will be easily exportable outside the HSM, and its secret might be compromised.
Export the HSM-level DPX transport key wrapped by the KEK
To export the HSM-level DPX transport key
- To prepare the export, in the Key Managment Utility window, select OneSpanTransportKey.
Figure: Export the HSM-level DPX transport key wrapped by the KEK (1)
- From the menu, select Options > Export.
- Select the write encrypted part to the screenoption.
Figure: Export the HSM-level DPX transport key wrapped by the KEK (2)
- Keep the wrapped key and its KCV safe.
Figure: Export the HSM-level DPX transport key wrapped by the KEK (3)
Distribute the encrypted HSM-level DPX transport key and the KEK to OneSpan
The HSM-level DPX transport key can be delivered to OneSpan using the following media:
- secure physical mail (secure envelope)
- fax
Date: 07 March 2007
Wrapped Transport Key: 1e7b 3a39 ee0b 793a 8338 19f3
ea0a c057 18ff c6ee 7609 3909
Transport Key KCV: d2e3d3
Key Encryption Key KCV: 26d098
The components of the KEK can be delivered to OneSpan using the following media:
- secure physical mail (secure envelope) for every single key component
Date: 07 March 2007
Key Share (A/B/C): A
Key Share: b9ae 4051 a8f8 625b 01d0 b93b
6131 dadc c779 f494 fd8a 5eea
Key Share KCV: 1ccc74
Key Encryption Key KCV: 26d098