Skip to content

Device Hardening

This page describes the CPE security hardening baseline that RansNet applies to Customer Premises Equipment (CPE) such as SD-WAN gateways and branch routers (CMG, HSG, HSA, UA, XE, UAP) to comply with industry best practices, including CIS Benchmarks where applicable, during device onboarding, provisioning, and firmware updates — ensuring devices are securely configured before deployment.


What are CIS Benchmarks?

CIS Benchmarks are security hardening standards developed by the Center for Internet Security (CIS). They outline detailed, widely accepted configuration recommendations for systems ranging from operating systems (e.g. Linux, Windows) to network devices and applications.

For embedded CPE devices, not all CIS controls apply directly. RansNet CPE device OS/image are pre-built with functionally equivalent controls where native CIS rules cannot be applied due to platform constraints. These benchmarks serve as a baseline for secure configuration that auditors, integrators, and service providers often reference.

RansNet CPE hardening aligns with the following standards:

Standard Version Scope
CIS Benchmark for Linux Level 1 – Enterprise Sections applicable to embedded systems
CIS Benchmark for Network Devices v2.0 Supplementary
CIS Critical Security Controls v8 Framework reference
ISO/IEC 27001 2022 Annex A — information security controls
NIST SP 800-53 Rev 5 Control families: AC, AU, IA, SC, SI

Purpose

This hardening baseline aims to:

  • Reduce the device attack surface
  • Enforce secure defaults
  • Protect against common network attacks (e.g. SYN floods, brute force, unauthorized access)
  • Improve resilience against denial-of-service threats
  • Ensure consistent security posture across all deployed devices

Hardening Controls

The controls below highlight critical requirements as part of CPE deployments.

Some controls are OS defaults (built into the OS, already CIS-compliant, and cannot be changed). The remaining controls require action as part of the hardening process.

1. Operating System and Services

Control Action Required
Default credentials must be changed before onboarding OS default. A CLI login (SSH or console) with a factory default login or enable password must change it before the CLI can be used; the web GUI forces a change of the factory mboxadmin password at login; mFusion flags devices that still use one. See CLI Login Policy.
Passwords must meet complexity requirements OS default. Minimum 12 characters; must include uppercase, lowercase, digit, and special character; must not contain the username or hostname. Adjustable with security login-policy.
Password reuse is restricted OS default. The current and the last 5 passwords cannot be reused.
Account lockout is enforced OS default. The account is locked after 5 consecutive failed login attempts (SSH, console, or enable) and unlocks after 15 minutes.
Unused services (e.g. telnet, FTP) are disabled OS default
Privileged access (e.g. root/enable) is restricted Ensure login and enable passwords are different and comply with corporate security policy
Login warning banner is displayed Configure a legal warning banner on all management interfaces (SSH, console, web). See example below.
Firmware is kept up-to-date Upgrade to latest STABLE firmware after onboarding; apply security patches within the timelines defined in Vulnerability and Patch Management

2. Management and Access Controls

Control Action Required
Management access (SSH/HTTPS) enabled only over secure channels Configure VRF for management interface; add firewall-input rules to permit authorized source IPs only
Telnet and unencrypted management interfaces are disabled OS default
SSH root login is disabled OS default
SSH protocol version 2 only OS default
SSH authentication attempt limit OS default. MaxAuthTries 3 configured; brute-force attempts trigger session termination.
SSH dead-connection cleanup OS default. Connections that stop responding are closed after about 10 minutes (ClientAliveInterval 300, ClientAliveCountMax 2). Idle sessions are covered by the idle CLI session timeout.
Idle CLI session timeout OS default. SSH and console CLI sessions log out after 15 minutes without input. Adjustable with idle-timeout. See CLI Login Policy.
SNMP v1 and v2c are disabled OS default — SNMP v1/v2c are not enabled. If SNMP monitoring is required, use SNMPv3 with authPriv mode (SHA-256 authentication, AES-256 encryption) only

3. Network and Firewall Hardening

Control Action Required
Stateful firewall is enabled OS default
Default deny rules apply to untrusted interfaces OS default
Management and control ports restricted by ACLs Configure VRF for management interface; add firewall-input rules to permit authorized source IPs only
Address translation and NAT used responsibly Review firewall rules — strictly no "permit all" type rules
Rate limiting for TCP SYN, ICMP, and other flood vectors Configure rate limiting for management (SSH/HTTPS) services if these are allowed
Unused physical ports are administratively disabled Disable switch ports and WAN interfaces that are not in use
Known-bad addresses, port scans and SSH brute force are blocked Turn on Intrusion Prevention with threat feeds, scan protection and SSH brute-force protection

