Towards a Principled Approach for Engineering Privacy by Design
The DOI matches its Crossref record; 21 of the 21 references it cites were found in a registry or an index.
Overview
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
Claims other papers make about this one
Each is checked against this paper’s own text: does it say what the citing paper says it does?
In the citing paper
“The gap between principles and practice is large, and widened by complexity, variability, subjectivity, and lack of standardisation, including variable interpretation of the ‘components’ of each of the ethical principles (Alshammari and Simpson 2017).”
From From What to How: An Initial Review of Publicly Available AI Ethics Tools, Methods and Research to Translate Principles into Practices (2020) · cites this paper as Alshammari and Simpson 2017
Citations
Cites
Information Privacy: Measuring Individuals’ Concerns About Organizational Practices1
Smith, H. J., Milberg, S. J., & Burke, S. J. (1996) · MIS Quarterly · doi:10.2307/249477 · Cited by 2,266
Privacy in Context: Technology, Policy, and the Integrity of Social Life
Nissenbaum, H. (2009) · doi:10.1515/9780804772891 · Cited by 2,129 · cited 5×
“This emphasises the importance of synthesising approaches (such as, for example, the aforementioned taxonomy of privacy [21] and contextual integrity framework [18]) to use reasonable expectations as a baseline during analysis.”
BackgroundMethodInfluentialSolove, D. J. (2006) · University of Pennsylvania Law Review · doi:10.2307/40041279 · Cited by 1,388
Deng, M., Wuyts, K., Scandariato, R., Preneel, B., & Joosen, W. (2011) · Requirements Engineering · doi:10.1007/s00766-010-0115-7 · Cited by 533 · cited 11×
“Finally, LINDDUN supports interaction between privacy requirements and software architectures by providing a catalogue of threat tree patterns to aid in mapping appropriate Privacy-Enhancing Technologies (PETs) onto the identified threat types [10].”
BackgroundMethodInfluentialSpiekermann, S., & Cranor, L. F. (2009) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2008.88 · Cited by 424 · cited 17×
“The Framework for Privacy-Friendly System Design (PFSD) was developed by Spiekermann and Cranor to provide a comprehensive view of privacy engineering [23].”
BackgroundMethodInfluentialSchaar, P. (2010) · Identity in the Information Society · doi:10.1007/s12394-010-0055-x · Cited by 387 · cited 1×
“In addition, it is essential to analyse privacy and functional requirements from the early stages of the design process to determine the relevant and necessary data for achieving given functionality [Sch10].”
BackgroundGürses, S. F., Troncoso, C., & Díaz, C. (2011) · Lirias · Cited by 386
Hoepman, J.-H. (2014) · IFIP Advances in Information and Communication Technology · doi:10.1007/978-3-642-55415-5_38 · Cited by 318
Addressing privacy requirements in system design: the PriS method
Kalloniatis, C., Kavakli, E., & Gritzalis, S. (2008) · Requirements Engineering · doi:10.1007/s00766-008-0067-3 · Cited by 269 · cited 5×
“Specifically, we analyse the Framework for PrivacyFriendly System Design (PFSD) [23], LINDDUN [10] and the PriS method [16], which were previously analysed against a conceptual framework for privacy requirements engineering by Beckers [1].”
BackgroundMethodInfluentialThe challenges of privacy by design
Spiekermann, S. (2012) · Communications of the ACM · doi:10.1145/2209249.2209263 · Cited by 177 · cited 2×
“Privacy is a ‘fuzzy’ concept; consequently, it is difficult to protect [22].”
BackgroundPrivacy Engineering: Shaping an Emerging Field of Research and Practice
Gürses, S. F., & Álamo, J. M. D. (2016) · IEEE Security & Privacy · doi:10.1109/msp.2016.37 · Cited by 149
PRIPARE: Integrating Privacy Best Practices into a Privacy Engineering Methodology
Notario, N., Crespo, A., Martín, Y.-S., Álamo, J. M. D., Métayer, D. L., Antignac, T., Kung, A., Kroener, I., & Wright, D. (2015) · IEEE Security and Privacy Workshops (SPW) · doi:10.1109/spw.2015.22 · Cited by 144 · cited 1×
“Such impact can be measured either financially or as personal and societal impacts [19].”
BackgroundA Critical Analysis of Privacy Design Strategies
Colesky, M., Hoepman, J.-H., & Hillen, C. (2016) · 2016 IEEE Security and Privacy Workshops (SPW) · doi:10.1109/spw.2016.23 · Cited by 135 · cited 2×
“The privacy design strategies of, for example, [15] and [9] specify architecture goals that realise a set of protection goals — which are derived from privacy principles and data protection regulations — to achieve a certain level of privacy protection; on the other hand, our strategies are a set of design objectives”
BackgroundMethodPrivacy by Design [Leading Edge]
Cavoukian, A. (2012) · IEEE Technology and Society Magazine · doi:10.1109/mts.2012.2225459 · Cited by 127 · cited 1×
“In 2010 Privacy by Design was recommended as an international privacy standard by the participants of the 32nd International Conference of Data Protection and Privacy Commissioners in Jerusalem [5].”
BackgroundProtection Goals for Privacy Engineering
Hansen, M., Jensen, M., & Rost, M. (2015) · 2015 IEEE Security and Privacy Workshops · doi:10.1109/spw.2015.13 · Cited by 123 · cited 4×
“In this regard, unlinkability, transparency and intervenability as proposed in [14] need to be adopted to complement the security protection goals of confidentiality, integrity and availability.”
BackgroundInfluentialThe state of the art in privacy impact assessment
Wright, D. (2012) · Computer Law & Security Review · doi:10.1016/j.clsr.2011.11.007 · Cited by 95 · cited 1×
“Therefore, Wright [Wri12] argues that a PIA is not only a systematic tool, but it is also an ongoing process.”
BackgroundThe Privacy Engineer’s Manifesto: Getting from Policy to Code to QA to Value
Dennedy, M. F., Fox, J., & Finneran, T. R. (2014) · Apress eBooks · doi:10.1007/978-1-4302-6356-2 · Cited by 54
Comparing Privacy Requirements Engineering Approaches
Beckers, K. (2012) · International Conference on Availability, Reliability and Security (ARES) · doi:10.1109/ares.2012.29 · Cited by 45 · cited 2×
“To be holistic, there is a need to adopt universal privacy principles that provide high privacy standards [8] to meet stakeholders’ expectations, which may exceed legal requirements in some jurisdictions [1].”
BackgroundMethodPrivacy by design: moving from art to practice
Shapiro, S. S. (2010) · Communications of the ACM · doi:10.1145/1743546.1743559 · Cited by 36 · cited 1×
“Privacy by Design [4] has been advocated as a response to these challenges.”
BackgroundPEARs: Privacy Enhancing ARchitectures
Kung, A. (2014) · Lecture notes in computer science · doi:10.1007/978-3-319-06749-0_2 · Cited by 27 · cited 1×
“Many privacy-preserving solutions have a significant architectural impact [17] and are typically not accompanied by design guidelines to mitigate these impacts.”
BackgroundEnhancing Privacy by Design from a Developer’s Perspective
Bier, C., Birnstill, P., Krempel, E., Vagts, H., & Beyerer, J. (2014) · Lecture notes in computer science · doi:10.1007/978-3-642-54069-1_5 · Cited by 7 · cited 10×
“‘Privacy by Default’ implies that the default setting is considered to be an adequate level of privacy protection; in practice, however, users are not likely to restrict themselves to a default operational mode [2].”
BackgroundInfluential
Research works printed but not linked: 2
- The European Union: Official Journal of the European Union: General Data Protection Regulation (2016). http://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ:L:2016:119:FULL&from=EN
- United States Department of Health, Education, Welfare: Secretary’s Advisory Committee on Automated Personal Data Systems: Records, Computers and the Rights of Citizens: Report. [Cambridge? Mass.]: [MIT Press], Cambridge (1973)
Cited by
Morley, J., Floridi, L., Kinsey, L., & Elhalal, A. (2020) · Science and Engineering Ethics · doi:10.1007/s11948-019-00165-5 · Cited by 882
Ethics as a Service: A Pragmatic Operationalisation of AI Ethics
Morley, J., Elhalal, A., Garcia, F., Kinsey, L., Mökander, J., & Floridi, L. (2021) · Minds and Machines · doi:10.1007/s11023-021-09563-w · Cited by 266
“…by identifying the methods and tools already available to help AI developers, engineers, and designers (collectively ‘practitioners’ (Orr & Davis, 2020)) know not only what to do or not to do, but also how to do it, or avoid doing it, by adopting an ethical perspective (Alshammari & Simpson, 2017).”
MethodFrom ethical AI frameworks to tools: a review of approaches
Prem, E. (2023) · AI and Ethics · doi:10.1007/s43681-023-00258-9 · Cited by 242
Operationalising AI governance through ethics-based auditing: an industry case study
Mökander, J., & Floridi, L. (2023) · AI and Ethics · doi:10.1007/s43681-022-00171-7 · Cited by 129
“In contrast, EBA procedures that aim at risk assurance should be adapted locally to reflect how respective business areas understand risk.”
BackgroundMorley, J., Floridi, L., Kinsey, L., & Elhalal, A. (2021) · Philosophical studies series · doi:10.1007/978-3-030-81907-1_10 · Cited by 224
Metadata
- Authors
- Alshammari, M., & Simpson, A.
- Affiliations
- University of Oxford (GB)
- Corresponding author
- Alshammari, Majed
- ORCID
- Simpson, Andrew
- Venue
- Lecture Notes in Computer Science
- Publisher
- Springer International Publishing
- Published
- 2017
- Pages
- 161-177
- ISSN
- 0302-9743 (ISSN-L)
- 1611-3349
- OpenAlex
- W2635353767
- Cited by
- 68
- References
- 20
- Citations by year
- 2026: 1 · 2025: 6 · 2024: 18 · 2023: 9 · 2022: 5 · 2021: 9 · 2020: 3 · 2019: 8 · 2018: 8 · 2017: 1
- FWCI
- 17.41
- Type
- conference paper
- Language
- en
- Open access
- closed
- Locations
- Lecture notes in computer science (publishedVersion)
- Topics
- Social Sciences › Sociology and Political Science › Privacy, Security, and Data Protection
- Physical Sciences › Computer Science › Artificial Intelligence › Privacy-Preserving Technologies in Data
- Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
- Keywords
- privacy by design, privacy engineering, privacy violations, privacy harms, design decisions, privacy principles, information and communication technologies
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.