Audit Trails Service

Securing audit trails and making them available for the Get Audit Trails functionality
The Get Audit Trails Client collects audit trails from different parts of the bit repository, i.e. audit trails information from pillars, clients (especially the integrity client), bus, alarms. These audit trails must be secured either on individual initiative or by a dedicated client.

There are a number of approches to secure audit trails and make them available.

Individual and independent ensurance of audit trails by the individual pillars and clients
Individual ensurance of audit trails via common Audit trails Bit Repository Collection
Audit trail service pulls audit trails and doing the ensurance via Audit trails Bit Repository Collection

The approach used for the reference client/service is the third where

the spike will include collection and processing of audit trails as described under Get Audit Trails
collection will later be moved to the service, ehich also will do the ensurance of the audit trails (e.g. GetAuditTrails will have to get them from teh Service)
...

An overview of how the Alarm Service interchange information with Monitoring service and Audit trails is given in Reference services.

Individual and independent ensurance of audit trails by the individual pillars and clients

This must include functionality to provide audit trails to Get Audit Trails function, if requested.

Benefits

Their can be different levels of securing the audit trals for dfifferent Clients and Pillars

Disadvantages

All clients and pillars must be available in order to get a full audit trail.

Individual ensurance of audit trails via common Audit trails Bit Repository Collection

The Get Audit Trails function can access the data via the Audit trails Bit Repository Collection.

The approach described here is that audit trails are ensured by letting pillars and clients secure copies on other pillars according to a Audit trails Bit Repository Collection .

Benefits

Disadvantages

There may be issues on the format which the data is stored in, since a media migration can result in changes to a lot of FileID audit trails, i.e. it can be storage consuming to store it in the required form.