Child pages
  • Different Audit Trails solutions
Skip to end of metadata
Go to start of metadata

Discription of different audit trail solutions, where only one is implemented as reference implementation
There three very different ways to implement audit trail solutions, these are

It is the third one with an Audit Trails Service that are part of the reference implementation.

Individual and independent ensurance of audit trails

In this case all clients, pillars and services are individually responsible for ensurance of the audit trail. In this case there will most likely only be exchanged audit trails as part of the Get Audit Trails operation.

This solution assumes that all components in the system can provide audit trails information to Get Audit Trails function, if requested.

Benefits
  • There can be different levels of securing the audit trails for different Clients and Pillars
Disadvantages
  • Complexities of ensurance of audit trails must be in all components
  • 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

In this case all clients, pillars and services individually ensure the audit trail by putting it to the same Special Audit trails Bit Repository Collection.

The Get Audit Trails function could be implemented by accessing the data directly via the Special Audit trails Bit Repository Collection.

Benefits
  • All audit trail is ensured together and in the same way
Disadvantages
  • Complexities of ensurance of audit trails must be in all components
  • 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 collects and ensures audit trails via Special Audit trails Bit Repository Collection

Audit trail service collects audit trails and ensure the audit trails via a Special Audit trails Bit Repository Collection.

The Get Audit Trails function could be implemented by accessing the data directly via the Special Audit trails Bit Repository Collection, however the Get Audit Trails function will be more simple by just letting it ask the service.

Benefits
  • Complexity of collection and ensurance of audit trails are isolated to this service
  • All audit trail is ensured together and in the same way
Disadvantages
  • may overload coordination layer with single FileID audit trails requests to all components in the system
  • Delayed view of audit trail, because audit trail must be pulled before it can be delivered
  • 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.
  • No labels