Secure logging for host security module
AssigneeInternational Business Machines Corporation
InventorsRichard V. Kisley, Mark D. Marik, Michael J. Miele, Tamas Visegrady
Life of this patent
Estimating the term…
Abstract
Embodiments include method, systems and computer program products for secure logging of host security module. In some embodiments, an event may be received. The event may include data to be written to a secure log file. A hash may be generated using data of the event. The hash may be stored in a first field of an event record associated with the event. The event record may be stored in the secure log file. The hash may be stored in a second field of a next event record in the secure log file.
Claims17
A computer-implemented method for secure logging on a host security module (HSM), the method comprising:
- receiving an event, wherein the event comprises data to be written to a secure log file;
- generating a hash using data of the event;
- storing the hash in a first field of an event record associated with the event, wherein the event record is stored in the secure log file;
- storing the hash in a second field of a next event record in the secure log file;
- receiving a request from a user associated with a first user role to clear a set of event records from the secure log file;
- verifying that the set of event records has been retrieved at least once by analyzing metadata associated with each event record of the set of event records to be cleared;
- updating metadata associated each event record of the set of event records;
- receiving a second request from a second user associated with a second user role to clear the set of event records from the secure log file;
- verifying the data received in the second request by analyzing the metadata associated with each event record of the set of event records;
- and
- removing the set of event records from the secure log file.
A computer program product comprising a storage medium readable by a processing circuit and storing instructions for execution by the processing circuit for performing a method comprising:
- receiving an event, wherein the event comprises data to be written to a secure log file;
- generating a hash using data of the event;
- storing the hash in a first field of an event record associated with the event, wherein the event record is stored in the secure log file;
- storing the hash in a second field of a next event record in the secure log file;
- receiving a request from a user associated with a first user role to clear a set of event records from the secure log file;
- verifying that the set of event records has been retrieved at least once by analyzing metadata associated with each event record of the set of event records to be cleared;
- updating metadata associated each event record of the set of event records;
- receiving a second request from a second user associated with a second user role to clear the set of event records from the secure log file;
- verifying the data received in the second request by analyzing the metadata associated with each event record of the set of event records;
- and
- removing the set of event records from the secure log file.
A system, comprising:
- a processor in communication with one or more types of memory, the processor configured to:
- receive an event, wherein the event comprises data to be written to a secure log file;
- generate a hash using data of the event;
- store the hash in a first field of an event record associated with the event, wherein the event record is stored in the secure log file;
- store the hash in a second field of a next event record in the secure log file;
- receive a request from a user associated with a first user role to clear a set of event records from the secure log file;
- verify that the set of event records has been retrieved at least once by analyzing metadata associated with each event record of the set of event records to be cleared;
- update metadata associated each event record of the set of event records;
- receive a second request from a second user associated with a second user role to clear the set of event records from the secure log file;
- verify the data received in the second request by analyzing the metadata associated with each event record of the set of event records;
- and
- remove the set of event records from the secure log file.
Dependencies are inferred from the claim text.