Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Securing audit trails and making them available for the Get Audit Trails functionality

  • Letting each client and pillar ensure their audit trails individually, and including functionality to provide audit trails to Get Audit Trails function
  • Letting each client and pillar ensure their audit trails via a specific sub-SLA, which the Get Audit Trails function can access directly

To support securing of audit trails we use the PutFile functionality along with special AuditTrail-SLAs and to access logs we use the GetFile functionality along with the special AuditTrail-SLAs.The GetAuditTrails Client provides the GetAuditTrail functionality to the user.

A special Audit Trails Servcie is responsible for securing audit trails is not in the illustration but is also a possibility.

which asks the pillars and other clients for logs to secure or receives request to secure audit trails from pillars and other clients.

  • No labels