Unalterable log Module

Introduction

Unalterable archive is a feature that helps in ensuring that the preserved data is non-rewritable, which helps in maintain safety and security of confidential data. Maintenance of important data is certainly one of the primary work that needs to be done by an organisation without allowing any error. Hence, Tactic provides a better and more secure interface to store non-rewritable data within the software with the assistance of unalterable log module. Unalterable log module helps the users in managing certain business events in a batter and more organised manner. The archive provides a table of chain events that can be read and exported.

Installation

There is no need of installing this module, as it is already included within Tactic services.

Setup

For using this module the users need to enable it by using an administrator account. The menu options for activating this module are: Home –> Setup – > Module. The users then need to click on Activate. The modules will be activated after completing this step. The settings icon File:Cog.png will be visible at the end of the module box, the users can click in that to access setup.

Importance of unalterable logs

Apparently this is not a very functional module, which can help the users in cutting down their manual effort. However, this module can be helpful in tracing certain management actions in the form of a log or a table. Record and registration of the payment related actions is one of the primary action that is traced by this module. This module also records the activation and the deactivation of unalterable long module as well. Unalterable log helps in reducing the risk of unnecessary modifications that can create huge issues within an organisation. The unalterable logs cannot be deleted or modified, it is protected for ensuring a successful record of management actions. The log record is protected by a checksum, which is depended on the data of record. The checksum can be made invalid for stopping the data to be modified. The checksums are chained with the record of previous data, hence, it is almost impossible to hack into the checksum system chain and modify a record. The users can also assign a program signature for validating a program code. It can also be used a verification tool to verify the identification of a file that has been modified.

Finding archived logs

The users can go to the home menu then to modules and choose the option of module unalterable log to read the archived logs. The users can filter the log based on dates and then export those into a CSV file.