# Privacy Goals for the Data Lifecycle
## Appendix A \begin{tabular}{l l l l l}
**No.** & **Goal** &
\begin{tabular}{l} **Mentioned in Following** \\ **Frameworks** \\ \end{tabular} & **Privacy Meaning** & **Inclusion/Exclusion** \\ \hline \multirow{3}{*}{1.} & \multirow{3}{*}{Confidentiality} & LINDDUN, IRIS (CAIRIS), & _Ensuring data is usable on_ & Part of the CIA triangle (Confidentiality, \\  & ICPPS, ENISA - ISO & _demand and accessible to_ & Integrity and Availability), widely accepted as \\  & & mention but not as a goal & _authorised stakeholders._ & standard practice to include for both security \\ \hline \multirow{3}{*}{2.} & \multirow{3}{*}{Integrity} & LINDDUN, IRIS (CAIRIS), & _Ensuring non-repudiation and_ & \\  & ICPPS - ENISA, PriS - ISO & _i.e., processing accurate,_ & Confidentiality, Integrity and Availability form \\  & & mention but not as a goal & _authorised data._ & part of the CIA triad in security terms [55]. \\ \hline \multirow{3}{*}{3.} & \multirow{3}{*}{Availability} & LINDDUN, IRIS (CAIRIS), & _Ensuring data is usable on_ & Part of the CIA triad [55]. ENISA, [PERSON] et al. and LINDDUN discuss these concepts as 'classic' security properties or protection goals with \\  & & ICPDS, ENISA - ISO & _demand and accessible to_ & Availability, however, has a slightly different \\  & & mention but not as a goal & _authorised stakeholders._ & meaning in terms of privacy. In security terms \\  & & & & this partly refers to the availability of the system \\  & & & & (e.g., uptime) and partly availability of the data. \\  & & & & In privacy terms, this relates to the availability of the data and/or being able to access the data as \\  & & & & required (assuming, of course, the user is \\  & & & authorised to access the data). Included as a \\ \hline \multirow{3}{*}{4.} & \multirow{3}{*}{Unlinkability} & PriS, IRIS (CAIRIS), & _Ensuring data cannot be_ & ENISA considers this one of the \"privacy \\  & & [PERSON] and [PERSON] 2010, & _linked across platforms or_ & refore to this as one of the data protection goals, \\ \cline{1-1}  & & ENISA, ICPPS & _domains with similar context_ & linking this to necessity and data minimisation. \\ \cline{1-1} \end{tabular}   
\begin{tabular}{c c c c c} \hline \hline
**No. ** & **Goal** & **Mentioned in Following Frameworks** & **Privacy Meaning** & **Inclusion/Exclusion** \\ \hline  & & & & Included as 7-DL Privacy Goal with \\  & & & & _Undetectability_ (see Line 11). In terms of data, \\  & & & both are mechanisms for hiding information to \\  & & & facilitate the unobservability and undetectability \\  & & & of the data concerning the individual data \\  & & & & subject. It could be argued these should be split \\
5. & Unobservability & [PERSON] and [PERSON] 2010- & _Ensuring no unauthorised party can observe what data or service is bring utilised or performed, even if they gain_ & into separate goals. The reason these two \\  & & & _service is bring utilised or_ & have been grouped in 7-DL is because, \\  & & & _performed, even if they gain_ & unobservability refers to whether the users' \\  & & & _access to the system._ & actions (e.g., sending or receiving) are observable \\  & & & & and ensuring that the data itself cannot be \\  & & & & observed either. This, arguably, includes \\  & & & & undetectability as, if an attacker or unauthorised \\  & & & person, cannot observe then they cannot detect, \\  & & & thus, these terms have been grouped together. \\ \hline  & & & & GDPR discusses anonymisation in relation to \\
6. & Anonymity & LINDDUN, PriS, IRIS & _Olfuscating links between data and identity, i.e., the ability to_ & different communication and data processing activities within system but then goes on to say \\  & & and ISO mention but not as a goal & _defining identifying data_ & that, once data has been anonymised, it is no \\  & & & _from the data._ & longer subject to data protection regulation \\  & & & & (Recital 26). Included as a Privacy Goal.