Collecting and securing audit trails and making them available for the Get Audit Trails functionality
The audit trail service is a Reference services which will be part of the reference implementation.
The audit trail service has the responsibilities of collecting and securing audit trails and making them available for the Get Audit Trails functionality.This means that the Get Audit Trails client in most cases can be siplified to just ask this audit trails service for the requested audit trails. Furthermore all ensurance of audit trails are placed as part of the service instead of as part of individual components in the system.
The Audit Trails Service collects audit trails from components in the bit repository, i.e. audit trails information from pillars, clients (e.g. the integrity client), bus (monitoring service), alarms (Alarms service).
The Audit Trails Service secure audit trails by putting them into a Special Audit trails Bit Repository Collection which only contain audit trail information for a file bit repository collection.
The approach used for the reference client/service will include collection of audit trails as described under Get Audit Trails and make them available on request from the Get Audit Trails client.
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 Special Audit trails Bit Repository Collection
The Get Audit Trails function can access the data via the Special 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 Special 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.
Audit trails service pulls audit trails and does the ensurance via Special Audit trails Bit Repository Collection
Asks the pillars and other clients for audit trails to secure audit trails from pillars and other clients.
Benefits
Disadvantages
- Delayed view of audit trail, because audit trail must be pulled before it can be delivered