|
Home > |
|---|
The HSM can log its events with varying levels of verbosity (like critical events only, failures, failures and successes, key usage, all). By default, only critical events are logged, which imposes virtually no load on the HSM.
In addition, you have the option to create the Audit user on the HSM and specify that log entries are secured for writing off the HSM. As above, the level/frequency of that logging can be specified by setting the logging threshold.
Or, you can just specify that entries are written to the SafeNet Network Appliance file system without verification security.
Beginning with release 5.2, SafeNet HSMs consolidate and enhance auditing of HSM operations in the Standard Audit Logging feature.
•This method is the most secure and verifiable, to satisfy the strictest auditing requirements.
•This method places the highest Audit-related load on the HSM.
Beginning with release 6.2.1 in general release (and 5.3.10 in limited release), SafeNet Network HSM offers direct-to-file, or appliance-side logging of HSM activity.
•This method preserves the HSM activity audit records and offloads them to the file system for further processing or off-board storage, without securing or validating the resulting records or files.
•This method imposes substantially less processing load on the HSM, compared with the fully secured logging method (above).
The audit logging feature works only with hardware and software update levels at, or newer than, the versions that introduced the feature:
•SafeNet Network HSM 5.x (or newer) appliance
•Client Software 5.2.0 or newer
•HSM Firmware 6.10.x or newer
•SafeNet PED 2.5.0-2 or newer (if PED-authenticated HSM)
The audit logging function is controlled by two roles on SafeNet Network HSM, that must be used together :
•the "audit" appliance account (use ssh or PuTTy to log in as "audit", instead of "admin", or "operator", or "monitor", etc.)
Note: Use of older PuTTY versions, and related tools, can result in the appliance refusing to accept a connection. This can happen if a security update imposes restrictions on connections with older versions. To ensure compatibility, always use the versions of executable files included with the current client installer.
•the "audit" HSM account (accessible only if you have logged into the appliance as "audit"; this account must be initialized)
On SafeNet Network HSM, the audit logging is managed by an audit user (an appliance system role), in combination with the HSM audit role, through a set of lunash:> commands. The audit user can perform only the audit-logging related tasks and self-related tasks. Other HSM appliance users, such as admin, operator, and monitor, have no access to the audit logging commands.
For factory configured SafeNet Network HSM, a default appliance (lunash) audit user is automatically created. Upon first login, the audit user is asked to change his password. That appliance audit user would need to initialize the HSM audit role first, before being able to administer the audit logging. The SafeNet Network HSM admin user can create more audit users when necessary.
To simplify configuration,
•the maximum log file size is capped at 4 MB
•the log path is kept internal
•the rotation offset is set at 0
The HSM Audit role does not exist until it is created (initialized). The appliance audit user is a standard user account on SafeNet Network HSM, with default password "PASSWORD" (without the quotation marks). By default, the appliance audit user is disabled. Therefore, you must enable it in LunaSH before it becomes available. See user enable for the command syntax.
A SafeNet HSM Audit role allows complete separation of Audit responsibilities from the Security Officer (SO or HSM Admin), the Partition User (or Owner), and other HSM roles. If the Audit role is initialized, the HSM and Partition administrators are prevented from working with the log files, and auditors are unable to perform administrative tasks on the HSM. As a general rule, the Audit role should be created before the HSM Security Officer role, to ensure that all important HSM operations (including those that occur during initialization), are captured.
Use LunaSH to initialize the Audit role, as described in audit init.
For SafeNet HSMs with Password Authentication, the auditor role logs into the HSM to perform their activities using a password.
For SafeNet HSMs with PED Authentication, the auditor role logs into the HSM to perform their activities using the Audit (white) PED Key. The Audit feature works only with SafeNet PED version 2.5.0-3 or newer. Older versions of PED firmware are not aware of the Audit role and Audit Key.
Creating the Audit role (and imprinting the white PED Key for PED authenticated HSMs) does not require the presence or cooperation of the HSM SO.
The Audit role has a limited set of operations available to it, on the HSM, as reflected in the reduced command set available to the "audit" user when logged in to the shell (lunash:>).
login as: audit
audit@192.20.9.23's password:
Last login: Mon Jan 19 14:28:27 2015 from 192.20.10.110 SafeNet Network HSM 6.0.0-29 Command Line Shell - Copyright (c) 2001-2015 SafeNet, Inc. All rights reserved. [mylunasa] lunash:>? The following top-level commands are available: Name (short) Description -------------------------------------------------------------------------------- help he Get Help exit e Exit Luna Shell hsm hs > Hsm audit a > Audit my m > My network n > Network
The following list summarizes the functionality of the audit secure logging feature:
•Log entries originate from the SafeNet HSM - the feature is implemented via HSM firmware (rather than in the library) for maximum security
•Log origin is assured
•Logs and individual records can be validated by any SafeNet HSM that is a member of the same domain
•The audit logging feature is applicable to password-authenticated (FIPS 140-2 level 2) and to PED-authenticated (FIPS 140-2 level 3) product configurations (but not between the two - see the "same domain" requirement, above)
•Each entry includes the following:
–when the event occurred
–who initiated the event (the authenticated entity)
–what the event was
–the result of the logging event (success, error, etc.)
•Multiple categories of audit logging are supported, configured by the audit role
•Audit management is a separate role - the role creation does not require the presence or co-operation of the SafeNet HSM SO
•The category of audit logging is configurable by (and only by) the audit role
•Audit log integrity is ensured against the following:
–Truncation - erasing part of a log record
–Modification - modifying a log record
–Deletion - erasing of the entire log record
–Addition - writing of a fake log record
•Log origin is assured
•The following critical events are logged unconditionally, regardless of the state of the audit role (initialized or not):
–Tamper
–Decommission
–Zeroization
–SO creation
– Audit role creation
The HSM creates a log secret unique to the HSM, computed during the first initialization after manufacture. The log secret resides in flash memory (permanent, non-volatile memory), and is used to create log records that are sent to a log file. Later, the log secret is used to prove that a log record originated from a legitimate HSM and has not been tampered with.
A log record consists of two fields – the log message and the HMAC for the previous record. When the HSM creates a log record, it uses the log secret to compute the SHA256-HMAC of all data contained in that log message, plus the HMAC of the previous log entry. The HMAC is stored in HSM flash memory. The log message is then transmitted, along with the HMAC of the previous record, to the host. The host has a logging daemon to receive and store the log data on the host hard drive.
For the first log message ever returned from the HSM to the host there is no previous record and, therefore, no HMAC in flash. In this case, the previous HMAC is set to zero and the first HMAC is computed over the first log message concatenated with 32 zero-bytes. The first record in the log file then consists of the first log message plus 32 zero-bytes. The second record consists of the second message plus HMAC1 = HMAC (message1 || 0x0000). This results in the organization shown below.
| MSG 1 | HMAC 0 |
| . . . | |
| MSG n-1 | HMAC n-2 |
| MSG n | HMAC n-1 |
| . . . | |
| MSG n+m | HMAC n+m-1 |
| MSG n+m+1 | HMAC n+m |
| . . . | |
| MSG end | HMAC n+m-1 |
| Recent HMAC in NVRAM | HMAC end |
To verify a sequence of m log records which is a subset of the complete log, starting at index n, the host must submit the data illustrated above. The HSM calculates the HMAC for each record the same way as it did when the record was originally generated, and compares this HMAC to the value it received. If all of the calculated HMACs match the received HMACs, then the entire sequence verifies. If an HMAC doesn’t match, then the associated record and all following records can be considered suspect. Because the HMAC of each message depends on the HMAC of the previous one, inserting or altering messages would cause the calculated HMAC to be invalid.
The HSM always stores the HMAC of the most-recently generated log message in flash memory. When checking truncation, the host would send the newest record in its log to the HSM; and, the HSM would compute the HMAC and compare it to the one in flash. If it does not match, then truncation has occurred.
Each message is a fixed-length, comma delimited, and newline-terminated string. The table below shows the width and meaning of the fields in a message.
| Offset | Length (Chars) | Description |
|---|---|---|
| 0 | 10 | Sequence number |
| 10 | 1 | Comma |
| 11 | 17 | Timestamp |
| 28 | 1 | Comma |
| 29 | 256 | Message text, interpreted from raw data |
| 285 | 1 | Comma |
| 286 | 64 | HMAC of previous record as ASCII-HEX |
| 350 | 1 | Comma |
| 351 | 96 | Data for this record as ASCII-HEX (raw data) |
| 447 | 1 | Newline '\n' |
The raw data for the message is stored in ASCII-HEX form, along with a human-readable version. Although this format makes the messages larger, it simplifies the verification process, as the HSM expects to receive raw data records.
The following example shows a sample log record. It is separated into multiple lines for readability even though it is a single record. Some white spaces are also omitted.
The sequence number is “38”. The time is “12/08/13 15:30:50”.
The log message is “session 1 Access 2147483651:22621 operation LUNA_CREATE_CONTAINER returned LUNA_RET_SM_UNKNOWN_TOSM_STATE(0x00300014) (using PIN (entry=LUNA_ENTRY_DATA_AREA))”. In the message text, the “who” is the session identified by “session 1 Access 2147483651:22621” (the application is identified by the access ID major = 2147483651, minor = 22621). The “what” is “LUNA_CREATE_CONTAINER”. The operation status is “LUNA_RET_SM_UNKNOWN_TOSM_STATE(0x00300014)”.
The HMAC of previous record is 
The remainder is the raw data for this record as ASCII-HEX.
•The “who” is lunash session “session 1 Access 2147483651:22621”
(identified by the lunash access ID major = 2147483651, minor = 22621).
•The “what” is “LUNA_CREATE_CONTAINER”.
•The operation status is “LUNA_RET_SM_UNKNOWN_TOSM_STATE(0x00300014)”.
Note: Log Rotation Categories, Rotation Intervals, and other Configurable Factors are covered here in the Administration & Maintenance Manual. Command syntax is in the Reference Manual.
The HSM has an internal real-time clock (RTC). The RTC does not have a relevant time value until it is synchronized with the HOST system time. Because the HSM and the host time could drift apart over time, periodic re-synchronization is necessary. Only an authenticated audit officer is allowed to synchronize the time.
The 256-bit log secret which is used to compute the HMACs is stored in the parameter area on the HSM. It is set the first time an event is logged. It can be exported from one HSM to another so that a particular sequence of log messages can be verified by the other HSM. Conversely, it can be imported from other HSMs for verification purpose.
To accomplish cross-HSM verification, the HSM generates a key-cloning vector (KCV, a.k.a the Domain key) for the audit role when it is initialized. The KCV can then be used to encrypt the log secret for export to the HOST.
To verify a log that was generated on another HSM, assuming it is in the same domain, we simply import the wrapped secret, which the HSM subsequently decrypts; any records that are submitted to the host for verification will use this secret thereafter.
When the HSM exports the secret, it calculates a 32-bit checksum which is appended to the secret before it is encrypted with the KCV.
When the HSM imports the wrapped secret, it is decrypted, and the 32-bit checksum is calculated over the decrypted secret. If this doesn’t match the decrypted checksum, then the secret that the HSM is trying to import comes from a system on a different domain, and an error is returned.
To verify a log generated on another HSM, in the same domain, the host passes to the target HSM the wrapped secret, which the target HSM subsequently decrypts; any records submitted to the target HSM for verification use this secret thereafter.
Importing a log secret from another HSM does not overwrite the target log secret because the operation writes the foreign log secret only to a separate parameter area for the wrapped log secret.
CAUTION: Once an HSM has imported a wrapped log secret from another HSM, it must export and then re-import its own log secret in order to verify its own logs again.
The log capacity of SafeNet HSMs varies depending upon the physical memory available on the device. The SafeNet PCIe HSM and the HSM contained in the SafeNet Network HSM appliance are the SafeNet K6 HSM card. The HSM inside both the SafeNet USB HSM and the SafeNet Remote Backup HSM is the SafeNet G5 HSM module.
The K6 HSM has approximately 16 MB available for Audit logging (or more than 200,000 records, depending on the size/content of each record).
The G5 HSM has approximately 4 MB available for Audit logging (or more than 50,000 records, depending on the size/content of each record).
In both cases, the normal function of Audit Logging is to export log entries constantly to the file system. Short-term, within-the-HSM log storage capacity becomes important only in the rare situations where the HSM remains functioning but the file system is unreachable from the HSM. This would be a rare or unlikely event for an HSM connected to a server or workstation, and almost unheard-of in the closed and hardened environment of a SafeNet Network HSM appliance.
When you perform audit time get you might see a variance of a few seconds between the reported HSM time and the Host time. Any difference up to five seconds should be considered normal, as the HSM reads new values from its internal clock on a five-second interval. So, typically, Host time would show as slightly ahead.
Audit Logging configuration is not removed or reset upon HSM re-initialization. It survives tamper and decommission and factory reset. Logs must be cleared by specific command. Therefore, if your security regime requires decommission at end-of-life, or prior to shipping an HSM, then explicit clearing of HSM logs should be part of that procedure.
This is by design, as part of separation of roles in the HSM. When the Audit role exists, the SO cannot modify the logging configuration, and therefore cannot hide any activity from auditors.
As a general rule, you should not delete a file while it is open and in use by an application. In most systems, deletion of a file is deletion of an inode, but the actual file itself, while now invisible, remains on the file system until the space is cleaned up or overwritten. If a file is in use by an application - such as audit logging, in this case - the application can continue using and updating that file, unaware that it is now in deleted status.
If you delete the current audit log file, the audit logging feature does not detect that and does not create a new file, so you might lose log entries.
The workaround is to restart the pedClient daemon, which creates a new log file.