s::can con::cube D-330 - 6.4 con::cube Network Integration and Security

6.4 con::cube Network Integration and Security
For normal operation, remote control, data transfer and other features it might be necessary to setup a connectivity of the
con::cube.Withinthissectionthedi󰀨erentpossibilitiesareexplainedandsecuritybackgroundismentionedalso.
The con::cube is based on Microsoft Windows XP embedded (XPe) operating system until moni::tool versions V2.5. From
Version 3.0 on it is based on a Linux operating system (Debian).
While the XPe platform is well-proven and stable it already
has reached the end of its mainstream support. Microsoft
will still supply security updates within a certain period but
won‘txnon-criticalissues.Linuxwillsupportfurthersecurity
updates.
Nonetheless, the con::cube is a complex device o󰀨ering
services over the network. Software security therefore is an
issue which needs to be considered to safely operate the
con::cube.
On the con::cube the TCP / IP interface can be used via LAN,
WLAN or 3G Modem (optional). All these features can be
conguredwithintheService / Terminal / Network menu (see
manual moni::tool).
The table below contains all types of possible connectivity setups. Regarding the individual connection types please refer to
the subsections afterwards.
con::cube Type of data transfer Connection type Customer infrastructure Security
acts as client (i.e. con::
cube establishs the
connection, performs
a task and shuts down
the connection)
FTP data transfer
SSH data transfer
NTP-client (for system
time synchronization)
all connection types FTP server
SSH server
acts as server
(i.e. con::cube waits for
a client to connect and
responds to its request)
Modbus TCP
TML
VNC remote control
FTP remote control
LAN or WLAN trusted network
3G private IP internet
3G private IP VPN server
3G public IP
open WLAN without
WEP
Because of the number of services o󰀨ered, the con::cube MUST NOT be operated in environments where those
services can be reached public. i.e. the con::cube MUST NOT be reachable from the internet. The most common
congurationsthatareNOTsafearea3GconnectionwithapublicIPaddressandaWLANconnectiontoapublic,
non-encrypted network.
Itisalwayssafetooperatethecon::cubeinaprivatenetwork,i.e.inaLANunlesstherewallisconguredtoforward
external requests to the con::cube (port-forwarding).
con::cube D-330, 01-2020 Release
www.s-can.at
Copyright © s::can Messtechnik GmbH
19 / 42
!
!