Log Design for Accountability
Abstract
The position put forward in this paper is that accountability is a requirement to be taken into account from the initial design phase of a system because of its strong impact on log architecture implementation. As an illustration, the logs we consider here record actions by data controllers handling personally identifiable information to deliver services to data subjects. The structures of those logs seldom take into account requirements for accountability, preventing effective dispute resolution. We address the question of what information should be included in logs to make their a posteriori compliance analysis meaningful. Real-world scenarios are used to show that decisions about log architectures are nontrivial and should be made from the design stage on. Three categories of situations for which straightforward solutions are problematic are presented. Our discussion shows how log content choices and accountability definitions mutually affect each other and incites service providers to rethink up to what extent they can be held responsible. These different aspects are synthesized into key guidelines to avoid common pitfalls in accountable log design. This analysis is based on case studies performed on our implementation of the PPL policy language.
Origin : Files produced by the author(s)
Loading...