4. Cryptography and TLS

Control Action Required
Only TLS 1.2 and TLS 1.3 are enabled OS default
Weak protocols (SSL, TLS 1.0, TLS 1.1) are disabled OS default
Cipher suites adhere to strong cryptographic practices (forward secrecy, AEAD) OS default
SSH uses strong algorithms only OS default. No NIST ECDH/ECDSA, SHA-1, CBC or ChaCha20, MACs Encrypt-then-MAC only, compression off. See SSH Algorithms.
Certificate validation follows industry best practices Review company SOP; use valid SSL certificates and rotate yearly
VPN and IPSec use strong algorithms IKEv2 only; AES-256, SHA-256 minimum; DH group 14 (MODP-2048) or higher

5. Logging and Monitoring

Control Action Required
System and security logging is enabled Enable logging for firewall rules; export logs to a syslog collector
Authentication attempts, firewall drops, and config changes are logged Deploy syslog collector to receive logs from all devices; severity level info and above
Configuration changes are recorded with operator identity and timestamp OS default. Ensure AAA accounting is enabled; all CLI commands executed under a named account are forwarded to syslog
NTP time synchronization configured for consistent timestamps Use customer's internal NTP server if available; configure at least two NTP sources for redundancy
Log retention — online Logs must be searchable for a minimum of 90 days on the syslog collector
Log retention — archive Logs must be archived for a minimum of 12 months in cold storage or a SIEM

CLI Login Policy

The CLI login policy enforces the password, lockout, and session controls above for the CLI accounts on SSH and the serial console. The hardened defaults apply without any configuration, on new and upgraded devices. Existing passwords keep working; the rules apply at the next password change.

  • Factory default passwords must be changed at the first login
  • Password rules and reuse history
  • Account lockout after failed logins
  • Idle session timeout
  • Warning banner before login, and a notice of failed attempts at the next login
Account Used for Policy
Login (support) SSH and console login Password rules, reuse history, lockout
Enable Enable mode (enable) Password rules, reuse history; wrong enable passwords count towards locking the login account

Default Policy

Setting Default CLI
Minimum password length 12 password min-length <8-64>
Complexity: uppercase, lowercase, digit, special character; not the username or hostname Enabled password complexity enable or disable
Previous passwords that cannot be reused (the current password is always blocked) 5 password history <0-10>
Failed login attempts before lockout 5 lockout attempts <0-10> (0 = no lockout)
Seconds until a locked account unlocks 900 lockout attempts <n> unlock-time <60-86400>
Minutes without input before a CLI session logs out 15 idle-timeout <0-120> (0 = never)

Change Passwords

In enable mode, use change login or change enable. The new password is typed twice and checked against the policy:

mbox# change login
New login password: at least 12 characters, with upper and lower case letters, a digit and a special character, not containing the username or hostname.
New password:
Retype new password:
[info] login password changed.

When the factory default login or enable password is still in use, the CLI asks for new passwords right after login, on SSH and the console: first the login password, then the enable password. The CLI is not available until both are changed. Pressing Ctrl-C or Ctrl-D, or leaving the prompt idle, logs the session out. Entering enable mode checks again.

[warn] The factory default login password must be changed before you continue (Device Hardening).
New login password: at least 12 characters, with upper and lower case letters, a digit and a special character, not containing the username or hostname.
New password:
Retype new password:
[info] login password changed.
[warn] The factory default enable password must be changed before you continue (Device Hardening).
New enable password: ...

Note

On some models (for example XE-300), Ctrl-C has no effect at the password prompt. Press Ctrl-D to cancel.

To change the passwords of many devices at once, use Change CLI Passwords in mFusion. See Manage CLI Logins from mFusion.

Adjust the Policy

Change the policy only where your corporate security policy requires different values:

mbox# configure
mbox(config)# security login-policy
mbox(config-loginpolicy)# password min-length 14
mbox(config-loginpolicy)# password history 10
mbox(config-loginpolicy)# lockout attempts 5 unlock-time 1800
mbox(config-loginpolicy)# idle-timeout 10
mbox(config-loginpolicy)# end
mbox# write memory

no security login-policy returns to the defaults.

Account Lockout

After the configured number of consecutive failed attempts, the account is locked: even the correct password is rejected until the account unlocks. A successful login resets the count. To unlock an account before the unlock time, use one of the following:

  • CLI (enable mode): clear security login-lockout user support
  • mFusion: Unlock CLI Login (see below)
  • Change the password: a new password also clears the lockout

Note

