OneSpan customer procedure
  • 23 Jan 2025
  • 4 Minutes à lire
  • Sombre
    Lumière
  • PDF

OneSpan customer procedure

  • Sombre
    Lumière
  • PDF

The content is currently unavailable in French. You are viewing the default English version.
Résumé de l’article

Customers must adhere to the following key management procedures to be able to use the authenticator application:

  1. Generate the HSM-level BLOB storage key.
  2. Generate the KEK with Custodians Export.
  3. Generate the HSM-level DPX transport key.
  4. Export the HSM-level DPX transport key wrapped by the KEK.
  5. 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

  1. Launch Key Management Tool provided with Authentication Suite Server SDK for HSM.

    Figure: Generate the HSM-level BLOB storage key (1)

  2. On the Key Management Tool main screen, select (2): Generate a storage key.

  3. Select one of the following key types: AES128, AES256, DES2 or DES3. The default value is 3. (DES2 is not recommended.)

In case of using FIPS 140-2 Level 3 Security World (strict FIPS 140-2 Level 3 mode), the new Entrust nShield HSMs based on PowerPCELF architecture (nShield XC) does not permit to generate keys being double-length 3DES keys (DES2).

Attempting to generate a storage key with DES2 type will fail in such case with the following error: “Function exits with an error : 62 -> StrictFIPS140”.

  1. Select the ID of the storage key. The default value is 0.

    Figure: Generate the HSM-level BLOB storage key (2)

The key name is determined by the key ID as follows:

  • ID 0 corresponds to the name vascoStorageKey.
  • IDs 1 to 9 correspond to the names vasco1 to vasco9.
  • ID 0x7fffff corresponds to the name vascoTransportKey.

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.

As this key is highly sensitive, it should be generated by a security officer.

To generate the KEK

  1. On the Key Management Tool main screen, select (3): Generate a Key Encrypting Key.

  2. Select one of the following key types: AES128, AES256, DES2 or DES3. The default value is 3. (DES2 is not recommended.)

    In case of using FIPS 140-2 Level 3 Security World (strict FIPS 140-2 Level 3 mode), the new Entrust nShield HSMs based on PowerPCELF architecture (Entrust nShield XC) does not permit to generate keys being double-length 3DES keys (DES2).

    Attempting to generate a key encrypting key with DES2 type will fail in such case with the following error: “Function exits with an error : 62 -> StrictFIPS140”.

  3. Select the number of custodians. The default value is 3.

  4. Select the ID of the key encrypting key. The KCV of the KEK appears on the screen.

  5. Press any key to continue.
  6. Figure: Generate the KEK with custodians export (1)

  7. Press any key to display the first component on the screen.

    Figure: Generate the KEK with custodians export (2)

  8. The first component and its KCV are displayed on the screen:

    Figure: Generate the KEK with custodians export (3)

  9. Repeat the previous steps for all further components.

Each component of the KEK must be kept safe by a key custodian. The KEK generation must be supervised by the security officer.

Generate the HSM-level DPX transport key

To generate the HSM-level DPX transport key

  1. On the Key Management Tool main screen, select (4): Generate a Transport Key.
  2. Select one of the following key types: AES128, AES256, DES2 or DES3. The default value is 3. (DES2 is not recommended.)

In case of using FIPS 140-2 Level 3 Security World (strict FIPS 140-2 Level 3 mode), the new Entrust nShield HSMs based on PowerPCELF architecture (Entrust nShield XC) does not permit to generate keys being double-length 3DES keys (DES2).

Attempting to generate a transport key with DES2 type will fail in such case with the following error: “Function exits with an error : 62 -> StrictFIPS140”.

  1. Select the ID of the transport key. The default value is 0x7fffff.
  2. Select the ID of the KEK key authorized to wrap and export this transport key. No other key will be able to perform this operation.

    Figure: Generate the HSM-level DPX transport key (1)

The KCV of the HSM-level DPX transport key is displayed.

During this operation, the security officer in charge of the export ceremony must verify which KEK is authorized to export (wrap) the HSM-level DPX transport key. If the authorized KEK is not controlled by the security officer, the HSM-level DPX transport key secret might be compromised.

Export the HSM-level DPX transport key wrapped by the KEK

To export the HSM-level DPX transport key

  1. On the Key Management Tool main screen, select (5): Export a Transport Key.
  2. Select the ID of the transport key to export. The default value is 0x7fffff.
  3. Select the ID of the KEK key authorized to wrap and export this transport key. This KEK must be the same as in Generate the HSM-level DPX transport key.
  4. Press any key to display the wrapped value of the HSM-level DPX transport key on the screen.

    Figure: Export the HSM-level DPX transport key (1)

The wrapped value of the HSM-level DPX transport key must be kept safe.

  1. Press any key to return to the main screen.

    Figure: Export the HSM-level DPX transport key (2)

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:

  • E-mail
  • 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 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

Cet article vous a-t-il été utile ?

Changing your password will log you out immediately. Use the new password to log back in.
First name must have atleast 2 characters. Numbers and special characters are not allowed.
Last name must have atleast 1 characters. Numbers and special characters are not allowed.
Enter a valid email
Enter a valid password
Your profile has been successfully updated.
ESC

Ozzy, facilitant la découverte de connaissances grâce à l’intelligence conversationnelle