## 4 Findings
### Providing Concerns and Proposals by Experts (for System Design)  
While discussing each task, the experts raised several concerns and proposed useful solutions for future system designs. This section summarizes additional concerns raised by the experts in Table 3 and illustrates their proposals.  
Cloud services were assumed by most of the experts as'mostly secured' with a lower probability of not patching vulnerabilities and properly monitoring their systems. However, other experts argued that cloud services require a lot of trust in the service provider and that many examples have shown vulnerabilities. They also pointed out that a malicious cloud provider would be highly problematic. The first row in Table 3 includes the experts' comments while they discussed cloud and related security.  
Further, while discussing the significance of identifying a device, or security threats relevant to devices, experts emphasized maintaining industry and/or government maintained standards with a timely upgrade of relevant hardware and software. Remarkably, the experts did not always agree and identify best practice approaches. For example, there was no clear conclusion on the topic of virus scanners and anti-malware software, while **Expert-7** pointed out anti-malware software needs to be always updated, **Expert-5** argued against it,  
_\"I think the only thing that we can assume is that any kind of protection software on smartphones breaks the security of the smartphone. I have not seen any proof of anti-malware software strengthening security. However, I have seen many issues with this...\"_  
Another significant concern by the experts was human-centric issues related to accessing a smart healthcare environment. In this regard, they discussed ransomware attacks, lack of awareness from both the doctor and patient side, and various social engineering attacks, while discussing these, one expert commented,  
_\"So if you've got a compromised individual anywhere in the chain, then he can gain system access, and that does not require any vulnerability...\"_**Expert-4**  
Along with various concerns, some experts proposed a'specially prepared device and system environment' for minimizing security threats in the designed healthcare scenario and indicated information related to those should be added as security metadata. According to **Expert-5**,  
_\"I would build something like a Virtual Private Network (VPN) connection through a vendor. Maybe we can channel through them (the vendor) without them able to process it. However, this vendor specifically knows what kind of traffic should go in and out. He can decide whether the traffic is okay or not\"_  
**Expert-6** explained the idea of using VPN in the healthcare system as follows.  
_\"I like the idea that certain data, especially health data can only flow through certain channels. Furthermore, that happens to be a VPN or some private network. In that case, we can skip encryption and make sure that health data pass through these channels is ending up in a secured channel from an information flow perspective. They should not just be going through public networks\"_As another potential solution, some experts proposed utilizing mobile phone operators to limit the communication pathways to allow the devices to reach certain endpoints. One example considered by them was 5G slices for limited communication pathways between the devices. Moreover, experts considered a specially designed smartphone with restricted device configuration and specific access control mechanisms for any unwanted intruder, designed to deal with health data only. We argue that these concerns and proposals reveal important insights for a security-aware provenance-based system design.