A reboot also clears a lockout. Restrict management access to authorized source IPs (see Management and Access Controls) so that failed attempts from the internet cannot lock out administrators.

Manage CLI Logins from mFusion

Navigate to ORCHESTRATOR → Configuration → Gateway Devices (or Branch Devices). The Login Security column shows what each device reports:

Value Meaning
OK Custom passwords, no lockout
Default password (login, enable) A factory default password is still in use. Change it before the device goes into production.
Locked: support from <IP> The login account is locked after failed attempts
Weak hash The password was set before the policy; change it so it is stored with SHA-512. New passwords use SHA-512 where the device firmware supports it, otherwise MD5-crypt; devices that support only MD5-crypt are not flagged
Not reported The device firmware does not report login security yet, or the device has not checked in

Hover over a value to see the device's policy and when each password was last changed. Use Export to keep the list as audit evidence.

To change passwords or unlock accounts, tick the devices, click Selected, and select:

  • Change CLI Passwords: enter a new login and/or enable password. Leave a password empty to keep it. All ticked devices get the same password.
  • Unlock CLI Login: unlocks the locked login accounts.

Each device applies the change on its next mFusion check-in (about a minute). The device checks the new password against its own policy and password history and reports the result in its operation log, for example login: changed or login: rejected: Password must not contain the hostname. The passwords are sent encrypted and are not stored or logged in mFusion.

Login Banner and Notices

Before the password prompt, SSH and the serial console show a warning banner. Its second line follows the lockout policy:

WARNING: Authorised access only. All activity is logged and monitored.
Accounts are locked for 15 minutes after 5 failed login attempts.

After a successful login, the CLI reports failed attempts since the previous login, so that a legitimate administrator notices password guessing:

[warn] 3 failed login attempt(s) for support since the last login (last from 192.0.2.10).
[warn] Account support was locked at 2026-11-18 03:57:59 after 5 failed login attempts (last from 192.0.2.10).

Audit Log

Password changes, lockouts, and unlocks are logged with the account, the source, and who made the change, for example:

pwpolicy: account support locked after 5 failed login attempts (last from 192.0.2.10); auto-unlock in 900s
pwpolicy: account support unlocked by cli
pwpolicy: password for support changed by mFusion

These messages are forwarded to the remote syslog server with the other authentication messages. On Debian-based devices they are also kept in /var/log/loginsec.log.

Verification

Items to Test Command Expected Outcome
Policy in force and account status show security login-policy Policy values; each account shows custom (not DEFAULT) and active
Password rules change login, enter a short password [error] Password must be at least 12 characters.
Lockout Log in over SSH with a wrong password 5 times show security login-policy shows LOCKED (from <IP>, unlocks in ...s)
Unlock clear security login-lockout user support The account shows active; login works
Banner ssh support@<device> The warning banner is shown before the password prompt
Idle timeout Leave a CLI session without input for the idle time Warning: Idle timeout. The session will be closed. and the session ends
mFusion report Gateway / Branch Devices, Login Security column OK for every production device

Troubleshooting

Problem Cause Resolution
Correct password is rejected The account is locked after failed attempts Wait for the unlock time, run clear security login-lockout user support, or use Unlock CLI Login in mFusion
enable asks for a new password A factory default password is still in use Set a new password; enable mode is available after the change
mFusion job result rejected: ... The password breaks the device's policy, matches a recent password, or contains the hostname Choose another password and run Change CLI Passwords again
Login Security shows Not reported Firmware without the CLI login policy, or the device has not checked in Upgrade the firmware; check the device's mFusion connection
The session ends right after login with The CLI requires changing the factory default ... password A factory default password is still in use and the change was cancelled or timed out Log in again and set new passwords, or set them with Change CLI Passwords in mFusion
The session closes with Idle timeout No input for the configured idle time Adjust with idle-timeout under security login-policy (0 = never)

Login Warning Banner

A legal warning banner must be displayed before authentication on all management interfaces (SSH, serial console, and web). This is required by ISO 27001 A.5.14, NIST SP 800-53 AC-8, and PCI-DSS Requirement 8.

RansNet devices show a standard warning banner before every SSH and console login. See Login Banner and Notices. The banner text is fixed in this release; it does not include the organization name.

The banner must:

  • State that the system is for authorized users only
  • Warn that activity is monitored and logged
  • Not disclose system-specific information (e.g. OS version, hostname) to unauthenticated users

Recommended banner text:

