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 (other possible implementations are described on Different Audit Trails solutions).
The audit trail service has the responsibilities of collecting and securing audit trails and making them available as a webservice.This means that Audit Trails clients 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.
The Audit Trails Service collects audit trails from pillars in the bit repository.
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.
See [
Processes in the Audit Trails Service
There are three main processes:
* Collection of audit trails
* Ensurance of audit trails
* Responses to [BITMAG:Get Audit Trails] requests
The service may have an internal database to collect the audit trail information in order to be able to secure the audit trails in chunks and in order to be able to answer on requests without accessing the [BITMAG:Special Audit trails Bit Repository Collection]