Tamper Events
SafeNet Luna Network HSMs detect hardware anomalies (such as card over-temperature) and physical events (such as card removal or chassis intrusion), and register them as tamper events. A tamper event is considered a security breach, and effectively locks the HSM.
If Policy 48: Do Controlled Tamper Recovery is enabled (the default), the HSM SO must clear the tamper condition before the HSM is reset, to return the HSM to normal operation (see HSM Capabilities and Policies). While the HSM is in the tamper condition, only the subset of
You can enable Policy 40: Decommission on Tamper to decommission the HSM when a tamper event occurs, so that partitions and roles are deleted from the HSM. By default, Policy 40: Decommission on Tamper is disabled, and the contents of the HSM are not affected by the tamper event.
If both policies are disabled, the HSM sends a warning when a tamper event occurs but does not make partition data inaccessible. We do not recommend disabling both policies.
If both policies are enabled, the HSM SO role is deleted when a tamper event occurs, so you do not need to log in this role to clear the tamper condition.
There are several conditions that can result in a tamper. The tamper state is indicated by the HSM Tamper State field in the output of the LunaSH hsm show command. If tamper events have been detected and not cleared, the field will read Tamper(s) detected. Use the hsm tamper show command to view detailed information for the tamper event, including whether it requires an HSM reset in addition to a tamper clear.
NOTE A tamper event resets the HSM hardware, including the PCIe logic. This prevents the HSM from reporting any statuses, including the cause of the tamper condition. The only thing which is detected in this case is k7pf0: ALM0015: PCIe Link Failure. The HSM must be rebooted before the cause of the tamper event can be reported.
| Tamper event | Response |
|---|---|
| Chassis intrusion |
Halt the HSM. Deactivate activated partitions. Decommission the HSM if policy 40: Decommission on Tamper is enabled. |
| Card removal |
Halt the HSM. Deactivate activated partitions. Decommission the HSM if policy 40: Decommission on Tamper is enabled. |
| Over/under temperature |
Halt the HSM. Deactivate activated partitions. Decommission the HSM if policy 40: Decommission on Tamper is enabled. Warnings are logged for mild over/under temperature events. Warnings are self-clearing if the condition is resolved. |
| Over/under voltage |
Halt the HSM. Deactivate activated partitions. Decommission the HSM if policy 40: Decommission on Tamper is enabled. Warnings are logged for mild over/under voltage events. Warnings are self-clearing if the condition is resolved. |
| Battery removal/depletion |
Halt the HSM. Deactivate activated partitions. Decommission the HSM. Warnings are logged for low battery conditions. |
Recovering from a Tamper Event
How you recover from a tamper event depends on how the following HSM policies are set. See HSM Capabilities and Policies for more information:
| Policy 40: Decommission on tamper | If enabled, the HSM is decommissioned when a tamper event occurs. You must clear the tamper condition before you can re-initialize the HSM SO, re-create your partitions, restore the partition contents from backup, and re-initialize the partition roles (Partition SO, Crypto Officer, and Crypto User, and Audit, as relevant). |
| Policy 48: Do Controlled Tamper Recovery | If enabled, the tamper condition that halted the HSM must be cleared by the HSM SO (by issuing the tamper clear command), before the HSM can be reset to resume normal operations. |
Activation and auto-activation is disabled on tamper
If you are using activation or auto-activation on your PED-authenticated partitions, it is disabled when a tamper is detected, or if any uncleared tamper conditions are detected on reboot. See Activation and Auto-Activation on PED-Authenticated Partitions and Partition Capabilities and Policies for more information.
To recover from a tamper
1.Use the following command to display the last tamper event:
lunash:> hsm tamper show
NOTE The hsm tamper show command only shows the last tamper event, even if several tampers have occurred. To view a complete list of the tamper events that have occurred on the HSM, use the LunaSH hsm supportinfo command.
2.Resolve the issue(s) that caused the tamper event.
3.If Policy 48: Do Controlled Tamper Recovery is enabled, clear the tamper condition. Otherwise, go to the next step:
lunash:> hsm tamper clear
4.If the tamper message indicates that a reset is required, use the LunaSH sysconf appliance reboot command to reboot the HSM:
lunash:> sysconf appliance reboot
5.Verify that all tampers have been cleared:
lunash:> hsm tamper show
6.If the HSM was decommissioned as a result of the tamper, you must re-create your partitions, re-initialize the partition roles (Partition SO, Crypto Officer, and Crypto User, and Audit as relevant), and restore the partition contents from backup. See the following sections in the Configuration Guide .
a.To re-create your partitions, see Create Application Partitions.
b.To re-initialize the partition roles, see Configure Application Partitions.
c.To restore the partition contents from backup, see Backup and Restore HSMs and Partitions.
7.If the Policy 22: Allow Activation and/or Policy 23: Allow AutoActivation are enabled on your PED-authenticated partitions, the CO and CU (if enabled) must log in to reactivate those roles:
lunacm:> role login -name <role>
