Zero Touch allows a UTM to receive a complete configuration, e.g., from a cloud backup, without requiring any input on the device itself.
In Unified Security Console (USC), a UTM Zero Touch Profile must first be stored, linked to the serial number, the PIN from the startup screen, a license, and, if applicable, a configuration file .
The UTM attempts to connect to our portal (requiring a DHCP server accessible on LAN1/ A0) and automatically downloads the Zero Touch profile.
The UTM restarts with the stored license and, if applicable, the stored configuration, and is accessible via USC Websession
The displayed QR code allows our shipping department to pre-send the serial number and PIN to a reseller
Login mask
Using the key combination Alt→ (Cursor/Right arrow key) respectively → you can access the login mask
Factory Setting:
Username: admin
Password: insecure
Web interface
Open the web interface via the IP address of the UTM (factory setting: https://192.168.175.1) and the respective port:
Administration Interface
Administration interface: Port 11115 (factory setting)
The start of e.g. Google Chrome or Edge is done with the start parameter --explicitly-allowed-ports=xyz.
For Firefox, a string variable with the value of the port to be released is created in the configuration (about:config in the address bar) under network.security.ports.banned.override.
It is possible to create a temporary policy for chromium-based browsers to allow its use. This is strongly discouraged for safety reasons!
Error message in Chome / Edge: ERR_UNSAFE_PORT
Error message in Firefox: Error: Port blocked for security reasons
Making the admin interface accessible Change in menu → Netzwerk →ServereinstellungenTab Administration Button Add IP/ Network or via CLI: name.firewall.local> manager new hostlist 192.0.192.192/32 system update rule
Access as an administrator is also possible via SSH. With the SSH client under Linux, the command ssh user@<IP address>
Further notes in the article about access with SSH is sufficient.
Users with root permission get directly to the Linux console of the UTM. Call CLICommand Line Interface with the command spcli. Root permission is given to
Users with the user name root and membership of a group with Administrator permission
Serial interface
When using the serial interface, the connection is established with a suitable program, e.g. Putty on Windows ( ) Minicom on Linux.
The following settings must be used to use the serial interface:
A Websession to a UTM can be established via Unified Security Console (USC).
The operation is the same via the Webinterface. Access via https://portal.securepoint.cloud / Menü USC UTMs /Select Utm tile / Section Websession / Button start new Websession
Further details can be found in the Wiki under Websessions
Monitor failed logins
The log can be viewed in the web interface under Log Only display alerting center messages. Alternatively, the data can also be retrieved with the following CLI command:
alertingcenter alerts get
Limitation / throttling of login attempts
Error message if login attempts fail too often
In addition to the blocking of login attempts in IDS / IPS (activation under BlockChain (Fail2Ban) ) a new automatic throttling of login attempts takes effect for the admin and user interface:
After 8 consecutive failed login attempts, the login function via the admin and user interface will be blocked for a certain time.
This throttling takes effect on all interfaces and cannot be deactivated
The block time is initially a few seconds and increases for each additional failed login attempt
A corresponding message is displayed as a pop-up window
If a blocking threshold of more than 8 is set in the IDS / IPS, automatic throttling takes effect first. Lockouts via the IDS/IPS can be configured individually for each login service
In addition to the admin and user interface, smtp and ssh can also be protected there
and each IP address through which access is made. Depending on the number of login attempts and the duration of the ban set there, a combination is created with the login attempt limitation described here.
Connection Rate Limit
Throttling of access from certain source IPs to recurring ports
notempty
The function is still in the testing phase and will be further expanded. The function can initially only be configured via the CLI
The function aims to protect against attacks. SSL-VPN accesses can be protected against aggressive scans or login attempts, for example.
From v12.6.2, the UTM can limit the number of TCP and/or UDP connections from an external IP address to one port.
The following conditions apply:
Only incoming connections for which a default route exists are monitored
The connections from an IP address to a port of the UTM are counted within one minute
When activated, 5 connections / connection attempts per minute are permitted. The connections are then limited:
The additionally permitted connections are distributed evenly within 60 seconds of the first connection.
With a CONNECTION_RATE_LIMIT value of 20, an additional connection is added every 3 seconds.
10 seconds after the first login, 3 further connections could be established (each from the same IP address to the same destination port)
Blocking an IP address only affects access to the port that has been used too often.
Other ports can still be accessed.
The function is activated by default for new installations on 20 UDP connections / minute on all ports
For Updates the function must be manually activated
extc-Variable
Default
Description
CONNECTION_RATE_LIMIT_TCP
0
Number of permitted TCP connections of an IP address per port 0 = Function deactivated, no blocking is performed
CONNECTION_RATE_LIMIT_TCP_PORTS
Ports to be monitored. Empty by default=all ports would be monitored (if activated). Individual ports are separated by spaces: [ 1194 1195 ]
extc value get application securepoint_firewall Alternatively as root user: spcli extc value get application securepoint_firewall | grep RATE
Lists all variables of the securepoint_firewall application. The variables beginning with CONNECTION_RATE_LIMIT_ are responsible for the connection limit.
extc value set application securepoint_firewall variable CONNECTION_RATE_LIMIT_TCP value 20 system update rule
Limits the allowed number of TCP connections from a single IP address to a specific port to 20 per minute
A change is made directly by a rule update. The value must not be set to 0 first!
extc value set application securepoint_firewall variable CONNECTION_RATE_LIMIT_TCP value 0 system update rule
Deactivates the monitoring of TCP connections
extc value set application securepoint_firewall variable CONNECTION_RATE_LIMIT_TCP_PORTS value [ 443 11115 ] system update rule
Restricts the monitoring of TCP connections to ports 443 and 11115 There must be spaces before and after the square brackets [ ]!
extc value set application securepoint_firewall variable CONNECTION_RATE_LIMIT_TCP_PORTS value [ ] system update rule
There must be spaces before and after the square brackets [ ]!
extc value set application securepoint_firewall variable CONNECTION_RATE_LIMIT_UDP value 20 system update rule
Limits the allowed number of UDP connections from a single IP address to a specific port to 20 per minute Default setting for new installations from v12.6.2: 20 For update installations the value is 0, so the function is deactivated.
A change is made directly by a rule update. The value must not be set to 0 first!
extc value set application securepoint_firewall variable CONNECTION_RATE_LIMIT_UDP value 0 system update rule
Deactivates the monitoring of UDP connections
extc value set application securepoint_firewall variable CONNECTION_RATE_LIMIT_UDP_PORTS value [ 1194 1195 ] system update rule
Restricts the monitoring of UDP connections to ports 1194 and 1195. (Example for 2 created SSL-VPN tunnels). There must be spaces before and after the square brackets [ ]!
extc value set application securepoint_firewall variable CONNECTION_RATE_LIMIT_UDP_PORTS value [ ] system update rule
There must be spaces before and after the square brackets [ ]!
extc value set application securepoint_firewall variable CONNECTION_RATE_LIMIT_TCP value 20 extc value set application securepoint_firewall variable CONNECTION_RATE_LIMIT_TCP_PORTS value [ 443 11115 ] extc value set application securepoint_firewall variable CONNECTION_RATE_LIMIT_UDP value 20 extc value set application securepoint_firewall variable CONNECTION_RATE_LIMIT_UDP_PORTS value [ ] system update rule
notempty
Finally, the CLI command system update rule must be entered so that the values in the rules are applied.
For example, to allow a maximum of 20 connections per minute per IP address and port. For TCP, monitoring is restricted to ports 443 and 11115. All ports are monitored for UDP connections.
