![SafeNet Luna SA Скачать руководство пользователя страница 71](http://html1.mh-extra.com/html/safenet/luna-sa/luna-sa_configuration-manual_798623071.webp)
CHAPTER 4 HSM Capabilities and Policies
Note:
The FIPS 140-2 standard mandates a set of security factors that specify a restricted
suite of cryptographic algorithms. The HSM is designed to the standard, but can permit
activation of additional non-FIPS-validated algorithms if your application requires them. The
example listing above indicates that non-validated algorithms have been activated. The HSM is
just as safe and secure as it is with the additional algorithms switched off. The only difference
is that an auditor would not validate your configuration unless the set of available algorithms is
restricted to the approved subset.
2.
In order to change HSM policies, the HSM Administrator must first login.
lunash:> hsm login
(If you are not logged in, the above command begins the login process, directing you to the PED. If you are already
logged in, the Luna SA tells you so, with an error message, that you can ignore.)
Control is passed to the PED, which prompts you for the blue PED Key.
Insert the appropriate PED Key for this HSM, and press [ENT] on the PED keypad.
3.
If you need to modify a policy setting to comply with your operational requirements, type:
lunash:> hsm changePolicy -policy <policyCode> -value <policyValue>
As an example, change code 15 from a value of 1 (On) to 0 (Off).
Example – Change of HSM Policy
lunash:> hsm changePolicy -policy 15 -value 0
That command assigns a value of zero (0) to the “HSM Admin can reset partition PIN” policy, turning it off.
WARNING! The above example is a change to a destructive policy, meaning that, if
you apply this policy, the HSM is zeroized and all contents are lost. For this reason,
you are prompted to confirm if that is what you really wish to do. You must now re-
initialize the HSM.
While this is not an issue when you have just initialized an HSM, it may be a very
important consideration if your HSM system has been in a “live” or “production”
environment and the HSM contains useful or important data, keys, certificates.
If you have been following the instructions on this page as part of setting up a new HSM system, then the next step is to
create virtual HSMs or HSM Partitions on the HSM that you just configured. Click the following link:
Create Partition
(Trusted Path Authentication)
Luna SA 5 does not currently have a secure identity management (SIM) configuration. Certain HSM policy settings
exist to enable migration from Luna SA 4.x to Luna SA 5.x, specifically the “Enable masking” and “Enable portable
masking key” values.
Luna SA Configuration Guide
Release 5.4.1 007-011136-007 Rev C July 2014 Copyright 2014 SafeNet, Inc. All rights reserved.
71
Содержание Luna SA
Страница 1: ...Luna SA Configuration Guide ...