San Francisco, CA
May 23, 2013 to May 24, 2013
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/SPW.2013.26
Accountability is a requirement to be included in the initial design phase of systems because of its strong impact on log architecture implementation. As an illustration, the logs we examine here record actions by data controllers handling personally identifiable information to deliver services to data subjects. The structures of those logs seldom consider 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 architecture are nontrivial and should be made from the design stage on. Four categories of situations for which straightforward solutions are problematic are presented. Our contribution 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.
PPL, Accountability, Security Policy, Privacy
Denis Butin, Marcos Chicote, Daniel Le Metayer, "Log Design for Accountability", SPW, 2013, 2013 IEEE CS Security and Privacy Workshops (SPW2013), 2013 IEEE CS Security and Privacy Workshops (SPW2013) 2013, pp. 1-7, doi:10.1109/SPW.2013.26