Privacy by Design: A Counterfactual Analysis of Google and Facebook Privacy Incidents
Privacy by Design: A Counterfactual Analysis of Google and Facebook Privacy Incidents
复制标题
隐私设计：谷歌和 Facebook 隐私事件的反事实分析
DOI：
10.2139/ssrn.2128146
复制
发表时间：
2012
期刊：
影响因子：
--
通讯作者：
Nathaniel Good
中科院分区：
文献类型：
--
作者：
I. Rubinstein;Nathaniel Good
国内外的监管机构已经将“设计隐私”作为其正在进行的现行隐私法修订的关键要素。其基本思想是在创建软件产品和服务时“内置”隐私（以公平信息实践或FIP的形式）。但FIP不是自动执行的。相反，隐私设计需要将FIP转化为工程和可用性原则和实践。确保软件包含FIP和任何相关公司隐私指南中描述的广泛隐私目标的最佳方法是将其包含在软件“需求”的定义中。制定软件设计规范或需求的一个主要组成部分是使其具体，具体，最好与度量相关联。同样重要的是开发软件界面和其他视觉元素，这些元素关注最终用户的目标，需求，需求和限制。这篇文章首次全面分析了与隐私相关的工程和可用性原则。在相关技术文献的基础上，推导出少量相关原则，并以最近发生的十起涉及谷歌和Facebook的隐私事件为例进行说明。这篇文章的结论是，所有十个隐私事件都可以通过这些隐私工程和可用性原则的应用而避免。此外，我们认为，设计有效的隐私的主要挑战是没有设计准则。相反，这是商业问题往往与隐私问题竞争并掩盖隐私问题。因此，解决方案在于为公司提供关于适用设计原则以及如何最好地将其纳入软件开发过程的更清晰的指导。在如何平衡隐私与商业利益方面也需要更多的指导，而且还必须有监督机制。
Regulators here and abroad have embraced “privacy by design” as a critical element of their ongoing revision of current privacy laws. The underlying idea is to “build in” privacy (in the form of Fair Information Practices or FIPs) when creating software products and services. But FIPs are not self-executing. Rather, privacy by design requires the translation of FIPs into engineering and usability principles and practices. The best way to ensure that software includes the broad goals of privacy as described in the FIPs and any related corporate privacy guidelines is by including it in the definition of software “requirements.” And a main component of making a specification or requirement for software design is to make it concrete, specific and preferably associated with a metric. Equally important is developing software interfaces and other visual elements that are focused around end-user goals, needs, wants and constraints. The Article offers the first comprehensive analysis of engineering and usability principles specifically relevant to privacy. Based on the relevant technical literature, it derives a small number of relevant principles and illustrates them by reference to ten recent privacy incidents involving Google and Facebook. The Article concludes that all ten privacy incidents might have been avoided by the application of these privacy engineering and usability principles. Further, we suggest that the main challenge to effective privacy by design is not the lack of design guidelines. Rather, it is that business concerns often compete with and overshadow privacy concerns. Hence the solution lies in providing firms with much clearer guidance about applicable design principles and how best to incorporate them into their software development processes. Greater guidance is also needed for how to balance privacy with business interests, and there must be oversight mechanisms as well.