Towards a privacy debt

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 u...

Full description

Saved in:
Bibliographic Details
Published inIET software Vol. 15; no. 6; pp. 453 - 463
Main Authors Larrucea, Xabier, Santamaría, Izaskun, Graña Romay, Manuel
Format Journal Article
LanguageEnglish
Published Hindawi-IET 01.12.2021
Subjects
data privacy
privacy
Privacy Debt
security
security of data
software engineering
Technical Debt
Online AccessGet full text

Cover

More Information
Summary: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.
ISSN:1751-8806
1751-8814
DOI:10.1049/sfw2.12044