# Privacy Goals for the Data Lifecycle
## 6 Step 3-Aligning the Privacy Goals to GDPR and the Data Lifecycle
\begin{table}
\begin{tabular}{p{42.7 pt} p{113.8 pt} p{113.8 pt}} \hline \hline
**No.** & **Goal** & **Mentioned in following Frameworks** & **Meaning** \\ \hline
1. & Confidentiality & LINDDUN, IRIS (CAIRIS), ICPPS, ENISA-ISO mention but not as a goal & _Ensuring data is usable on demand and accessible to authorised stakeholders._ \\ \hline
2. & Integrity & LINDDUN, IRIS (CAIRIS), ICPPS-ENISA, PriS-ISO mention but not as a goal & _Ensuring non-repudiation and reliability for each piece of data, i.e., processing accurate, authentic, and unmodified data._ \\ \hline
3. & Availability & LINDDUN, IRIS (CAIRIS), ICPPS, ENISA-ISO mention but not as a goal & _Ensuring data is usable on demand and accessible to authorised stakeholders._ \\ \hline
4. & Unlinkability & PriS, IRIS (CAIRIS), [PERSON] and [PERSON] 2010, ENISA, ICPPS & _Ensuring data cannot be sufficiently distinguished to linked across platforms or domains with similar context or purpose._ \\ \hline
5. & Unobservability & PriS, IRIS (CAIRIS), [PERSON] and [PERSON] 2010-ICPPS mentions but not as a goal & _Ensuring no unauthorised party can observe what data or service is being utilised or performed, even if they gain access to the system._ \\ \hline
6. & Anonymity & LINDDUN, PriS, IRIS (CAIRIS), [PERSON] and [PERSON] 2010, ENISA-ICPPS and ISO mention but not as a goal & _Offuscating links between data and identity, i.e., the ability to distinguish any one individual from the data.._ \\ \hline
7. & Pseudonymity & LINDDUN, PriS, IRIS (CAIRIS), [PERSON] and [PERSON] 2010-ENISA, ICPPS and ISO mention but not as a goal & _Replacing identifying data with pseudonyms ensuring any links to original data cannot be made by unauthorised parties.._ \\ \hline
8. & Intervenability & ENISA 2014, ICPPS & _Enabling data subject access and/or supervisory authority access to affect action on the records (e.g., to correct inaccuracies, request modification and/or deletion). In that way it can be seen as a safeguarding measure that must be included within any process or system involving personal data._ \\ \hline
9. & Transparency & ENISA 2014, ICPPS- PriS and ISO mention but not as a goal & _Openness-Providing assurance, accountability and traceability for internal and external stakeholders._ \\ \hline
10. & Authentication & LINDDUN, PriS - Pfitzmann and Hansen, ICPPS and ENISA mention but not as a goal & _Verifying the identity of a process, device or user goal_ \\ \hline
11. & Undetectability & [PERSON] and Hansen 2010-ICPPS & _Ensuring data is anonymised so that anonymity and undetectability of the individual is preserved._ and _Ensuring data cannot be sufficiently distinguished to establish whether it exists or not._ \\ \hline
12. & Accountability & LINDDUN, IRIS (CAIRIS), ENISA, Pitzmann and Hansen, ICPPS and ISO29100 mention but not as a goal & _Having someone designated as ‘accountable’-ensuring that someone takes responsibility for how data is processed and that, for example, privacy goals are followed and adhered to_ \\ \hline
13. & Identification & PriS & _This concerns user identifying themselves within a system_ \\ \hline
14. & Data Protection & PriS & _Ensuring personal data is appropriately processed and stored_ \\ \hline
15. & Authorisation & LINDDUN, PriS, IRIS (CAIRIS) mention but not as goal & _Ensuring user accessing a system or process has authority to do so._ \\ \hline
16. & Non-repudiation & LINDDUN, ENISA mentions this as a threat, not a privacy goal - ICPPS and IRIS (CAIRIS) mention but not as goal & _Proof of action, e.g., making sure that a user who processes an item of data cannot at a later stage deny having processed that item of data._ \\ \hline \hline \end{tabular}
\end{table} 
Table 1: Privacy Goals Compared incl. Definitions. will need to be made around what data to collect, how long data will be stored for, why etc.