| Excerpt |
|---|
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.
...
The Get Audit Trails function can access the data via the Audit trails SLA.
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 SLA .
Benefits
...
- Delayed view of audit trail, because audit trail must be pulled before it can be delivered
The Get Audit Trail Client collects audit trails from different parts of the bit repository, i.e. audit trails information from pillars, clients, bus, alarms. These audit trails must therefore be secured either on individual initiative or by a dedicated client. The approach described here is that audit trails are ensured by letting pillars and clients secure copies on other pillars according to a Log-SLA. Especially the integrity client is important here.
...
| Child pages (Children Display) | ||||||||
|---|---|---|---|---|---|---|---|---|
|