31,003
edits
Module Unalterable Archives - Logs: Difference between revisions
Jump to navigation
Jump to search
m
→Usage
m (→Usage) Tag: 2017 source edit |
m (→Usage) Tag: 2017 source edit |
||
| Line 36: | Line 36: | ||
*Each checksum is chained with the checksum of the previous record, so that it is not possible to hack a checksum chain of a record without invalidating the previous record in turn. | *Each checksum is chained with the checksum of the previous record, so that it is not possible to hack a checksum chain of a record without invalidating the previous record in turn. | ||
*A program signature can be defined to validate a state of the program code and a verification tool can be used to identify if a file has been modified (e.g. as a result of a server hack) making it detectable if computer code has been modified in an attempt to bypass the unalterable log mechanism. | *A program signature can be defined to validate a state of the program code and a verification tool can be used to identify if a file has been modified (e.g. as a result of a server hack) making it detectable if computer code has been modified in an attempt to bypass the unalterable log mechanism. | ||
==Reading archived logs== | |||
To browse the list of archived event, a tool is available into menu Home - Modules - Modules Unalterable Archives/Log - Tab "Unalterable Logs". You can filter on a date and export the list of events into a CSV file. | |||