Since 2026, network capable devices of the 'MKT-View' family are shipped with a configuration
considered 'Secure by Default', as required by the EU Commission's Cyber Resilience Act (CRA).
At the time of this writing (November 2026), only up-to-date firmware of devices with network-capable communication ports
(especially Ethernet LAN or Wireless LAN) had the Cyber Security configuration menu / status display
described in the chapters of this document.
Older, network-capable devices like MKT-View III could also be configured for safe settings, but the default settings were not
necessarily the safest possible network configuration. For those devices, network features like the integrated
HTTP server had to be configured individually in the Network Setup.
Newer devices (shipped with firmware not older than November 2026) ..
.. are shipped with a configuration considered Secure by Default, as required per CRA Annex I, Part 1, Section 2(b):
> products with digital elements must:
> "be made available on the market with a secure by default configuration,
> unless otherwise agreed between manufacturer and business user
> in relation to a tailor-made product with digital elements,
> including the possibility to reset the product to its original state;"
.. have the "possibility to reset the product to its original state" as explained
in the next chapter.
Resetting the product to its original state ("Secure by Default")
Being secure by default is an official legal requirement under the EU Cyber Resilience Act (CRA) [Regulation (EU) 2024/2847].
In practice, this means (interpreted with the help of an AI) ..
Out-of-the-Box Security: Products must ship in a secure state
the moment a user turns them on, without requiring the end-user
to manually harden settings, read complex manuals,
or figure out trade-offs.
No Shared Default Passwords: Manufacturers cannot use universal
default passwords across devices; they must either use unique
credentials or force a password setup on first use.
Minimized Attack Surface: Unnecessary communication interfaces,
open ports, or non-essential services must be disabled by default.
Encrypted Communication: Data in transit and at rest must have
proper encryption enabled right away.
Distinction from Secure by Design: While secure by design
governs how a product is architected and built during development,
secure by default governs the actual configuration the product
leaves the factory with. Both are distinct, mandatory obligations
under Annex I of the CRA.
To restore the device to the default state (with maximum security, at the expense of being able to access the device
remotely over network-capable ports), proceed as follows:
Enter the device's local System Menu:
In the MKT-View devices, press the 2nd and 3rd function key simultaneously.
If entering the System Menu had been disabled (for 'local security'), hold these keys pressed
before turning on the power.
Scroll down to the 'Cyber Security' item. This item already shows the current setting,
e.g. Maximum (which is the 'secure default').
Press the ENTER key (or rotary button) to enter the 'Cyber Security' overview,
along with the statuses of all communication ports (including CAN, which may also be used
to remotely control the device as explained in another document).
On the bottom of the screen, press the button labelled
F1: Restore 'Secure Defaults'
That's all - no need to "read complex manuals".
The consequences of setting the Security level to Maximum (versus other levels like Low, Moderate, High)
are explained in the subsequent chapters.
Cyber Security Levels
At the time of this writing (November 2026), the following (Cyber-)Security Levels could be selected:
Low
HTTP server (not HTTPS) enabled: Should only be used 'behind a firewall', in a local network without Internet access,
or (if Internet access is really required) using a VPN (Virtual Private Network).
Same also for TELNET, FTP, VNC, and the OpenABK server (allowed only at the LOW security level).
"Program" (user application) transfer via CAN is possible (using a special Pseudo-Random Sequence for safety).
Any physical communication port (CAN1..CAN4, RS-232, USB with Virtual COM Ports, Ethernet LAN, Wireless LAN, etc)
is fully functional, including Remote Control from MKT's Programming Tool.
Moderate
HTTP-, TELNET-, FTP-, VNC, and OpenABK- server are disabled
"Program" (user application) transfer via CAN is possible (using a special Pseudo-Random Sequence for safety).
High
HTTP-, TELNET-, FTP-, VNC-, and OpenABK server are disabled
"Program" (user application) transfer via CAN is possible (using a special Pseudo-Random Sequence for safety).
The user application (compiled script) still can open certain communication ports (including RS-232, USB / Virtual COM, TCP/IP)
Maximum
HTTP-, TELNET-, FTP-, VNC-, and OpenABK server are disabled
Not even a "program" (user application) update via CAN from the programming tool is possible.
The only method to load a new "program" is manually, via memory card, as explained here.
Even the user application (script) cannot open communication ports considered 'network capable' (TCP/IP, UDP, via Ethernet or Wireless LAN).