## 3 Develop Technical Infrastructure and CUREX Tools
\begin{table}
\begin{tabular}{c c c c c c c c} \hline \hline
**IP** & **Host** & **Notes** & **System** & **Domain** & **Name** & **IP/Port Number** \\ \hline
172.21.40.2 & DEVUCUREXSAVAC & HIS server CUREX & Centos 7.7, BBDD Oracle 11.2.0.4.0 & 40 & CUREX\_SERVER & 172.21.40.0/24 \\ \hline
172.21.40.3 & PREPACS & Preproduction PACS server CUREX & Windows 2016, IPS. & & & & \\  & & & & & & \\ \hline
172.21.40.4 & PREPACSSQL & Preproduction PACS SQL server CUREX & Windows 2016, SQL Server & 42 & CUREX\_ME & 172.21.42.0/24 \\ \hline
172.21.40.5 & DEVUCUREXSAVI05 & Integration HIS server CUREX & Windows 2012, Apache Tomcat & & & & \\ \hline
172.21.40.6 & DEVUCUREXSAVIPS &
\begin{tabular}{c} HIS Template server CUREX \\ \end{tabular} & Windows 2012, File server & & & & \\ \hline
172.21.40.7 & DEVUCURESAVIPS1 &
\begin{tabular}{c} HIS Reports server CUREX \\ \end{tabular} & Windows 2012, File server & & & & \\ \hline
172.21.40.8 & DEVUCUREXASVC01 &
\begin{tabular}{c} Virtualisation server CUREX \\ \end{tabular} & Windows 2012R2 Citrix Server & 172.21.41.2 & pccurex01 & 255.255.0 & Windows 10 \\ \hline
172.21.40.9/24 & DEVUCUREXADT01 &
\begin{tabular}{c} Asset Discovery \\ Server Curex\_Server \\ \end{tabular} & OVA & 172.21.41.3 & pccurex02 & 255.255.0 & Windows 10 \\ \hline
172.21.41.5/24 & DEVUCUREXADT02 &
\begin{tabular}{c} Asset Discovery \\ server Curex\_User \\ \end{tabular} & OVA & 172.21.41.4 & pccurex03 & 255.255.0 & Windows 10 \\ \hline \hline \end{tabular}
\end{table} 
Table 1: Main components of the infrastructure and sectorization with VLANs. \begin{table}
\begin{tabular}{c c c c c c} \hline \hline
**Main Components** & **VLANs** \\ \hline HIS client application: either accessed from the CITRIX server farm or from a PC that has the client version installed locally, connects to the HIS database, which is installed in the hospital’s data center (DC). & & & \\ \hline Workstations: 4 PCs are placed inside VLAN user with the basic programs together with hospital’s user credential handling procedures (credentials). & & & \\ HIS database server: consists of a cluster of servers that contains all the information stored. & & & & \\ \hline Kali Linux Server: Debian-based Linux distribution aimed at advanced penetration testing and security auditing. & & & & \\ \hline Firewall: The hospital’s DC is generally supervised by a firewall system in which specific rules are programmed. VLAN user, VLAN server and VLAN device are connected bi-directionally to the firewall. & & & \\ \hline Switch: Dedicated 20G LACP link to the cluster of servers and a 10G LACP link to the rest of the network’s elements. & & & & \\ PACS image server: Images are stored on a server called PACS (picture and archiving communications system). To retrieve the images, from the HIS, a call is made to a URL through a unique identifier of the patient’s image study. & & & \\ \hline Integration server: Used to collect all the data and external files and integrate them into HIS, either in the database or on the file server, or by external links using identifiers. & & & \\ \hline Medical equipment: Two medical devices and an emulator are placed in VLAN_device. Medical devices can be real hardware or & & & \\ \hline Smartphone: Connection through Wi-Fi (open Wi-Fi validated via capture portal), using a specific identification that the firewall allows it to be visible & & & \\ \hline \hline \end{tabular}
\end{table} 
Table 2: Network details of mounted servers in the use case infrastructure, open virtual appliances (OVAs), configured VLANs and virtual workstations. Notice that all IPs and ports' information is safe in terms of cybersecurity and information privacy because they are not used and isolated from the real hospital's infrastructure. Moreover, the operating systems of the workstations and PCs are selectable between Windows 7 and Windows 10, which are commonly used operating systems among health providers. Windows XP is no longer in use at the hospital facilities.