CHAPTER 3 HSM Initialization
specific, hands-on, oversight and recovery actions, in the case of a tamper event at the HSM. In that case, keep the
external split and handle with care (including having on-site and off-site backup copies, just as you would with the
Security Officer (blue) PED Key). You are not "done" with a purple PED Key until its contents have been returned to its
HSM with
srk disable
.
Re-split
1
the SRK
You have the option to re-split the SRK at any time - you need the current external SRK split (the purple PED Key(s)) to
initiate the action. The purpose would be to ensure that the SRK for your HSM is secure and that you have the only
copies of the external portion of the secret. That is, by re-splitting at your convenience, you remove the risk that
somebody kept a copy of the purple PED Key before they sent your HSM to you. Any copy of the previous secret
becomes useless when a re-split operation is performed. Similar logic applies if a copy of your new SRK goes missing
(or is thought to have been compromised) - a re-split/regeneration of the secure recovery vector onto a new external key
(SRK) or keys renders the lost/stolen/compromised SRK useless to anyone.
Other Uses of the SRK
The SRK is also used to recover from a real tamper event on the HSM or its appliance.
The steps are the same as above, except that the HSM resumes granting access with its contents intact - [re-]
initialization is not required.
You can set the HSM to Secure Transport Mode before placing it into storage, or before shipping to your organization's
remote location, or before shipping to your customer (offering them the same Secure Shipping option as is available
from SafeNet).
If you have just received an HSM from SafeNet in Secure Transport Mode, and recovered from STM, your next step
should be to initialize the HSM. Go to
"Initializing a PED-Authenticated HSM" on page 48
.
See also
"re-split required"
.
To view a table that compares and contrasts various "deny access" events or actions that are sometimes confused,
see
"Comparison of destruction/denial actions"
.
Initializing a PED-Authenticated HSM
In this section, you initialize the HSM portion of the Luna appliance, and set any policies that you require. In normal
operation, you would perform these actions just once, when first commissioning your Luna appliance.
Note:
Perform initialization only after you have set the system-level parameters - time, date,
timezone, use of NTP (Network Time Protocol), etc. - and configured network and IP settings
to work with your network.
Exception: The statement (above) applies to a new Luna SA appliance, or one that has been
factory reset. One of the options when initializing an HSM is to forbid changing of
time/timezone without HSM login
(hsm init -label myluna -authtimeconfig)
. If
you make that choice, then it remains in force until you change it. Therefore, if you are following
these steps for a Luna SA appliance that is not fresh from the factory, or freshly factoryReset,
1
[ see 'resplit' ]
Luna SA Configuration Guide
Release 5.4.1 007-011136-007 Rev C July 2014 Copyright 2014 SafeNet, Inc. All rights reserved.
48
Содержание Luna SA
Страница 1: ...Luna SA Configuration Guide ...