*******************************************************************************
*                        AUTHORIZED ACCESS ONLY                               *
*                                                                              *
*  This system is the property of [Organization Name] and is for authorized   *
*  use only. Unauthorized or improper use of this system may result in        *
*  administrative disciplinary action and/or civil and criminal penalties.    *
*                                                                              *
*  By accessing and using this system, you consent to monitoring and          *
*  recording of all activity. Evidence of unauthorized or malicious use may   *
*  be referred to law enforcement or other relevant authorities.              *
*                                                                              *
*  Disconnect IMMEDIATELY if you are not an authorized user.                  *
*******************************************************************************

SSH Algorithms

The SSH server on every device offers only strong algorithms, as recommended by security assessments (VAPT) and CIS. This is an OS default: nothing has to be configured.

Type Allowed
Key exchange curve25519-sha256, diffie-hellman-group16-sha512, diffie-hellman-group18-sha512. Devices with a current SSH server also use strict key exchange; the Terrapin attack (CVE-2023-48795) does not apply to the allowed ciphers and MACs in any case.
Host keys ssh-ed25519, rsa-sha2-512, rsa-sha2-256
Ciphers aes256-gcm, aes128-gcm, aes256-ctr, aes192-ctr, aes128-ctr
MACs hmac-sha2-512-etm, hmac-sha2-256-etm (Encrypt-then-MAC only)
Compression Off

Not offered: NIST elliptic-curve key exchange and host keys (ecdh-sha2-nistp*, ecdsa-sha2-nistp*), SHA-1 (ssh-rsa, diffie-hellman-group14-sha1), CBC ciphers, ChaCha20, and MACs that are not Encrypt-then-MAC.

Firmware Upgrade

The firmware upgrade applies these settings at once, without a reboot; existing SSH sessions stay connected. Routers also receive OpenSSH 10.6. A router whose firmware image does not match the upgrade package keeps its current OpenSSH, but still gets the hardened settings.

After the upgrade:

  • The device offers its Ed25519 host key first. SSH clients that saved the old key warn once that the host key has changed. Confirm the new fingerprint, then remove the old entry (for example, ssh-keygen -R <device-ip>).
  • SSH clients that support none of the algorithms above can no longer connect. See Backward Compatibility.

Verification

Items to Test Command Expected Outcome
Algorithms in use ssh -v support@<device> from a Linux or macOS client kex: algorithm: curve25519-sha256 and host key algorithm: ssh-ed25519
Weak key exchange refused ssh -o KexAlgorithms=ecdh-sha2-nistp256 support@<device> no matching key exchange method found
Weak host key refused ssh -o HostKeyAlgorithms=ssh-rsa support@<device> no matching host key type found
Weak MAC refused ssh -o MACs=hmac-sha2-256 support@<device> no matching MAC found
CBC cipher refused ssh -o Ciphers=aes128-cbc support@<device> no matching cipher found

Troubleshooting

Problem Cause Resolution
WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! after the upgrade The device now offers its Ed25519 host key Confirm the fingerprint, then run ssh-keygen -R <device-ip> and connect again
no matching key exchange method found (or host key type, cipher, MAC) The SSH client is too old for the allowed algorithms Upgrade the client (OpenSSH 7.4 or later, PuTTY 0.75 or later)
An automation script or tool cannot connect Its SSH library offers only old algorithms Update the library; see Backward Compatibility

Vulnerability and Patch Management

RansNet monitors the relevant system component CVE feeds and issues firmware updates according to the patch timelines below:

Severity CVSS Score Maximum Patch Timeline
Critical 9.0–10.0 14 days from disclosure
High 7.0–8.9 30 days from disclosure
Medium 4.0–6.9 Next scheduled firmware release
Low / Informational 0.1–3.9 Best-effort; addressed in major release

Note

Patch timelines above represent the maximum target for a firmware release to be available. Deployment to production devices is subject to the customer's own change management process.

When a critical or high severity CVE affects a deployed component, RansNet will:

  1. Publish a security advisory in the release notes
  2. Release a patched firmware build within the timeline above
  3. Notify affected customers via the support portal

Compliance Mapping

The table below maps RansNet hardening controls to commonly referenced compliance frameworks to assist auditors and integrators.

