Chapter 4: System Logging
2017 Mar
1 14:29:53 local_host
local5 info
hsm[3948]: STC policy is set to "OFF" on partition
66331 : Unknown ResultCode value
2017 Mar
1 14:29:59 local_host
local5 info
lunash [29529]: info : 0 : Command: syslog
remotehost add
: admin : 10.124.0.87/61470
2017 Mar
1 14:30:37 local_host
local5 info
hsm[5511]: STC policy is set to "OFF" on partition
66331 : Unknown ResultCode value
2017 Mar
1 14:30:48 local_host
local5 info
lunash [29529]: info : 0 : Command: syslog
remotehost list
: admin : 10.124.0.87/61470
2017 Mar
1 14:33:10 local_host
local5 info
lunash [29529]: info : 0 : Command: syslog severity
set
: admin : 10.124.0.87/61470
2017 Mar
1 14:33:47 local_host
local5 info
lunash [29529]: info : 0 : Command: syslog severity
set -logname lunalogs -loglevel crit : admin : 10.124.0.87/61470
Command Result : 0 (Success)
HSM Alarm Logging
The HSM card produces logs pertaining to the card status, including alarm messages for events such as
zeroization, tamper events, and changes to Secure Transport Mode. The
syslog tail
command allows you to
search for this type of message in the logs.
To search the system logs for HSM alarm messages:
Search for log messages containing the string "ALM" (see
).
lunash:>
syslog tail -logname messages -entries
<#entries>
-search ALM
For example, this command will display all alarm messages from the last 200000 log entries:
lunash:>syslog tail -logname messages -entries 200000 -search ALM
2017 Apr 17 11:00:45 local_host kern info kernel: k7pf0: [HSM] ALM2006: HSM decommissioned by FW
2017 Apr 17 11:00:48 local_host kern info kernel: k7pf0: [HSM] ALM2014: Auto-activation data
invalid - HSM deactivated
2017 Apr 17 11:01:12 local_host kern info kernel: k7pf0: [HSM] ALM2006: HSM decommissioned by FW
2017 Apr 17 11:01:14 local_host kern info kernel: k7pf0: [HSM] ALM2011: HSM unlocked - tamper
clear done
2017 Apr 17 11:02:47 local_host kern info kernel: k7pf0: [HSM] ALM2007: HSM zeroized
2017 Apr 17 11:02:47 local_host kern info kernel: k7pf0: [HSM] ALM2005: HSM deactivated
2017 Apr 17 11:15:32 local_host kern info kernel: k7pf0: [HSM] ALM2013: HSM recovered from secure
transport mode
Command Result : 0 (Success)
Exporting System Logs
If you are managing the logs locally, you must transfer them to a client workstation in order to read them. After
you have exported the log records, you can clear them from the syslog directory on the appliance.
To transfer system logs from the appliance to a client:
1.
Create the log archive file (see
).
lunash:>
syslog tarlogs
lunash:>syslog tarlogs
The tar file containing logs is now available via scp as filename 'logs.tgz'.
Command Result : 0 (Success)
SafeNet Luna Network HSM 7.3 Appliance Administration Guide
007-013576-005 Rev. A 13 December 2019 Copyright 2001-2019 Thales
50