What is a logbook?

Password Safe logs any user interaction. These entries can be viewed and filtered via the module of the same name. In this way, at a central location, it is possible at any time to understand which user has made exactly what changes. This module is (theoretically) classified as uncritical since the employee has only access to those logbook entries to which he is actually entitled. The configuration of visibility is explained in a similar way to the other modules in one place.

Use of the filter in the logbook

As is the case in all other modules, you can also use the filter in the logbook to limit the number of displayed elements based on the defined criteria. In the following example, the user is searching for logbook entries relating to the object type “Password” and which match the event criteria “Change”. In short: The entries are being filtered based on changes to passwords.

Grouping in the logbook

The resulting list can also be grouped together by dragging and dropping column headers. The following shows the entries being grouped together based on the column “Computer user”. The filtered results correspond to changes to passwords carried out by the computer user “administrator”.

Revision-safe archiving

In Password Safe, an uncompromising method is used when handling the logbook. Every change of state is recorded and saved in the MSSQL database. There are no plans to enable the selective triggering of logbook entries to be defined. Revision-safe archiving and thus the audit-proof traceability of changes can only be guaranteed using this approach.

Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.