# A Perfect Match: Converging and Automating Privacy and Security Impact Assessment On-the-Fly
## 5 Case Study for the Healthcare Sector
### Assessment Results
\begin{table}
\begin{tabular}{c c c c c c c c c c c} \hline  & & & \begin{tabular}{c} **Vulnerab.** \\ \end{tabular} & \begin{tabular}{c} **Asset** \\ \end{tabular} & \begin{tabular}{c} **Vuln.** \\ \end{tabular} & \begin{tabular}{c} **Level** \\ **Type** \\ \end{tabular} & \begin{tabular}{c} **Scope** \\ **of Impact** \\ \end{tabular} & \begin{tabular}{c} **Data** \\ **of Impact** \\ \end{tabular} & \
\begin{tabular}{c} **Privacy** \\ **Type** \\ \end{tabular} &
\begin{tabular}{c} **Privacy** \\ **Impact** \end{tabular} \\ \hline
**ID-01** & **SQLServer** & **Vulnerability** & **Character.**1  & **Sensit.** & **Type** \\ \hline
**ID-02** & **SQLServer** & **VUE-202-11898 & 6.4 & VH & Gain Info & VH (7.0) & All (1.5) & Sensitive (1.5) & VH (10) & VH (8.8) \\
**ID-02** & Glucose Meter & **CVE-201-10964** & 5.8 & H & Byruss Auth. & H (4.5) & Single (0.5) & Sensitive (1.5) & H (6.5) & H (6.3) \\
**ID-03** & Blood P. Mon & **CVE-201-11579** & 4.8 & H & Gain Info & VH (7.0) & Single (0.5) & Sensitive (1.5) & VH (9) & H (7.6) \\
**ID-04** & **PC001** & **CVE-2017-13993** & 9.3 & H & Code Exec. & VH (7.0) & Single (0.5) & Sensitive (1.5) & VH (9) & VH (9.1) \\
**ID-05** & **PC0001** & **CVE-2019-1343** & 7.1 & H & DoS & L (1.0) & Single (0.5) & Sensitive (1.5) & L (3) & M (4.4) \\
**ID-06** & **PC0002** & **CVE-2019-5831** & 6.8 & H & DoS & L (1.0) & Single (0.5) & Personal (1) & L (2.5) & L (3.9) \\ \hline \end{tabular}
\end{table} 
Table 6: Use case threats, assets and privacy scores association. By taking a closer look at the scores of Table 6, one can notice that for ID-01, the SQLServer can be affected by a vulnerability that can lead to leak of information. Such a type of threat against a sensitive asset (in terms of privacy) can have a major impact to data subjects' privacy. However, if the assessor prioritise the mitigation actions following solely the CVSS score (Vulnerability characterisation), the ID-05 case, would look more severe, even thought the ID-01 case has a direct impact of users privacy via the information leakage. In fact, the same applies for the case of ID-06. In consideration of the potential impact that CVE-2020-11898 may have on patients' privacy, our risk scoring system considers the severity of the vulnerability, but via the weighted scale of Equation (1) the final score focuses on the privacy aspect. Hence, the scoring system addresses the need of considering the operational ramifications posed by the domain and quantifies the privacy risk based on an extensible scoring system. The same applies in the cases of ID-02 and ID-03, where the medical devices have been found vulnerable to Authentication. Bypass and Gain Information attacks. Again in both cases, the final privacy score results to a higher score than the vulnerability characterisation and assists the assessor to notice the privacy risk from the pertinent point of view. In the case of ID-04, the code execution vulnerability of PC0001, leads to an almost equal privacy score as the vulnerability characterisation. **Data processing flows in the frame of GDPR:** As we analysed thoroughly in Section 4.2, one of the main contributions of APSIA is the formation of the data processing flows in the context of an organisation following the principles of GDPR. Thus, given the use case scenario and the Patient Registration and Patient Monitoring processing activities, Figures 13-13 are generated automatically by considering the interconnections of the interdependency graph of Figure 4.  
More specifically, Figure 13 creates a flow that maps the PII, Data subjects, (i.e., Patient1, Patient2), Purpose of processing and the Lawfulness of Processing for revealing what type of data are processed in the organisation's processing activities and under which conditions and legal grounds. Note that, this view can be modified in order to provide a mapping among various GDPR entities and requirements in order to give the necessary flexibility to the assessor to keep track of particular flows of interest.