Towards a privacy debt

Xabier Larrucea*, Izaskun Santamaría, Manuel Graña Romay

*Corresponding author for this work

Research output: Contribution to journalArticlepeer-review

3 Citations (Scopus)

Abstract

This study argues the difference between security and privacy and outlines the concept of Privacy Debt as a new Technical Debt. Privacy is gaining momentum in any software system due to mandatory compliance with respect to laws and regulations. There are several types of technical debts within the umbrella of software engineering, and most of them arise during different phases of software development. Several research studies have been focussed on highlighting different types of technical debts. However, authors introduce Privacy Debt as a particular technical debt focussed on privacy management and linked to a perturbative method. Privacy must be considered not only as technical debt requirements but also at design and deployment phases, among others. In addition, this method is illustrated with a use case.

Original languageEnglish
Pages (from-to)453-463
Number of pages11
JournalIET Software
Volume15
Issue number6
DOIs
Publication statusPublished - Dec 2021

Keywords

  • Privacy Debt
  • Technical Debt
  • data privacy
  • privacy
  • security
  • security of data
  • software engineering

Fingerprint

Dive into the research topics of 'Towards a privacy debt'. Together they form a unique fingerprint.

Cite this