Control Area CIS Controls v8 ISO 27001:2022 NIST SP 800-53 Rev 5
Default credentials changed CIS 4.7 A.5.17 IA-5
Password complexity and lockout CIS 5.2, 5.3 A.5.17 IA-5, IA-11
SSH root login disabled CIS 4.1 A.8.2 AC-2, AC-6
Login warning banner CIS 4.1 A.5.14 AC-8
Management ACLs / source IP restriction CIS 12.2 A.8.20 AC-3, SC-7
SNMP v3 (if SNMP used) CIS 12.1 A.8.20 AC-3
Unused services disabled CIS 4.8 A.8.8 CM-7
Stateful firewall, default deny CIS 13.1 A.8.20 SC-7
TLS 1.2/1.3, strong ciphers CIS 3.10 A.8.24 SC-8, SC-28
SSH strong algorithms only CIS 3.10 A.8.24 SC-8, SC-13
VPN / IPSec strong algorithms CIS 3.10 A.8.24 SC-8
System and security logging CIS 8.2 A.8.15 AU-2, AU-3
Config change audit trail CIS 8.5 A.8.15 AU-12, CM-5
NTP synchronization CIS 8.4 A.8.17 AU-8
Log retention (90 days online, 12 months archive) CIS 8.3 A.8.15 AU-11
Firmware update process CIS 7.3, 7.4 A.8.8 SI-2
CVE patch timelines CIS 7.4 A.8.8 SI-2, RA-5

Compliance and Evidence

To demonstrate compliance with this baseline during audits, collect and retain the following evidence artefacts:

Evidence Description
Firewall configuration export Full firewall ruleset showing default deny, management ACLs, and rate limiting
Login banner screenshot Screenshot of SSH/console login showing the warning banner before authentication
User account list Output of configured accounts with roles; confirm no default/shared accounts remain
SNMP configuration Confirm SNMP v1/v2c disabled; show SNMPv3 configuration if in use
Syslog configuration Show remote syslog destinations configured and log severity settings
Log sample Sample of authentication, firewall drop, and config change events from the syslog collector
NTP configuration Show NTP server configuration and synchronisation status
Firmware version Show current firmware version and confirm it is within the supported release window
Signed onboarding checklist Completed checklist (below) signed by the implementing engineer and project lead

This approach aligns with CIS Benchmarks where applicable and documents deviations where the embedded operating system or device role requires a different implementation. Deviations must be recorded with a compensating control and approved through the RansNet security governance process.


Onboarding Hardening Checklist

Use this checklist as part of your UAT/implementation report. Each item must be verified by the implementing engineer and signed off before the device enters production.

Device: ___________________________ Serial / ID: ___________________________

Engineer: ___________________________ Date: ___________________________

Reviewed by: ___________________________ Date: ___________________________


OS and Services

  • [ ] Default login password changed to a unique, policy-compliant password
  • [ ] Enable/privileged password set separately from login password
  • [ ] show security login-policy shows the required policy, no DEFAULT password, and no locked account
  • [ ] mFusion Login Security column shows OK for the device
  • [ ] Login warning banner configured on SSH and console
  • [ ] Unused services confirmed disabled (telnet, FTP)
  • [ ] Firmware version confirmed as latest STABLE release

Management and Access

  • [ ] Management interface assigned to dedicated VRF or restricted interface
  • [ ] Firewall-input rules permit only authorized source IPs for SSH/HTTPS
  • [ ] SSH root login disabled (PermitRootLogin no)
  • [ ] SSH MaxAuthTries set to 3
  • [ ] CLI idle timeout in force (show security login-policy; default 15 minutes)
  • [ ] SNMP v1/v2c confirmed disabled; SNMPv3 configured if monitoring required

Firewall and Network

  • [ ] Stateful firewall enabled
  • [ ] Default deny policy in place on WAN/untrusted interfaces
  • [ ] No "permit all" rules present
  • [ ] Rate limiting configured for SSH, HTTPS, and ICMP
  • [ ] Unused physical ports disabled

Cryptography

  • [ ] TLS 1.2/1.3 only (no SSL, TLS 1.0, TLS 1.1)
  • [ ] SSH refuses weak algorithms (ssh -o KexAlgorithms=ecdh-sha2-nistp256 support@<device> fails)
  • [ ] VPN/IPSec policy uses IKEv2, AES-256, SHA-256, DH group ≥ 14
  • [ ] SSL certificates are valid and will not expire within 90 days

Logging and Monitoring

  • [ ] Syslog remote destination configured and reachable
  • [ ] Firewall rule logging enabled
  • [ ] Authentication and config change logging confirmed (test log entry generated)
  • [ ] NTP synchronization configured with at least one reachable server
  • [ ] NTP authentication configured (if supported by platform)

Documentation

  • [ ] Configuration export archived in document management system
  • [ ] Baseline configuration backup taken
  • [ ] Deviations from this baseline documented with compensating controls

Review and Updates

This hardening baseline is reviewed at least annually or whenever significant security requirements change. Any deviations are documented and approved through the RansNet security governance process.

Field Value
Document owner RansNet Security Engineering
Review cycle Annual, or upon significant CVE disclosure
Last reviewed April 2026
Next review due April 2027