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 escribed on Different Audit Trails solutions).
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.