MXsecurity User Manual
Version 2.1, July 2024

www.moxa.com/product© 2024 Moxa Inc. All rights reserved.

MXsecurity User Manual
The software described in this manual is furnished under a license agreement and may be used only in accordancewith the terms of that agreement.

Copyright Notice© 2024 Moxa Inc. All rights reserved.

Trademarks
The MOXA logo is a registered trademark of Moxa Inc.
All other trademarks or registered marks in this manual belong to their respective manufacturers.

Disclaimer
•
•

•

•

Information in this document is subject to change without notice and does not represent a commitment
on the part of Moxa.
Moxa provides this document as is, without warranty of any kind, either expressed or implied, including,but not limited to, its particular purpose. Moxa reserves the right to make improvements and/orchanges to this manual, or to the products and/or the programs described in this manual, at any time.
Information provided in this manual is intended to be accurate and reliable. However, Moxa assumes noresponsibility for its use, or for any infringements on the rights of third parties that may result from its
use.
This product might include unintentional technical or typographical errors. Changes are periodicallymade to the information herein to correct such errors, and these changes are incorporated into new
editions of the publication.

Technical Support Contact Informationwww.moxa.com/support

Table of Contents
1.

2.

3.

4.

5.

6.

Introduction ......................................................................................................................................... 6
Key Features ......................................................................................................................................... 6
Centralized Management ................................................................................................................. 6
Unified, Error-free Mass Deployment................................................................................................. 6
Real-time Visibility and Monitoring .................................................................................................... 6
Event Logs and Alert Notifications .................................................................................................... 6
Interactive Map View ...................................................................................................................... 6
Comprehensive Reports .................................................................................................................. 6
System Requirements ............................................................................................................................ 7
Installation ........................................................................................................................................... 8
Downloading MXsecurity ......................................................................................................................... 8
Setting Up the Virtual Machine ................................................................................................................ 9
Installing MXsecurity on a VMware Workstation .................................................................................. 9
Installing MXsecurity on a VMware ESXi System ............................................................................... 12
Configuring the MXsecurity system ................................................................................................. 17
Migration ............................................................................................................................................ 20
Migrating to a Newer Version of MXsecurity (VMware Workstation) ............................................................ 20
Migrating to a Newer Version of MXsecurity (ESXi) ................................................................................... 24
Getting Started ................................................................................................................................... 28
Getting Started Task List ...................................................................................................................... 28
Opening the Management Console ......................................................................................................... 28
Connecting Secure Routers to MXsecurity ............................................................................................... 30
Dashboard and Widgets ...................................................................................................................... 31
Dashboard Widgets Overview ................................................................................................................ 31
System Status ............................................................................................................................. 31
Node License Usage ...................................................................................................................... 31
Group Status ............................................................................................................................... 32
Top 5 Layer 3-7 Policy Events by Source IP ..................................................................................... 33
Top 5 Layer 3-7 Policy Events by Destination IP ............................................................................... 34
Top 5 Layer 3-7 Policy Events by Severity ....................................................................................... 35
Top 5 Protocol Filter Policy Events by Source IP ............................................................................... 36
Top 5 Protocol Filter Policy Events by Destination IP ......................................................................... 36
Top 5 Protocol Filter Policy Events by Severity ................................................................................. 37
Top 5 ADP Events by Source IP ...................................................................................................... 38
Top 5 ADP Events by Destination IP ................................................................................................ 38
Top 5 IPS Events by Source IP ....................................................................................................... 39
Top 5 IPS Events by Destination IP ................................................................................................. 40
Top 5 IPS Events by Severity ......................................................................................................... 42
Top 5 IPS Events by Category ........................................................................................................ 42
Connection Interface (Cellular Router) ............................................................................................ 43
Signal Quality (Cellular Router) ...................................................................................................... 43
Device Log by Timeline ................................................................................................................. 44
Firewall Log by Timeline ................................................................................................................ 44
VPN Log by Timeline ..................................................................................................................... 45
Widget Management ............................................................................................................................ 46
Adding a Widget to the Dashboard ................................................................................................. 46
Removing a Widget from the Dashboard ......................................................................................... 47
Resizing a Widget ......................................................................................................................... 47
Moving the Widget Position ............................................................................................................ 48
Management ....................................................................................................................................... 49
Device Group Management ................................................................................................................... 50
Creating a New Device Group ........................................................................................................ 50
Deleting a Device Group ................................................................................................................ 51
Editing a Device Group .................................................................................................................. 52
Firmware Management ......................................................................................................................... 52
Uploading a New Firmware ............................................................................................................ 52
Deleting a Firmware ..................................................................................................................... 53
Exporting Firmware ...................................................................................................................... 54

7.

8.

9.

Software Package Management ............................................................................................................. 54
Checking the Security Package Status ............................................................................................. 54
Uploading a New Software Package ................................................................................................ 55
Deleting a Software Package.......................................................................................................... 56
Exporting Software Packages ......................................................................................................... 56
Viewing Detailed Information of a Software Package ......................................................................... 56
Viewing Network Security Package Logs .......................................................................................... 57
Setting Up a Scheduled Security Package Update Check .................................................................... 58
Object Management ............................................................................................................................. 58
Creating a New Filter Object .......................................................................................................... 58
Creating a New Interface Object..................................................................................................... 60
Editing an Object.......................................................................................................................... 60
Deleting an Object........................................................................................................................ 61
Policy Profile Management .................................................................................................................... 61
Creating a New Layer 3-7 Policy Profile ........................................................................................... 61
Creating a New Session Control Policy Profile ................................................................................... 64
Creating a New DoS Policy Profile ................................................................................................... 65
Creating a New IPS Policy Profile .................................................................................................... 67
Editing a Policy Profile ................................................................................................................... 68
Deleting a Policy Profile ................................................................................................................. 68
Device Configuration Management ......................................................................................................... 68
Uploading a Device Configuration File From a Local Host ................................................................... 68
Uploading a Configuration From a Device ........................................................................................ 69
Deployment ........................................................................................................................................ 71
Rebooting a Managed Device................................................................................................................. 71
Scheduling a Managed Device Reboot..................................................................................................... 72
Deleting a Managed Device Reboot Schedule........................................................................................... 73
Sending a Control SMS ......................................................................................................................... 73
Removing a Managed Device ................................................................................................................. 75
Deploying Policy Profiles to Managed Devices .......................................................................................... 76
Scheduling a Policy Profile Deployment for Managed Devices ..................................................................... 76
Deleting a Policy Profile Deployment Schedule ......................................................................................... 78
Upgrading the Software Package of Managed Devices .............................................................................. 78
Scheduling a Software Package Deployment for Managed Devices ............................................................. 79
Deleting a Software Package Deployment Schedule.................................................................................. 81
Upgrading the Firmware of Managed Devices .......................................................................................... 81
Scheduling a Firmware Deployment for Managed Devices ......................................................................... 82
Deleting a Firmware Deployment Schedule ............................................................................................. 83
Deploying a Configuration to Managed Devices ........................................................................................ 84
Scheduling a Configuration Deployment for Managed Devices ................................................................... 85
Deleting a Configuration Deployment Schedule ........................................................................................ 86
Map View ............................................................................................................................................ 88
Viewing Detailed Device Information ...................................................................................................... 89
Editing the Location of a Device ............................................................................................................. 90
Report ................................................................................................................................................ 92
Inventory Reports ................................................................................................................................ 92
Generating a Current Inventory Report ........................................................................................... 92
Scheduling an Inventory Report ..................................................................................................... 93
Cellular Signal Reports ......................................................................................................................... 95
Scheduling a Cellular Signal Report ................................................................................................ 95
Data Usage Reports ............................................................................................................................. 96
Generating a Cellular Data Usage Report ......................................................................................... 96
Scheduling a Cellular Data Usage Report ......................................................................................... 98
Trail Reports ....................................................................................................................................... 99
Generating a Trail Report .............................................................................................................. 99
Scheduling a Trail Report ............................................................................................................ 100
Viewing GPS Trajectories ............................................................................................................. 101
Report Settings ................................................................................................................................. 102
Configure Report Time Zone Settings ............................................................................................ 102
Editing a Report Schedule............................................................................................................ 103

10.

11.

Logging............................................................................................................................................. 104
Event Log ......................................................................................................................................... 104
Device Log ................................................................................................................................ 104
Firewall Log ............................................................................................................................... 106
VPN Log .................................................................................................................................... 110
Audit Log .................................................................................................................................. 111
Event Log Settings ..................................................................................................................... 113
Notifications ...................................................................................................................................... 114
Adding a Notification................................................................................................................... 114
Administration .................................................................................................................................. 118
User Accounts ................................................................................................................................... 118
User Roles ................................................................................................................................. 118
Account Input Format ................................................................................................................. 120
Adding a User Account ................................................................................................................ 121
Editing an Existing User Account .................................................................................................. 122
Deleting a User Account .............................................................................................................. 123
Configuring the Password Policy ................................................................................................... 123
Changing Your Account Password ................................................................................................. 124
Licenses ........................................................................................................................................... 125
Introduction to Licenses .............................................................................................................. 125
Viewing Your Product License Information ..................................................................................... 125
Alert Messages ........................................................................................................................... 126
Adding a New License ................................................................................................................. 127
Settings............................................................................................................................................ 129
Configuring Preferences .............................................................................................................. 129
Configuring the System Time ....................................................................................................... 129
Editing Email Settings ................................................................................................................. 130
Editing Syslog Settings ............................................................................................................... 131

1. Introduction

MXsecurity is a management platform that provides centralized visibility and security management to easily
monitor and identify cyberthreats and prevent security misconfigurations to create a robust threat defense.
This industrial network security management suite translates complex network activity and threat
intelligence into real-time visibility of cybersecurity statuses and actionable management for better
detection and reaction against cyberthreats. With real-time dashboards, MXsecurity helps users track andreact to OT network security events more efficiently.

Key Features
Centralized Management
Manage and monitor your secure router from one central location for better administration andmaintenance. Devices can also be managed in groups based on geographic location, function, or
responsibility to increase management efficiency.

Unified, Error-free Mass Deployment
Human error can lead to costly security breaches. Unified deployment of firewall policies, firmware
upgrades, configuration files, and IPS signature updates prevents configuration errors and ensures yournetwork is protected with the latest security intelligence.

Real-time Visibility and Monitoring
MXsecurity provides at-a-glance visibility, showing real-time network activity and threat analysis throughhighly customizable interactive widgets and a flexible dashboard.

Event Logs and Alert Notifications
MXsecurity automatically aggregates and monitors security logs at the appliance level and supports
customizable instant real-time alerts for more efficient monitoring and faster troubleshooting.

Interactive Map View
MXsecurity features a map view which shows the real-time GPS location of the secure router. The mapfunction is particularly useful to locate the secure router when it is used in mobile applications where thedevice is installed on moving equipment.

Comprehensive Reports
MXsecurity supports comprehensive reports for the OnCell Series, making it easier for administrators to
conduct device audits and manage cellular signal and data usage. Additionally, the scheduling featureenables users to set up periodical reports that are automatically generated and sent to specified recipients.

MXsecurity User Manual6System Requirements
The computer that MXsecurity is installed on must satisfy the following system requirements. The system
requirements depend on the number of nodes that will be managed through MXsecurity.
CPU (virtual cores)

4

RAM
Hard Disk Space

8 GB
64 GB

Supported Virtual
Machines

VMWare ESXi 6.x or above, VM Workstation 14 or above

MXsecurity User Manual7

2. Installation

Downloading MXsecurity
This section describes how to download the MXsecurity image file from the Moxa Software License Portal.

Steps:
1.

Open a web browser and go to https://netsecuritylicense.moxa.com.

2.

Log in to the Software License Portal using your Moxa account.

3.

In the top toolbar, navigate to Download > Download Software.

4.

Select MXsecurity and the image version.
A changelog for each version is provided in the Description field.

5.

Click Download.

MXsecurity User Manual

8

Setting Up the Virtual Machine
Installing MXsecurity on a VMware Workstation
This section describes how to deploy MXsecurity to a VMware Workstation system.

Prerequisites•

The OVA packages provided by Moxa must be available and accessible to the VMware Workstation.

•

VMware Workstation 14 or later is required.

Steps:
1.

Start the VMware Workstation.

2.

Go to File > Open in the menu bar.

3.

Select the MXsecurity VM image file (*.ova) from your localhost file path and click Open.

4.

Specify the name and the storage path for the new virtual machine and click Import.

5.

Check the detailed VM information of the imported MXsecurity VM.

6.

Add an external disk. MXsecurity requires one external disk with at least 20 GB of available storage,
otherwise MXsecurity will not be able to finish initialization and the boot process will not be completed.
The external disk is used to store the system configurations and event logs. You may attach theexternal disk of a terminated MXsecurity instance here instead of adding a new disk if you want tomigrate the configurations and logs of the terminated instance to the new MXsecurity instance.
a. Click Edit virtual machine settings.

MXsecurity User Manual9b. Click Add, then choose Hard Disk.

MXsecurity User Manual10

c. Select a disk type and click Next.

d. Set the disk space of the new hard disk. You can configure the external disk size depending on thenumber of logs to be stored.

e. Select the path to store the disk.
f.

Click Finish.

g. (Optional) If necessary, you can increase the disk size to hold a larger number of MXsecurity logs:

7.

i.

Power off the MXsecurity instance.

ii.

Increase the external disk size based on your requirements.

iii.

Power the MXsecurity instance back on.

(Optional) Adjust your MX MXsecurity instance to use proper resource configurations (Minimum: 4 CPU
cores, 8 GB of memory).
a. Click Edit virtual machine settings.
b. Configure the amount of memory.
c. Configure the number of CPU cores.

MXsecurity User Manual

11

8.

(Optional) Depending on your network environment, change the network adapter setting from ‘NAT’ to‘Bridged’ if necessary.
a. Right-click the MXsecurity VM icon and select Settings.
b. Select Network Adapter and change the default setting from NAT to Bridged.

9.

Boot the MXsecurity VM. The MXsecurity instance will initialize.

Installing MXsecurity on a VMware ESXi System
This section describes how to deploy MXsecurity to a VMware ESXi system.

Prerequisites•

The OVA packages provided by Moxa must be available and accessible to VMware ESXi.

•

ESXi version 6 or above with the required specifications.

•

The necessary networks have been properly created in ESXi.

Steps:
1.

Log in to the VMware vSphere web client.

2.

Under Navigator, click Host and then click Create/Register VM.

3.

Select Deploy a virtual machine from an OVF or OVA file.

4.

Enter a name for your MXsecurity instance and then select an MXsecurity image to upload.

5.

Choose a storage location for the MXsecurity virtual machine.

MXsecurity User Manual

12

6.

Select the deployment options.

MXsecurity User Manual13When you see the Ready to complete screen, click Finish to start the deployment.

7.

Under the Recent tasks pane, you will see a progress bar indicating that the MXsecurity image is being
uploaded. Wait until the upload has finished.

8.

Add an external disk with at least 20 GB of available space to the MXsecurity instance:a. Power off the MXsecurity instance if it is powered on.
b. Navigate to Actions > Edit settings > Add hard disk > New hard disk.

MXsecurity User Manual14

c. Set the disk space of the new hard disk and click Save.
You can configure the external disk size depending on the number of logs to be stored.

a. (Optional) If necessary, you can increase the disk size to hold a larger number of MXsecurity logs:i.

Power off the MXsecurity instance.

ii.

Increase the external disk size based on your requirements.

iii.

Power the MXsecurity instance back on.

If you want to migrate the existing MXsecurity settings to the newly launched VM, please refer to
Migration.

NOTE
The external disk is used to store the system configurations and event logs. You may attach the external
disk of a terminated MXsecurity instance instead of adding a new disk if you want to migrate theconfigurations and logs of the terminated instance to the new MXsecurity instance.
9.

Power on the VM.

10. (Optional) Adjust your MXsecurity instance to use proper resource configurations (Minimum: 8 coreCPU, 8 GB memory).
a. Shut down the instance of MXsecurity and click Edit.
The Edit settings window appears.
b. Configure the number of CPU cores.

MXsecurity User Manual15

c. Configure the amount of memory.

d. Click Save.
e. Boot the MXsecurity instance.

MXsecurity User Manual16Configuring the MXsecurity system
Accessing the MXsecurity CLI
Steps:
1.

Open the MXsecurity VM console.

2.

Log in with username admin and password moxa.

3.

Change the default password:

The password must meet the following requirements:
 Minimum 8 characters long The new password cannot be the same as the old password
 The new password cannot contain the old password
 The password cannot be too simplistic or contain simple character sequences such as “abc”,“123456”, etc
b. Log in to the MXsecurity again with your new password.
4.

(Optional) After logging in to the MXsecurity, type the “help” command to see a list of available
commands.

MXsecurity User Manual

17

Getting the IP Address of the MXsecurity Instance
Steps:
1.

Enter the interface ls command to get the IP address of the MXsecurity instance.

2.

If your VMware network adapter setting is using NAT, you will need to create port forwarding rules toallow traffic to pass from connected devices to MXsecurity.
a. Navigate to Edit > Virtual Network Editor, select the right network subnet and click NAT
Settings.
i.

To allow users to configure the devices through MXsecurity including all configuration settingsand commands and upload logs, forward packets from the host TCP port 8883 to the
MXsecurity server IP TCP port 8883.

ii.

To allow devices to synchronize their system time with MXsecurity, forward packets from thehost UDP port 123 to the MXsecurity server IP UDP port 123.

iii.

To access the web management console, forward packets from host TCP port 443 to the
MXsecurity server IP TCP port 443.

NOTEPort 8883, 123, and 443 are the default port numbers. If you change the port numbers, make sure to use
the correct port numbers in the NAT settings.

MXsecurity User Manual18Configuring the IP Address Settings
You can manually configure the IP address if necessary.

Steps:
1.

Use the interface --update command to update the settings of an existing network interface. For
example, the following command sets the interface “eth0” to the static IP address 192.0.2.4/24 with thegateway IP address 192.0.2.254.

$ interface --update eth0 --method static --address 192.0.2.4 --gateway
192.0.2.254 ––netmask 255.255.255.0
2.

Confirm the network interface settings are correct and execute the --restart [interface] command tohave the new settings take effect.

$ interface --restart eth0
3.

Execute the interface --ls command to view the network interface settings.

$ interface --ls4.

Use the resolve --add command to add a DNS server. For example, the following command adds
“8.8.8.8” to the DNS server list.

5.

Execute the resolve --ls command to view the DNS server settings.

6.

Execute the reboot command to reboot the VM.

$ resolve --add 8.8.8.8$ resolve --ls
$ reboot

MXsecurity User Manual193. Migration

This chapter provides information and instructions on how to migrate your MXsecurity data to a newer
version of MXsecurity.

Migrating to a Newer Version of MXsecurity(VMware Workstation)
This section describes how to migrate to a newer version of MXsecurity with VMware Workstation.

NOTE
MXsecurity v1.1.0 has implemented enhanced connection security measures. To avoid issues, managed
devices should be upgraded to a firmware version and MXsecurity Agent Package which is compatible with
MXsecurity v1.1.0. The following device firmware versions are compatible with MXsecurity v1.1.0:•

EDR-G9010 Series FW v3.0 or higher, MXsecurity Agent Package v2.0.13 or higher•

EDR-8010 Series FW v3.0 or higher, MXsecurity Agent Package v2.0.13 or higher•

OnCell G4302 Series FW v3.0 or higher. MXsecurity Agent Package v2.0.13 or higher

If you have an older version of the MXsecurity Agent Package installed, you will need to manually upgrade
it to v2.0.13 on the managed device first. To manually upgrade the software package, navigate to System> System Management > Software Package Management > MXsecurity Agent Package in the
Secure Router’s web interface.

Steps:
1.

Start the VMware Workstation.

2.

Power off the MXsecurity instance.

3.

Go to File > Open in the menu bar.

MXsecurity User Manual

20

4.

Select the VM image file (*.ova) of the new MXsecurity version from your localhost file path and click
Open.

5.

Add an existing Hard Disk.
a. Click Edit virtual machine settings.

b. Click Add, then choose Hard Disk.

MXsecurity User Manual21

c. Select a disk type and click Next.

MXsecurity User Manual22

d. Select Using an existing virtual disk and click Next.

e. Navigate to the disk of the original MXsecurity instance and click Open.

6.

Click Finish.

7.

Log in to the MXsecurity web console and confirm the migration was successful.

MXsecurity User Manual23Migrating to a Newer Version of MXsecurity(ESXi)
This section describes how to migrate to a newer version of MXsecurity with VMware ESXi.

NOTE
MXsecurity v1.1.0 has implemented enhanced connection security measures. To avoid issues, managed
devices should be upgraded to a firmware version and MXsecurity Agent Package which is compatible with
MXsecurity v1.1.0. The following device firmware versions are compatible with MXsecurity v1.1.0:•

EDR-G9010 Series FW v3.0 or higher, MXsecurity Agent Package v2.0.13 or higher•

EDR-8010 Series FW v3.0 or higher, MXsecurity Agent Package v2.0.13 or higher•

OnCell G4302 Series FW v3.0 or higher. MXsecurity Agent Package v2.0.13 or higher

If you have an older version of the MXsecurity Agent Package installed, you will need to manually upgrade
it to v2.0.13 on the managed device first. To manually upgrade the software package, navigate to System> System Management > Software Package Management > MXsecurity Agent Package in the
Secure Router’s web interface.

Steps:
1.

Start the VMware ESXi.

2.

Power off the MXsecurity instance.

3.

Under Navigator, click Host and then click Create/Register VM.

4.

Select Deploy a virtual machine from an OVF or OVA file.

MXsecurity User Manual

24

5.

Enter a name for your MXsecurity instance and then the image file of the new MXsecurity version to
upload.

6.

Choose a storage location for the MXsecurity virtual machine.

7.

Select the deployment options.

MXsecurity User Manual25

When you see the Ready to complete screen, click Finish to start the deployment.

8.

Under the Recent tasks pane, you will see a progress bar indicating that the MXsecurity image is being
uploaded. Wait until the upload has finished.

9.

When finished installing, right-click the new MXsecurity instance and click Edit Settings.

MXsecurity User Manual2610. Click Add Hard Disk > Existing hard disk.

11. Navigate to the disk of the original MXsecurity instance and click Select.

12. Click Save.
13. Log in to the MXsecurity web console and confirm the migration was successful.

MXsecurity User Manual27

4. Getting Started

This chapter describes how to get started with MXsecurity and perform the initial configuration.

Getting Started Task List
The Getting Started task list provides a high-level overview of all procedures required to get MXsecurity(MXsecurity) up and running as quickly as possible. Each step links to more detailed instructions later in the
document.
1.

Open the management console.

2.

Change the administrator’s default login name and password after logging in for the first time.
For more information, see Changing Your Account Password.

3.

Activate your product license.

For more information, see Opening the Management Console.

For more information, see Licenses.
4.

Configure the system time.
For more information, see Configuring the System Time.

5.

Assigning policies to the device groups.
For more information, see Device Group Management and Policy Profile Management.

6.

Creating user accounts.
For more information, see User Accounts

Opening the Management Console
MXsecurity provides a built-in management console that you can use to configure and manage the product.
View the management console using a web browser.

NOTE
View the management console using Google Chrome version 103 or later.

Steps:
1.

In a web browser, type the address of the MXsecurity in the following format:

https://<target server IP address or FQDN>
The login screen will appear.
2.

Enter your username and password.
If you are logging in for the first time, use the default administrator credentials:
 Username: admin
 Password: moxa

3.

Click LOG IN.
If this is your first time logging in, the Change Password window will appear.

NOTE
You must change the default login name and password before you can access the management console.

MXsecurity User Manual28

a. Enter your new login details.
i.

Current Passwordii.

New Passwordiii.

Confirm New Password

b. Click Confirm.
You will be automatically logged out of the system. The login screen will appear again.
c. Log in again using your new credentials.
The dashboard screen will appear.

MXsecurity User Manual29Connecting Secure Routers to MXsecurity
To manage secure routers through MXsecurity, the device needs to be synced to MXsecurity.

Steps:
1.

Open a web browser and navigate to the secure router’s web management interface by entering its IP
address into the address bar.

2.

Navigate to System > Management Interface > MXsecurity.

3.

Enter the MXsecurity IP address field in the Service Address field.

4.

(Optional) Configure the HTTPS port and Communication ports based on the MXsecurity server
settings.

5.

Click CONNECT.

The secure router’s MXsecurity page also shows the current connection status. Refer to the table below for
more information.
Setting
StatusPackage Version
Service Address

Profile Synchronization

MXsecurity User Manual

Description
The status of the connection to MXsecurity.
Disconnected: The secure router is not connected to MXsecurity.
Connecting: A connection to MXsecurity is being established.
Connected: The secure router is connected to MXsecurity.
The currently installed MXsecurity Agent Package.
The IP address or domain name of the MXsecurity server.
The status of the policy profile synchronization with MXsecurity.
Unsynchronized: Failed to sync the policy profile settings with MXsecurity.
Synchronized: The policy profile settings are synced with MXsecurity.
Out of Synchronization: The policy profile settings were manually modified on
the device, causing a mismatch the MXsecurity profile settings.

30

5. Dashboard and Widgets

Monitor the system status, security assets, and threat detection on the Dashboard page. By default, theDashboard includes widgets for System Status, Node License Usage, Group Status, Top 5 Layer 3-7 Policy
Events, Top 5 Protocol Filter Policy Events, Top 5 ADP Events, and Top 5 IPS Events.

NOTE
The amount of statistical information shown depends on your user account role and whether permission to
manage each device group has been shared with you.

Dashboard Widgets Overview
This section describes available widgets on the dashboard.

System Status
This widget shows the CPU usage, memory usage, and disk usage of the system running the MXsecurity
instance.

Node License Usage
This widget displays the number of registered devices and the number of unused node licenses.

MXsecurity User Manual31Group Status
This widget lists the information of device groups and device status.

MXsecurity User Manual32Top 5 Layer 3-7 Policy Events by Source IP
This widget displays the top 5 source IP addresses in the selected device group(s) where the most Layer 3-7
Policy Events were detected within the last 24 hours.

MXsecurity User Manual33Top 5 Layer 3-7 Policy Events by Destination IP
This widget displays the top 5 destination IP addresses in the selected device group(s) where the mostLayer 3-7 Policy Events were detected within the last 24 hours.

MXsecurity User Manual34Top 5 Layer 3-7 Policy Events by Severity
This widget displays the number of Layer 3-7 Policy Events in the selected device group(s) within the last 24
hours categorized by severity level.

MXsecurity User Manual35Top 5 Protocol Filter Policy Events by Source IP
This widget displays the top 5 source IP addresses in the selected device group(s) where the most Protocol
Filter Policy Events were detected within the last 24 hours

Top 5 Protocol Filter Policy Events by Destination IP
This widget displays the top 5 destination IP addresses in the selected device group(s) where the mostProtocol Filter Policy Events were detected within the last 24 hours.

MXsecurity User Manual36Top 5 Protocol Filter Policy Events by Severity
This widget displays the number of the Protocol Filter Policy Events in the selected device group(s) within
the last 24 hours categorized by severity level.

MXsecurity User Manual37Top 5 ADP Events by Source IP
This widget displays the top 5 source IP addresses in the selected device group(s) where the most ADP
Events were detected within the last 24 hours.

Top 5 ADP Events by Destination IP
This widget displays the top 5 destination IP addresses in the selected device group(s) where the most ADP
Events were detected within the last 24 hours.

MXsecurity User Manual38Top 5 IPS Events by Source IP
This widget displays the top 5 source IP addresses in the selected device group(s) where the most IPS
Events were detected within the last 24 hours.

MXsecurity User Manual39Top 5 IPS Events by Destination IP
This widget displays the top 5 destination IP addresses in the selected device group(s) where the most IPS
Events were detected within the last 24 hours.

MXsecurity User Manual40MXsecurity User Manual41Top 5 IPS Events by Severity
This widget displays the number of IPS Events in the selected device group(s) within the last 24 hours
categorized by severity level.

Top 5 IPS Events by Category
This widget displays the number of IPS Events in the selected device group(s) within the last 24 hours
categorized by category.

MXsecurity User Manual42Connection Interface (Cellular Router)
This widget displays a summary of the type of interface currently being used for internet connectivity acrossall OnCell Series routers. The categories include 5G, 4G, 3G, 2G, Ethernet, and Wi-Fi.

Signal Quality (Cellular Router)
This widget displays a summary of the cellular interface signal quality across all OnCell Series routers,
including Good, Fair, Poor, and No Signal.

MXsecurity User Manual

43

Device Log by Timeline
This widget provides a visual representation of device log events over a specified period. Users canconfigure the timeline to display events for either the past 24 hours or the past 30 days.

Firewall Log by Timeline
This widget offers a visual representation of firewall events over a specified period. Users can configure thetimeline to display events for either the past 24 hours or the past 30 days. Additionally, users can selectdifferent subcategories of firewall events, such as DoS policy, to display on the 24-hour or 30-day view.

MXsecurity User Manual

44

VPN Log by Timeline
This widget provides a visual representation of VPN events over a specified period. Users can configure thetimeline to display events for either the past 24 hours or the past 30 days.

MXsecurity User Manual45

Widget Management
This section describes how to manage the widgets on the MXsecurity Dashboard.

Adding a Widget to the Dashboard
Steps:
1.

Click the2.

Check the checkbox next to the widget(s) you want to add.

3.

Click APPLY to add the selected widget(s) to the tab.

MXsecurity User Manual

icon to add widgets.

46

Removing a Widget from the Dashboard
Steps:
1.

Click theicon to edit the dashboard.

2.

Click theicon of the widget you want to remove.

3.

Click theicon again to save your changes and leave edit mode.

Resizing a Widget
Steps:
1.

Click theMXsecurity User Manual

icon to edit the dashboard.

47

2.

Hover the mouse cursor over the bottom-right corner of the widget until the resize icon is visible.

3.

Click and drag the corner of the widget to the desired size, then release the mouse. The dark grey areain the Dashboard background indicates the final size of the widget.

4.

Click theicon again to save your changes and leave edit mode.

Moving the Widget Position
Steps:
1.

Click the2.

Click and hold theicon then drag the widget to the desired position and release the mouse. The
widget will automatically snap into place.
The dark grey area in the Dashboard background indicates the final location of the widget.

3.

Click theMXsecurity User Manual

icon to edit the dashboard.

icon again to save your changes and leave edit mode.

48

6. Management

The Management page lets you manage device groups, and system databases for firmware software,
packages, objects, policy profiles, and device configuration files. With these databases, you can deploy eachdevice individually or arrange them in groups to share the same configuration and policy.

NOTE
The information shown depends on your user account role and whether the permission to manage thedevice groups has been shared with you.

MXsecurity User Manual49

Device Group Management
To easily manage a large number of devices using MXsecurity, devices can be conveniently grouped so thatthe same security policy configurations can be shared among the devices that belong to the same group.
The configurations and policies that can be shared are:•Firmware•

Software packages•

Objects•

Policy profiles•

Device configurations

Creating a New Device Group
Steps:
1.

Navigate to Management > Device Groups.

2.

Click the3.

Provide a name and description for the group and click NEXT.

icon to create a new group.

The group name can be up to 32 characters long and supports a-z, A-Z, 0-9, periods (.), andunderscores (_).

4.

Check the box of the device(s) that you want to add to the group and click NEXT.

MXsecurity User Manual

50

5.

Check the box of the username(s) that you want to assign to the group and click APPLY.

Deleting a Device Group
Steps:
1.

Navigate to Management > Device Groups.

2.

Check the box of the group(s) you want to delete.

3.

Click theMXsecurity User Manual

icon to delete the selected group(s).

51

4.

When prompted to confirm, click DELETE.

Editing a Device Group
Steps:
1.

Navigate to Management > Device Groups.

2.

Click the3.

Edit the device group information, add devices, or grant access permissions.

icon to edit a device group.

4.

Click APPLY to save the changes.

Firmware Management
This section describes how to manage the local firmware database from MXsecurity.

Uploading a New Firmware
Steps:
1.

Navigate to Management > Firmwares.

MXsecurity User Manual

52

2.

Click theicon to add a new firmware.

NOTE"Schedule in Use" indicates there is an upcoming scheduled deployment to apply this firmware to thedevice. To avoid any disruptions or deployment process failures, firmware files with planned deployments
cannot be deleted.
3.

Drag and drop or browse to the firmware file on the local machine and enter a description.

4.

Click UPLOAD.

Deleting a Firmware
Steps:
1.

Navigate to Management > Firmwares.

2.

Check the box of the firmware you want to delete.

3.

Click the4.

When prompted to confirm, click DELETE.

MXsecurity User Manual

icon to delete the selected firmware.

53

Exporting Firmware
You can export the firmware files from MXsecurity to the local computer.

Steps:
1.

Navigate to Management > Firmwares.

2.

Click theicon to download the firmware.

Software Package Management
This section describes how to manage the software package either manually from a local PC or automaticallyby syncing to the Moxa server.
The following packages can be managed in MXsecurity:•

Network Security Package

This section contains the following tabs:•

Software Packages File: Manage software package files for supported devices.

•

Log: Shows software package-related event logs.

•

Sync: Configure scheduled software package update checks.

Checking the Security Package Status
The Software Packages Update Check section provides information about the Moxa server connection
status, the time and date of the last check, and the result of the last check. To access this section, navigate
to Management > Software Packages > Software Packages File.

The widget shows the following information:
Field
ServerLast Connection Check
Last Software Package
Update Result

Description
Shows the current status of the connection to the Moxa update server.
Shows the date and time of the last connection check.
Shows the result of the most recent software package update check.

To check for software package updates, click the CHECK SOFTWARE PACKAGE button. A list of models
and any available software package updates will be shown. The models shown in the list are configured in

MXsecurity User Manual54the Sync Settings tab. Refer to Setting Up a Scheduled Security Package Update Check.

Uploading a New Software Package
Steps:
1.

Navigate to Management > Software Packages > Software Packages File.

2.

Click theicon to upload a new software package.

NOTE"Profile in Use" indicates the number of policy profiles the file is being used by. Files used by policy profiles
cannot be deleted. Click the “…” icon in the column to see details of the referenced policy profile(s).

NOTE"Schedule in Use" indicates there is an upcoming scheduled deployment to apply this software package tothe device. To avoid any disruptions or deployment process failures, software packages with planned
deployments cannot be deleted.

MXsecurity User Manual

55

3.

Drag and drop or browse to the package file on the local computer and enter a description.

4.

Click UPLOAD.

Deleting a Software Package
Steps:
1.

Navigate to Management > Software Packages > Software Packages File.

2.

Check the box of the package(s) you want to delete.

3.

Click the4.

When prompted to confirm, click DELETE.

icon to delete the selected software package(s).

Exporting Software Packages
You can export the software packages from MXsecurity to the local computer.

Steps:
1.

Navigate to Management > Software Packages > Software Packages File.

2.

Click theicon to download the software packages.

Viewing Detailed Information of a Software Package
You view more detailed information about each software package, including the supported products, build
time, and how many devices use the software package.

Steps:
1.

Navigate to Management > Software Packages > Software Packages File.

MXsecurity User Manual

56

2.

Click theicon to show detailed information for the software package.

NOTE"Profile in Use" indicates the number of policy profiles the file is being used by. Files used by policy profiles
cannot be deleted. Click the “…” icon in the column to see details of the referenced policy profile(s).

NOTE"Schedule in Use" indicates there is an upcoming scheduled deployment to apply this software package tothe device. To avoid any disruptions or deployment process failures, software packages with planned
deployments cannot be deleted.

Viewing Network Security Package Logs
Steps:
1.

Navigate to Management > Software Packages > Log.

2.

You can perform the following actions:a. Click the

button to export the current search results as a CSV file.

b. Click the

button to renew the search results.

The following table describes the log’s fields.
Field
Time
Severity
Event
Username
Message

MXsecurity User Manual

Description
The time the log entry was created.
The severity level assigned to the event.
The category of the event.
The username of the user that generated the log.
Additional details about the event.

57

Setting Up a Scheduled Security Package Update Check
Steps:
1.

Navigate to Management > Software Packages.

2.

Click the Sync Settings tab.

3.

In the Product Model field, select the product models to include the software package update check.

4.

Set the Sync Software Package by Schedule radio to Enabled to enable scheduled update checks.

5.

Select a Scheduling Mode, either daily or weekly:a. If daily: Set the time of the day to perform the check.
b. If weekly: Set the day of the week and time of the day to perform the check.

6.

In the Period field, specify the check period. The system will only perform update checks on thespecified time and date during this period.

7.

Click APPLY.

Object Management
This section describes how to manage the local object database from MXsecurity. The objects simplify policy
management by storing configurations that can be used by the device group they are associated with.
You can configure the following types of objects in MXsecurity:•

Filter Objects: Contain the IP address and subnet, network service, industrial application service, anduser-defined service that you can apply to a policy rule.

•Interface Objects: Contain the VLAN interface and bridge interface that you can apply to a policy rule.

Creating a New Filter Object
Steps:
1.

Navigate to Management > Objects.

2.

Click the Filter tab.

MXsecurity User Manual

58

3.

Click theicon to create a new object.

4.

Enter a name for the object.

5.

Select the Object Type. Depending on the select type, configure the following settings:

a. IP Address and Subnet:
i.

Depending on the selected IP Type, enter the IP address, IP range, or subnet.

b. Network Service:i.

Check the box next to the service(s) you want to add to the object.

c. Industrial Application Service:i.

Check the box next to the industrial application service(s) you want to add to the object.

d. User-defined Service:

6.

i.

Select an IP protocol.

ii.

Depending on the select protocol, specify the port, port range, ICMP Type and Code, or protocol
decimal.

Click CREATE.

MXsecurity User Manual59Creating a New Interface Object
Steps:
1.

Navigate to Management > Objects.

2.

Click the Interface tab.

3.

Click the4.

Enter a name for the object.

5.

Select the Mode. Depending on the selected mode, configuring the following settings:

icon to create a new object.

a. VLAN:i.

Enter the VLAN ID.

b. Bridge:i.
6.

Select a bridge mode.

Click CREATE.

Editing an Object
Steps:
1.

Navigate to Management > Objects.

2.

Depending on the object you want to edit, click the Filter or Interface tab.

3.

Click the4.

Modify the object settings.
For Filter Objects, refer to Creating a New Filter Object.
For Interface Objects, refer to Creating a New Interface Object.

5.

When finished, click APPLY to save the changes.

MXsecurity User Manual

icon to edit the object.

60Deleting an Object
Steps:
1.

Navigate to Management > Objects.

2.

Depending on the object you want to delete, click the Filter or Interface tab.

3.

Check the box of the object(s) that you want to delete.

4.

Click the5.

When prompted to confirm, click DELETE.

icon to delete the selected object(s).

Policy Profile Management
This section describes how to manage the local policy profile database from MXsecurity. Policy profiles
aggregate various firewall policies and can be deployed to device groups based on network security
requirements.
You can configure the following types of policies in MXsecurity:•

Layer 3-7 Policy: Provides secure traffic control, allowing users to control network traffic based on
security needs.

•

Session Control: Protects network hosts or services from exceeding performance limitations.

•DoS Policy: Provides different DoS protection functions for detecting or defining abnormal packet
formats or traffic flows.

•

IPS Policy: Performs intrusion detection and prevention to protect networks from security threats.

Creating a New Layer 3-7 Policy Profile
Steps:
1.

Navigate to Management > Policy Profiles.

MXsecurity User Manual

61

2.

Click theicon to create a policy profile.

NOTE"Device in Use" indicates the number of devices the policy profile is being used by. Policy profiles applied
to devices cannot be deleted. Click the “…” icon in the column to see details of the referenced device(s).

NOTE"Schedule in Use" indicates there is an upcoming scheduled deployment to apply this policy profile to thedevice. To avoid any disruptions or deployment process failures, policy profiles with planned deployments
cannot be deleted.
3.

Enter a name and description for the policy profile.

4.

Expand the Layer 3-7 profile options.

5.

Configure the global policy and log settings:
a. Enforcement: Enable or disable the Layer 3-7 policy profiles.
b. Default Action: Choose to deny or allow packets if the packets do not match any configured rules.
c. Log: Enable or disable logging Layer 3-7 policy events.

6.

Click theMXsecurity User Manual

icon to create a Layer 3-7 policy profile.

62

7.

Configure the Layer 3-7 Policy Profile settings:

a. Index: Specify the index for the policy profile.
b. Status: Enable or disable the policy profile.
c. Name: Enter a description for the policy profile.
d. Description: Enter a description for the policy profile.
e. Log: Enable or disable event logs.
f.

Severity: Select the log severity level.

g. Log Destination: If logging is enabled, choose where the logs will be stored. Multiple options canbe selected.
h. Incoming/Outgoing Interface: Select the incoming and outgoing interfaces.
i.

Action: Select the action when traffic matches the policy rule.

j.

Filter Mode: Select a filtering mode. Depending on the selected mode, configure the following
settings:
IP and Port Filtering:i.

Source/Destination IP Address: Select Any or a preconfigured Filter Object. Refer toCreating a New Filter Object.

ii.

Source Port/Destination Port or Protocol: Select Any or a preconfigured Interface Object.
Refer to Creating a New Interface Object.

MXsecurity User Manual63

IP and Source MAC Binding:i.

Source MAC Address: Specify the source MAC address.

ii.

Source IP Address: Select a preconfigured Filter Object. Refer to Creating a New Filter
Object.

Source MAC Filtering:i.

Source MAC Address: Specify the source MAC address.

8.

Click CREATE to create the Layer 3-7 Policy Profile.

9.

Click APPLY.

Creating a New Session Control Policy Profile
Steps:
1.

Navigate to Management > Policy Profiles.

2.

Click the3.

Enter a name and description for the policy profile.

4.

Expand the Session Control profile options.

5.

Click theMXsecurity User Manual

icon to create a policy profile.

icon to create a Session Control policy profile.

64

6.

Configure the Session Control Profile settings:

a. Index: Specify the index for the policy profile.
b. Status: Enable or disable the policy profile.
c. Name: Enter a description for the policy profile.
d. Severity: Select the log severity level.
e. Log Destination: If logging is enabled, choose where the logs will be stored. Multiple options canbe selected.
f.

Action: Select the action when traffic matches the policy rule.

g. IP Address: Select Any or a preconfigured Filter Object. Refer to Creating a New Filter Object.
h. Port: Select Any or a preconfigured Interface Object. Refer to Creating a New Interface Object.
i.

Total TCP Connections: Specify the maximum allowed TCP connections.

j.

Concurrent TCP Requests: Specify the maximum allowed concurrent connections.

7.

Click CREATE to create the Session Control Policy.

8.

Click APPLY.

Creating a New DoS Policy Profile
Steps:
1.

Navigate to Management > Policy Profiles.

MXsecurity User Manual

65

2.

Click theicon to create a policy profile.

3.

Enter a name and description for the policy profile.

4.

Expand the DoS profile options.

5.

Configure the following settings:

a. DOS Setting: Check the box of the DoS types you want to enable. If you selected ICMP-Death,
SYN-Flood, or ARP-Flood, specify the packet limit.
b. Log: Enable or disable event logs.
c. Severity: Select the log severity level.
d. Log Destination: If logging is enabled, choose where the logs will be stored. Multiple options canbe selected.
6.

Click APPLY.

MXsecurity User Manual66

Creating a New IPS Policy Profile
Steps:
1.

Navigate to Management > Policy Profiles.

2.

Click the3.

Enter a name and description for the policy profile.

icon to create a policy profile.

4.

Expand the IPS profile options.

5.

Select a previously uploaded IPS software package version.
Refer to Software Package Management for more information.

6.

In the IPS rule table, check the box of the rule(s) you want to configure.
You can select multiple rules at once.

7.

Click the8.

Configure the following settings:

icon to configure the selected rule(s).

a. Status: Enable or disable the rule.
b. Action: Select the action when traffic matches the policy rule.
9.

Click APPLY to save the changes.

10. On the Policy Profiles screen, click APPLY.

MXsecurity User Manual67

Editing a Policy Profile
1.

Navigate to Management > Policy Profiles.

2.

Click the3.

Modify the profile settings.
For Layer 3-7 policy profiles, refer to Creating a New Layer 3-7 Policy Profile.
For Session Control policy profiles, refer to Creating a New Session Control Policy Profile.
For DoS policy profiles, refer to Creating a New DoS Policy Profile.
For IPS policy profiles, refer to Creating a New IPS Policy Profile.

4.

Click APPLY.

icon to edit the policy profile.

Deleting a Policy Profile
Steps:
1.

Navigate to Management > Policy Profiles.

2.

Check the box of the policy profile(s) you want to delete.

3.

Click the4.

When prompted to confirm, click DELETE.

icon to delete the selected profile(s).

Device Configuration Management
This section describes how to manage the device configuration database from MXsecurity.

Uploading a Device Configuration File From a Local Host
Steps:
1.

Navigate to Management > Device Configuration.

2.

Click theMXsecurity User Manual

icon to add a device configuration.

68

3.

Enter the name and description for the configuration file.

4.

Click NEXT.

5.

Select Upload Configuration from Local from the Upload Configuration Method drop-down menu.

6.

Drag and drop or browse to the device configuration file on the local machine.

7.

Click APPLY.

Uploading a Configuration From a Device
Steps:
1.

Navigate to Management > Device Configuration.

2.

Click theMXsecurity User Manual

icon to add a device configuration.

69

3.

Enter the name and description for the configuration file.

4.

Click NEXT.

5.

Select Upload Configuration from Device from the Upload Configuration Method drop-down menu.

6.

Select the device to back up and generate the configuration file from.

7.

Click APPLY.

NOTEEach device model can have a maximum of five configuration files. When this limit is reached, the Add
button will become unavailable.

MXsecurity User Manual70

7. Deployment

The Deployment section lets users configure multiple device groups at a time and check the synchronization
status between MXsecurity and the managed devices.
You can configure the following types of deployments in MXsecurity:•

General: Remove and reboot devices.

•

Policy Profiles: Deploy policy profiles to managed devices.

•

Software Packages: Upgrade the software package of managed devices.

•

Firmware: Upgrade the firmware of managed devices.

•

Device Configure: Deploy device configuration files to managed devices.

Rebooting a Managed Device
Steps:
1.

Navigate to Device Deployment > General.

2.

Check the box of the device(s) you want to reboot.
Click the3.

icon to reboot the selected device(s).

When prompted to confirm, click REBOOT.

MXsecurity User Manual71Scheduling a Managed Device Reboot
Rebooting a device may disrupt services or operations. To minimize the potential impact of rebooting
devices, users can schedule device reboots for specific times where they are least likely to affect operations.
Schedules can be configured to execute only once, or on a daily or weekly recurring basis.

Steps:
1.

Navigate to Device Deployment > General.

2.

Check the box of the device(s) you want to reboot.

3.

Click the4.

Select a scheduling mode:

icon to configure a reboot schedule for the selected device(s).

a. One Time: Select the date and time the device(s) will reboot. One-time schedules can be
configured for up to 30 days in the future. The reboot time should be set in 5-minute increments, forexample 16:05.

b. Daily: Select the time and the schedule period. Daily schedules can be configured for up to 90 daysin the future. For example, the selected device(s) will reboot every day at 05:00 from July 15

MXsecurity User Manual72through October 13.

c. Weekly: Select the day of the week, the time, and schedule period. Weekly schedules can be
configured for up to 90 days in the future. For example, the selected device(s) will reboot every
Monday, Wednesday, and Friday at 05:00 from July 15 through October 13.

5.

Click APPLY.

Deleting a Managed Device Reboot Schedule
Steps:
1.

Navigate to Device Deployment > General.

2.

Check the box of the device(s) with the reboot schedule you want to delete.

3.

Click the4.

When prompted to confirm, click DELETE.

icon to delete the selected reboot schedules.

Sending a Control SMS
The OnCell Series routers may be installed in areas outside the range of the base station coverage. If aconnection can be established, the signal may be extremely weak, leading to interruptions for applications. It
also makes it challenging for users to restore the device's external network connection via the web console or
SSH.

MXsecurity User Manual73However, if the cellular router’s SIM card can receive SMS messages, MXsecurity can remotely control thecellular router by sending SMS commands. Refer to the table below for an overview of available SMS
commands.
Command
System Restart
Cellular Start Connecting

Description
The device will reboot.
The device will enable the cellular data connection.

Cellular Stop Connecting
Start IPsec Tunnel

The device will disable the cellular data connection.
The device will establish the IPsec tunnel.

Stop IPsec Tunnel
Set DO On
Set DO Off
Switch SIM

The device will disconnect the IPsec tunnel.
The device will turn the status of the relay output to On.
The device will turn the status of the relay output to Off.
The device will restart the cellular module and switch to the SIM card installedin the other SIM slot.

Steps:
1.

Enable remote control functions on the OnCell secure router:a. Log in to the OnCell secure router’s web console.
b. Navigate to System > SMS > Remote Control List.
c. Enable the function(s) that you want to remotely control by SMS through MXsecurity.
For security reasons, all functions are disabled by default.

2.

In MXsecurity, navigate to Device Deployment > General.

3.

Check the box of an OnCell secure router.

4.

Click the5.

Select the SMS command you want to execute.

6.

Click Send.

MXsecurity User Manual

icon to send a control SMS.

74

NOTE
There is a one-minute wait timer between each SMS message. Once the wait timer expires runs out,
another SMS message can be sent.

NOTE
MXsecurity can send a maximum of 200 SMS control messages per device each month. A counter in the
top-right of Remote SMS Control page shows the number of sent messages.

Removing a Managed Device
Steps:
1.

Navigate to Device Deployment > General.

2.

Check the box of the device(s) you want to remove.

3.

Click the4.

When prompted to confirm, click DELETE.

MXsecurity User Manual

icon to remove the selected device(s).

75Deploying Policy Profiles to Managed Devices
You can deploy specific policy profiles to managed devices and check the synchronization status between
the device and MXsecurity.
The synchronization status can be one of the following:•

Sync: The policy profile has been successfully synced between MXsecurity and the device.

•

Not Sync: The policy profile failed to synchronize between MXsecurity and the device.

•

Out of Sync: Indicates the deployed policy profile has been modified on the device side.

•

Sync (modified): Indicates the deployed policy profile has been modified in MXsecurity.

Steps:
1.

Navigate to Device Deployment > Policy Profiles.

2.

Check the box of the device(s) you want to deploy a policy profile to.

3.

Click the4.

Select a previously configured policy profile.
Refer to Policy Profile Management for instructions on how to create policy profiles.

5.

Click APPLY.

icon to deploy a policy profile to the selected device(s).

Scheduling a Policy Profile Deployment forManaged Devices
Deploying a policy profile to a device may disrupt services or operations. To minimize the potential impact ofpolicy profile deployments, users can schedule the deployment for specific times where they are least likely
to affect operations. Schedules can be configured to execute only once, or on a daily or weekly recurring
basis.

MXsecurity User Manual76

Steps:1.

Navigate to Device Deployment > Policy Profiles.

2.

Check the box of the device(s) to configure.

3.

Click the4.

Select a scheduling mode:

icon to configure a policy profile deployment schedule for the selected device(s).

a. One Time: Select the date and time the device(s) will reboot. One-time schedules can be
configured for up to 30 days in the future. The reboot time should be set in 5-minute increments, forexample 16:05.

b. Daily: Select the time and the schedule period. Daily schedules can be configured for up to 90 daysin the future. For example, the selected device(s) will reboot every day at 05:00 from July 15
through October 13.

MXsecurity User Manual77

c. Weekly: Select the day of the week, the time, and schedule period. Weekly schedules can be
configured for up to 90 days in the future. For example, the selected device(s) will reboot every
Monday, Wednesday, and Friday at 05:00 from July 15 through October 13.

5.

Click APPLY.

Deleting a Policy Profile Deployment Schedule
Steps:
1.

Navigate to Device Deployment > Policy Profiles.

2.

Check the box of the device(s) with the deployment schedule you want to delete.

3.

Click the4.

When prompted to confirm, click DELETE.

icon to delete the selected deployment schedules.

Upgrading the Software Package of Managed
Devices
You can upgrade the software package of managed devices and check basic software package version
information.
You can check the following software package information:•

Package Version: Shows the version of the software package currently installed on the device.

•

Up-To-Date: Indicates if the currently installed version is up to date. If not, the latest available version
will be shown.

Steps:
1.

Navigate to Device Deployment > Software Packages.

2.

Check the box of the device(s) you want to upgrade the software package for.

MXsecurity User Manual

78

3.

Click theicon to upgrade the software package for the selected device(s).

4.

Select a previously uploaded software package to upgrade to.
Refer to Software Package Management for instructions on how to upload software packages.

5.

Click UPGRADE.

Scheduling a Software Package Deployment forManaged Devices
Deploying a software package to a device may disrupt services or operations. To minimize the potential
impact of software package deployments, users can schedule the deployment for specific times where they
are least likely to affect operations. Schedules can be configured to execute only once, or on a daily or
weekly recurring basis.
Users have the flexibility to choose either a specific version or the "Up-to-date" option for the security
package. If the "Up-to-date" option is selected, MXsecurity will deploy the most-recent version available inthe management database to the devices.

Steps:
1.

Navigate to Device Deployment > Software Packages.

2.

Check the box of the device(s) to configure.

3.

Click the4.

Select the software package version to deploy.
If you select Up-to-date, MXsecurity will deploy the latest version of the software package available in

MXsecurity User Manual

icon to configure a software package deployment schedule for the selected device(s).

79the database. If the device’s software package version is the same or newer than the latest database
version, the system will not perform the upgrade.
5.

Select a scheduling mode:a. One Time: Select the date and time the device(s) will reboot. One-time schedules can be
configured for up to 30 days in the future. The reboot time should be set in 5-minute increments, forexample 16:05.

b. Daily: Select the time and the schedule period. Daily schedules can be configured for up to 90 daysin the future. For example, the selected device(s) will reboot every day at 05:00 from July 15
through October 13.

c. Weekly: Select the day of the week, the time, and schedule period. Weekly schedules can be
configured for up to 90 days in the future. For example, the selected device(s) will reboot every
Monday, Wednesday, and Friday at 05:00 from July 15 through October 13.

6.

Click APPLY.

MXsecurity User Manual80Deleting a Software Package Deployment
Schedule
Steps:
1.

Navigate to Device Deployment > Software Packages.

2.

Check the box of the device(s) with the deployment schedule you want to delete.

3.

Click the4.

When prompted to confirm, click DELETE.

icon to delete the selected deployment schedules.

Upgrading the Firmware of Managed Devices
You can upgrade the firmware of managed devices and check basic firmware version information.
You can check the following firmware information:•

Package Version: Shows the firmware version currently installed on the device.

•

Up-To-Date: Indicates if the currently installed version is up to date. If not, the latest available version
will be shown.

Steps:
1.

Navigate to Device Deployment > Firmware.

2.

Check the box of the device(s) you want to upgrade the firmware for.

3.

Click theMXsecurity User Manual

icon to upgrade the firmware for the selected device(s).

81

4.

Select a previously uploaded firmware to upgrade to.
Refer to Firmware Management for instructions on how to upload firmware.

5.

Click UPGRADE.

Scheduling a Firmware Deployment forManaged Devices
Deploying firmware to a device may disrupt services or operations. To minimize the potential impact offirmware deployments, users can schedule the deployment for specific times where they are least likely toaffect operations. Schedules can be configured to execute only once, or on a daily or weekly recurring basis.
Users have the flexibility to choose either a specific version or the "Up-to-date" option for the firmware. If
the "Up-to-date" option is selected, MXsecurity will deploy the most-recent version available in the
management database to the devices.

Steps:
1.

Navigate to Device Deployment > Firmware.

2.

Check the box of the device(s) to configure.

3.

Click the4.

Select the firmware version to deploy.
If you select Up-to-date, MXsecurity will deploy the latest version of the firmware available in the
database. If the device’s firmware version is the same or newer than the latest database version, thesystem will not perform the upgrade.

5.

Select a scheduling mode:

MXsecurity User Manual

icon to configure a firmware deployment schedule for the selected device(s).

82a. One Time: Select the date and time the device(s) will reboot. One-time schedules can be
configured for up to 30 days in the future. The reboot time should be set in 5-minute increments, forexample 16:05.

b. Daily: Select the time and the schedule period. Daily schedules can be configured for up to 90 daysin the future. For example, the selected device(s) will reboot every day at 05:00 from July 15
through October 13.

c. Weekly: Select the day of the week, the time, and schedule period. Weekly schedules can be
configured for up to 90 days in the future. For example, the selected device(s) will reboot every
Monday, Wednesday, and Friday at 05:00 from July 15 through October 13.

6.

Click APPLY.

Deleting a Firmware Deployment Schedule
Steps:
1.

Navigate to Device Deployment > Firmware.

2.

Check the box of the device(s) with the deployment schedule you want to delete.

3.

Click theMXsecurity User Manual

icon to delete the selected deployment schedules.

83

4.

When prompted to confirm, click DELETE.

Deploying a Configuration to Managed Devices
You can deploy a previously uploaded configuration to managed devices. This is useful for quickly deploying
an identical configuration to multiple devices at once.

Steps:
6.

Navigate to Device Deployment > Device Configuration.

7.

Check the box of the device(s) you want to deploy the configuration to.

8.

Click the9.

Select a previously uploaded device configuration to deploy.
Refer to Device Configuration Management for instructions on how to upload a configuration.

icon to deploy the configuration to the selected device(s).

10. Click APPLY.

MXsecurity User Manual84Scheduling a Configuration Deployment forManaged Devices
Deploying a configuration to a device may disrupt services or operations. To minimize the potential impact
of configuration deployments, users can schedule the deployment for specific times where they are least
likely to affect operations. Schedules can be configured to execute only once, or on a daily or weekly
recurring basis.

Steps:
1.

Navigate to Device Deployment > Device Configuration.

2.

Check the box of the device(s) to configure.

3.

Click the4.

Select a previously uploaded configuration file to deploy.

5.

Select a scheduling mode:

icon to configure a configuration deployment schedule for the selected device(s).

a. One Time: Select the date and time the device(s) will reboot. One-time schedules can be
configured for up to 30 days in the future. The reboot time should be set in 5-minute increments, forMXsecurity User Manual85

example 16:05.

b. Daily: Select the time and the schedule period. Daily schedules can be configured for up to 90 daysin the future. For example, the selected device(s) will reboot every day at 05:00 from July 15
through October 13.

c. Weekly: Select the day of the week, the time, and schedule period. Weekly schedules can be
configured for up to 90 days in the future. For example, the selected device(s) will reboot every
Monday, Wednesday, and Friday at 05:00 from July 15 through October 13.

6.

Click APPLY.

Deleting a Configuration Deployment Schedule
Steps:
1.

Navigate to Device Deployment > Device Configuration.

2.

Check the box of the device(s) with the deployment schedule you want to delete.

3.

Click theMXsecurity User Manual

icon to delete the selected deployment schedules.

86

4.

When prompted to confirm, click DELETE.

MXsecurity User Manual878. Map View

The Map View feature allows network administrators to identify the current location of devices, the interfaces
in use, and the quality of the connection. For secure routers equipped with a GPS module such as OnCell
devices, the map will display their exact location on the map if the GPS function is enabled on the device. For
devices without a GPS module, users can manually enter the latitude and longitude details.

Refer to the following sections for more information about each function of the map.

Basic Functions
From the Map View screen, you can perform the following basic functions.
Icon

Function

Description

RefreshClick the Refresh button to update the map with the latest GPS data.

SearchSearch for a device by serial number, device name, or MAC address.

FilterFilter the devices to display on the map based on device type, online status, andconnection type
Click the corresponding icon to zoom in or zoom out on the map.
When zoomed out too far, devices in an adjacent area will be grouped together

Zoom in/out

and shown as a single, numbered dot ().
The number inside the dot represents the number of devices in that area. Zoom in
to view the device icons individually.

Signal Level
The map shows the current signal strength of managed devices. Refer to the table below for an overview of
each status.
Icon

Description
The cellular signal RSSI is higher than -73 dBm or the Ethernet WAN link is up.
The cellular signal RSSI is between -73 to -89 dBm.
The cellular signal RSSI is between -89 to -113 dBm.

MXsecurity User Manual88

No cellular signal or the Ethernet interface link is down.

Interface in Use
The device icons on the map show which interface is being used to connect to the Internet. Refer to thetable below for an overview of each interface.
Icon Description
The device is using Ethernet WAN to connect to the internet.
The device is using cellular 5G to connect to the internet.
The device is using cellular 4G to connect to the internet.
The device is using cellular 3G to connect to the internet.
The device is using cellular 2G to connect to the internet.
The device is using Wi-fi to connect to the internet.

Viewing Detailed Device Information
Clicking the device icon on the map or the device name from the No Location Devices list will bring up
additional information about the device.

Steps:
1.

Navigate to Map View.

2.

Click the device’s icon on the map or the device name in the No Location Devices list.

3.

Depending on the selected device, the following information will be shown:

MXsecurity User Manual89

a. Basic Information: Basic information about the device, including device name, model, S/N, IP
LAN/WAN address, MAC address, location, and firmware version.

b. Cellular Information: Information about the cellular interface, connection, carrier, and SIM. This is
only available for OnCell devices.

Editing the Location of a Device
For managed devices that do not support GPS or have their GPS module disabled, users can manually enter
geographic coordinates to display the device on the map.

Steps:
1.

Navigate to Map View.

2.

In the No Location Devices list, click the device name.

MXsecurity User Manual

90

3.

Click

the icon in the Location field.

4.

Enter the longitude and latitude coordinates.

5.

Click

6.

Click the.

icon on the map to refresh the map.

The device will now appear on the map based on the specified coordinates.

MXsecurity User Manual919. Report

The Report function simplifies audits and reviewing cellular secure router performance. Users can also set
up an email server to send reports directly to network administrators.

This section will provide information for the following reports:•

Inventory Reports: List of all assets of the devices in the field.

•

Cellular Signal Reports: The signal status of managed cellular secure routers.

•

Data Usage Reports: The status of the managed cellular secure routers’ SIM card data usage.

•

Trail Reports: The GPS movement tracking records of managed cellular secure routers.

Inventory Reports
Generating a Current Inventory Report
Inventory reports make it easier for users to conduct audits and to monitor the number of field devices andtheir status.

Steps:
1.

Navigate to Report > Inventory.

2.

Select all devices.

3.

Click theMXsecurity User Manual

icon to generate a report in CSV format.

92

The inventory report includes the following information:

The following table describes the report’s fields.
Field
Create AccountReport Generated Date
Report Generated Time
Product Model Statistics
Online / Offline Statistics

Description
The MXsecurity account used to generate the report.
The date the report was generated.
The time the report was generated.
A summary of the total number of managed devices, organized according byproduct model.
A summary of the total number of managed devices, organized according bystatus.

Scheduling an Inventory Report
Users can generate inventory reports according to a pre-configured schedule and automatically send it tospecified recipients by email.

Steps:
1.

Navigate to Report > Inventory.

MXsecurity User Manual

93

2.

Select all devices.

3.

Click the4.

Specify the email recipients for the report. You can specify up to 5 recipients.

icon to configure a report schedule.

5.

Enter the subject. This will act as the report email subject.

6.

Select a scheduling mode:a. One Time: Select the report date. One-time schedules can be configured for up to one year in the
future.

b. Monthly: Select the report date and period. Monthly schedules can be configured for up to one year
in the future.

7.

Click APPLY.
The schedule will appear on the Report > Report Setting > Schedule Report page.

MXsecurity User Manual94

Cellular Signal Reports
Scheduling a Cellular Signal Report
Users can generate cellular signal reports according to a pre-configured schedule and automatically send it
to specified recipients by email.

Steps:
1.

Navigate to Report > Cellular Signal.

2.

Select the device(s) you want to generate a report for.

3.

Click the4.

Specify the email recipients for the report. You can specify up to 5 recipients.

5.

Enter the subject. This will act as the report email subject.

6.

Select a scheduling mode:

icon to configure a report schedule.

a. One Time: Select the report date. One-time schedules can be configured for up to one year in the
future. To ensure complete 24-hour data, the report data will be of the day prior to the report date.

b. Daily: Select the report period. Monthly schedules can be configured for up to one year in the
future. To ensure complete 24-hour data, the report data will be of the day prior to the report date.

7.

Click APPLY.
The schedule will appear on the Report > Report Setting > Schedule Report page.

MXsecurity User Manual95Data Usage Reports
Generating a Cellular Data Usage Report
Cellular data usage reports provide useful insights into the data usage of SIM cards for a specific period. The
report will include a separate CSV file for each selected OnCell secure router.

Steps:
1.

Navigate to Report > Data Usage.

2.

Select the device(s) you want to generate a report for.

3.

Click the4.

Select the report period.

MXsecurity User Manual

icon to generate a report in CSV format.

96

NOTE
You can select a period of up to 30 days within the last 90 days.

NOTE
If you select the current day, the data included in the report will span from 00:00 of that day to thepresent time.
5.

Click DOWNLOAD.

The cellular data usage report includes the following information:

The following table describes the report’s fields.
Field
Create AccountReport Generated Date
Report Generated Time
Data Period
Device Name
Device MAC Address
Device Serial Number
Data Usage (Total Usage)
Data Usage (Daily Usage)

MXsecurity User Manual

Description
The MXsecurity account used to generate the report.
The date the report was generated.
The time the report was generated.
The period for which the data was collected.
The name of the device.
The device MAC address.
The device serial number.
Summary chart showing the cumulative total data usage in MB.
Summary chart showing the daily data usage in MB.

97

Scheduling a Cellular Data Usage Report
Users can generate cellular data usage reports according to a pre-configured schedule and automaticallysend it to specified recipients by email.

Steps:
1.

Navigate to Report > Data Usage.

2.

Select the device(s) you want to generate a report for.

3.

Click the4.

Specify the email recipients for the report. You can specify up to 5 recipients.

5.

Enter the subject. This will act as the report email subject.

6.

Select a scheduling mode:

icon to configure a report schedule.

a. One Time: Select the report date. One-time schedules can be configured for up to one year in the
future. To ensure complete 30-day data, the report data will be of the month prior to the report
date.

b. Monthly: Select the report date and period. Monthly schedules can be configured for up to one year
in the future. To ensure complete 30-day data, the report data will be of the month prior to thereport date.

7.

Click APPLY.
The schedule will appear on the Report > Report Setting > Schedule Report page.

MXsecurity User Manual98Trail Reports
Generating a Trail Report
Trail reports let users compile GPS trail records for each device. This information is useful for auditing andmanagement purposes. The collected data can help optimize operations in a variety of applications. For
example, trail reports can show the trajectory of a vehicle with an OnCell secure router on board using GPS
trail records. Based on this report data, administrators can optimize vehicles routes and schedules.

Steps:
1.

Navigate to Report > Trail.

2.

Select the device(s) you want to generate a report for.

3.

Click the4.

Select the report period.

MXsecurity User Manual

icon to generate a report in CSV format.

99

NOTE
You can select a period of up to 30 days within the last 90 days.

NOTE
If you select the current day, the data included in the report will span from 00:00 of that day to thepresent time.
5.

Click DOWNLOAD.

The trail report includes the timestamps and GPS coordinates of the device. Users can import this data into
third-party software to visualize the locations of the device.

Scheduling a Trail Report
Users can generate trail reports according to a pre-configured schedule and automatically send it tospecified recipients by email.

Steps:
1.

Navigate to Report > Trail.

2.

Select the device(s) you want to generate a report for.

3.

Click the4.

Specify the email recipients for the report. You can specify up to 5 recipients.

MXsecurity User Manual

icon to configure a report schedule.

100

5.

Enter the subject. This will act as the report email subject.

6.

Select a scheduling mode:a. One Time: Select the report date. One-time schedules can be configured for up to one year in the
future. To ensure complete 24-hour data, the report data will be of the day prior to the report date.

b. Daily: Select the report date and period. Monthly schedules can be configured for up to one year in
the future. To ensure complete 24-hour data, the report data will be of the day prior to the report
date.

7.

Click APPLY.
The schedule will appear on the Report > Report Setting > Schedule Report page.

Viewing GPS Trajectories
To visualize and improve the quality of trail reports, MXsecurity supports an online GPS trajectory view fortrail reports. This feature allows users to easily track and analyze movement patterns within their network,
providing a more intuitive and efficient way to understand network dynamics.

Steps:
1.

Navigate to Report > Trail.

MXsecurity User Manual

101

2.

Click on the device name.
The device’s GPS trajectory map will appear.

3.

Select a date to show the device’s GPS movement history up until that day.

Report Settings
From the Report Settings tab, users can set the report time zone and manage configured report schedules.

Configure Report Time Zone Settings
The device and MXsecurity might be deployed in different time zones. To ensure correct report data, users
can configure the time zone for reports.

Steps:
1.

Navigate to Report > Report Setting > Time Zone Setting.

2.

Select the time zone from the drop-down menu.

3.

Click APPLY.

MXsecurity User Manual102

Editing a Report Schedule
Steps:
1.

Navigate to Report > Report Setting > Schedule Report.

2.

Select the schedule you want to modify.

3.

Click the4.

When finished editing the schedule, click APPLY.

MXsecurity User Manual

icon to edit the schedule.

103

10.

Logging

This chapter covers the event log and notification functions. Users can view logs related to the device,
firewall, VPN, and audits. The notification function enables users to receive notifications for particular event
logs. Users can send these notifications to designated email recipients or a syslog server.

Event Log
The event log contains all system- and device-related logs. Logs are categorized by type, including device,
firewall, VPN, and audit logs. Refer to the following sections for more information about each log type.

Device Log
The device log records interactions between the device and MXsecurity, such as Device Added, Device
Deleted, Device Online/Offline, Device Deployment Success/Failure, and Send SMS.

Viewing Device Logs
Steps:
1.

Navigate to Logging > Event Log > Device.

2.

You can perform the following actions:a. Click theicon to open the filter menu. Select a start/end day and time or log severity from therespective drop-menu.

MXsecurity User Manual104

Click the

button to configure advanced filters. Check the box of the specific event(s) you

want to filter. Click APPLY. The logs will renew immediately to reflect the selected criteria.

b. Click the

button to export the current search results as a CSV file.

c. Click the

button to renew the search results.

The following table describes the log’s fields.
Field
Time
Severity
Event
Device Name
Username
MessageGroup Name
MAC Address

MXsecurity User Manual

Description
The time the log entry was created.
The severity level assigned to the system event.
The category of the system event.
The hostname of the device that generated the log.
The username of the user that generated the log.
This field displays a detailed description of the event.
The group name of the device group that generated the log.
The MAC address of the device that generated the log.

105

Firewall Log
The firewall logs include logs detected by the Trusted Access, Malformed Packets, DoS policy, L3-L7 policies,
protocol filter policies, ADP, IPS and Session Control features.

Viewing Firewall Logs
Steps:
1.

Navigate to Logging > Event Log > Firewall.

MXsecurity User Manual

106

2.

Select the firewall function event log type from the drop-down menu.

3.

You can perform the following actions:a. Click theicon to open the filter menu. Select a start/end day and time or log severity from therespective drop-menu.

MXsecurity User Manual107Click the

button to configure advanced filters. Check the box of the specific event(s) you

want to filter. Click APPLY. The logs will renew immediately to reflect the selected criteria.

b. Click the

button to export the current search results as a CSV file.

c. Click the

button to renew the search results.

The following table describes the log’s fields.
Field
Index
Time
Severity
Device HostnameGroup NameIPS Severity
IPS Category
Ethernet TypeIP Protocol
Incoming Interface
Source MAC
Source IP

MXsecurity User Manual

Description
The index of the log.
The time the log entry was created.
The severity level assigned to the firewall event.
The host name of the device that generated the log.
The group name of the device group that generated the log.
The severity level assigned to the IPS event.
The category of the IPS event.
The Ethernet type of the connection.
The IP protocol of the connection.
The name of the incoming interface where the event was registered.
The source MAC address of the connection.
The source IP address of the connection.

108

FieldSource Port
Outgoing Interface
Destination IP
Destination PortTCP Flags
ICMP TypeICMP CodeActionAdditional Message

MXsecurity User Manual

Description
The source port of the connection.
The name of the outgoing interface where the event was registered.
The destination IP address of the connection.
The destination port of the connection.
The TCP flags of the TCP protocol.
The ICMP type of the ICMP protocol.
The ICMP Code of the ICMP protocol.
The action performed based on the policy settings.
The additional message provided with the log.

109

VPN Log
The VPN logs show details about the status of tunnel connections and related events.

Viewing VPN Logs
Steps:
1.

Navigate to Logging > Event Log > Audit.

2.

You can perform the following actions:a. Click theicon to open the filter menu. Select a start/end day and time or log severity from therespective drop-menu.

MXsecurity User Manual110Click the

button to configure advanced filters. Check the box of the specific event(s) you

want to filter. Click APPLY. The logs will renew immediately to reflect the selected criteria.

b. Click the

button to export the current search results as a CSV file.

c. Click the

button to renew the search results.

The following table describes the log’s fields.
Field
Time
Severity
Event
Additional Message
Device Hostname
Username
Group Name

Description
The time the log entry was created.
The severity level assigned to the system event.
The category of the system event.
The additional message provided with the log.
The host name of the device that generated the log.
The username of the user that generated the log.
The group name of the device group that generated the log.

Audit Log
The audit logs show details about user access, configuration changes, and other events that occurred whenusing MXsecurity.

MXsecurity User Manual111

Viewing Audit Logs
Steps:
1.

Navigate to Logging > Event Log > Audit.

2.

You can perform the following actions:a. Click theicon to open the filter menu. Select a start/end day and time or log severity from therespective drop-menu.

Click thebutton to configure advanced filters. Check the box of the specific event(s) you

want to filter. Click APPLY. The logs will renew immediately to reflect the selected criteria.

b. Click the

button to export the current search results as a CSV file.

c. Click the

button to renew the search results.

The following table describes the log’s fields.
Field
Time

MXsecurity User Manual

Description
The time the log entry was created.

112

FieldSeverity
Event
Device Hostname
Username
Group Name

Description
The severity level assigned to the system event.
The category of the system event.
The host name of the device that generated the log.
The username of the user that generated the log.
The group name of the device group that generated the log.

Event Log Settings
From the Setting tab, users can check the status of event logs stored on the local drive and configure log
purging settings.

Purging Event Logs
The log purging function allows users to configure automatic log purging based on the specified retention
time and log amount. Purging logs may be useful when the system generates a lot of event logs, which may
affect network performance.
When the retention time or the number of entries for a log type exceeds the set threshold, MXsecurity will
start clearing the logs, starting with the oldest records.
1.

Navigate to Logging > Event Log > Setting.

2.

In the Disk Usage section, check the current used and available disk space.

MXsecurity User Manual

113

3.

In the Purge Settings section, select the retention time and number of entries to retain for each log
type.

4.

(Optional) In the Event Log Auto Refresh section, disable or select the interval at which the event log
data will refresh.

5.

Click APPLY.

Notifications
The Notification tab allows users to set up notifications for specific events. Users can configure thesenotifications to be sent by email or sent to a Syslog server.

Adding a Notification
Steps:
1.

Navigate to Logging > Notifications.

2.

Click theMXsecurity User Manual

icon to add a notification.

114

3.

Enter a name and description for the notification.

4.

Click NEXT.

5.

Select the device(s) that will send notifications for the specified events.

6.

Select the event types and configure filter rules:
a. Select the event type.

MXsecurity User Manual115

b. Specify the notification filter rules to determine when the device will send a notification for the
event. Depending on the select notification event, filter rule options will be different.

7.

Configure the notification content and recipient settings.

a. Select the notification delivery method. Multiple methods can be selected.
b. Edit the notification content using the predefined variables.
c. If Email is selected, specify the email recipients. You can add up to 5 recipients separated by acomma.
8.

Configure Advanced Settings. To prevent an influx of messages in a short period, users can configure alimit on the number of notifications for a specified interval. When exceeded, all additional notifications
will be discarded until the next interval begins.

a. Enable or disable the notification limit.
b. Specify the maximum number of notifications.

MXsecurity User Manual116

c. Specify the interval duration.
9.

Click APPLY.

MXsecurity User Manual

117

11.

Administration

This chapter describes the available administrative settings for MXsecurity.

User Accounts
NOTE
Log in to the management console using the default administrator account (“admin”) or any account withadministrator privileges to access the User Accounts screens.
MXsecurity uses role-based administration to grant and control access to the management console. Use thisfeature to assign specific management console privileges to user accounts and present them with only thetools and permissions necessary to perform specific tasks. Each account is assigned a specific role. A role
defines the level of access to the management console. Users can log in to the management console using
custom user accounts.

The following table outlines the tasks available on the User Accounts tab.
Task

Description

Add a user accountClick theicon create a new user account.
For more information, see Adding a User Account.

Delete an existing accountSelect one or more existing user accounts and click the
For more information, see Deleting a User Account.

Edit an existing accountConfigure the password
policyicon.

Click theicon next to an existing user account to view or modify thecurrent account settings.
For more information, see Editing an Existing User Account.
Click Password Policy to adjust password restrictions.
For more information, see Configuring the Password Policy.

User RolesThe following table describes the permissions matrix for user roles.

Dashboard
Configuration Screen Action
View
Dashboard
All operations

MXsecurity User Manual

User Roles
Admin
Yes
Yes

Operator
VG
VG

ViewerVG
VG

118

System Tab
Configuration Screen Action
View
User Accounts
All operations
View
Licenses
All operations
View
Settings
All operations

User Roles
Admin
Yes
Yes
Yes
Yes
Yes
Yes

Operator
No
No
No
No
No
No

Viewer
No
No
No
No
No
No

User Roles
Admin
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes

Operator
VG
No
Yes
No
Yes
No
Yes
No
Yes
No
VG
No

Viewer
No
No
No
No
No
No
No
No
No
No
No
No

Management Tabs
Configuration Screen Action
View
Device GroupAll operations
View
Firmwares
All operations
View
Software Packages
All operations
View
Objects
All operations
View
Policy Profiles
All operations
View
Device Configuration
All operations

NOTE
VG denotes that if the administrator has assigned/shared the device group permissions with a specific user
account, then that user can view the information for that device group on the Management/Device Groups
pages.

Device Deployment
Configuration Screen Action
View
Device Deployment
All operations

User Roles
Admin
Yes
Yes

Operator
VG
VG

ViewerNo
No

NOTE
VG denotes that if the administrator has assigned/shared the device group permissions with a specific user
account, then that user can view the information for that device group on the Device Deployment page.

Map View
Configuration Screen Action
View
Map View
All operations

MXsecurity User Manual

User Roles
Admin
Yes
Yes

Operator
VG
VG

ViewerVG
No

119

ReportConfiguration Screen Action
View
All operations
Reports

User Roles
Admin
Operator
Yes (All users) VG (Self)
Write (Self)
VG (Self)
Delete (Allusers)

Viewer
VG (Self)
VG (Self)

Logging
Configuration Screen Action
View
Event Log
All operations
View
All operations
Notification

User Roles
Admin
Yes
Yes
Yes
Write (Self)
Delete (Allusers)

Operator
VG
VG
VG (Self)
VG (Self)

ViewerVG
No
VG (Self)
VG (Self)

NOTE
VG denotes that if the administrator has assigned/shared the device group permissions with a specific user
account, then that user can view the information for that device group on the Logging/Event Log pages.

Account Input Format
Input format validation will apply to the account management form text fields. The following table describes
the format restrictions for user input.

MXsecurity User Manual

120

Type

LengthUsername

1 to 32
characters

Description

0 to 255
characters

FormatLetters: a-z, A-Z
Numbers: 0-9
Special characters: periods (.), underscores (_)

Reserved Nameadminadministrator
vieweroperatorroot
auditor

Letters: a-z, A-Z
Numbers: 0-9
Special characters: periods (.), underscores (_),
spaces, parenthesis [ ( , ) ], hyphens (-)

Adding a User AccountWhen logging in with an administrator account, you can create new user accounts for accessing MXsecurity.

Steps:
1.

Navigate to System > User Accounts > Account List.

2.

Click theMXsecurity User Manual

icon.

121

The Create User screen will appear.

3.

Configure the following settings:
a. Username: Enter the username used to log in to the management console.
b. Password: Enter the account password.
c. Confirm Password: Enter the account password again to confirm.
d. Role: Select a user role for this account. For more information, see User Roles.
e. Description: Enter a description for this account.

4.

Click APPLY.

Editing an Existing User AccountSteps:
1.

Navigate to System > User Accounts > Account List.

2.

Click the3.

Modify the user account settings. Refer to Adding a User Account for more information.

4.

Click APPLY.

MXsecurity User Manual

icon next to the user account you want to modify.

122

Deleting a User AccountSteps:
1.

Navigate to System > User Accounts > Account List.

2.

Check the box of the user account(s) you want to delete.

3.

Click the4.

When prompted to confirm, click DELETE.

icon to delete the selected user account(s).

Configuring the Password Policy
To improve password strength, the administrator can customize the password policy from the Password
Policy screen.

Steps:
1.

Navigate to System > User Accounts > Password Policy.

MXsecurity User Manual

123

2.

Select the option(s) to apply to the password policy.

3.

Click APPLY.

Changing Your Account Password
Steps:
1.

Click theicon in the top-right of the management console banner.

2.

Click Change Password.
The Change Password screen will appear.

3.

Configure the following settings:
a. Current Password: Enter your current password.

MXsecurity User Manual124b. New Password: Enter your new password.
c. Confirm New Password: Enter your new password again.
4.

Click APPLY. This will automatically log you out and return you to the login screen.

Licenses
From the License tab you can view license information and manage license keys to enable specific functions
within MXsecurity.

NOTE
Only user accounts with administrator privileges can access the Licenses screen.

Introduction to Licenses
MXsecurity supports two types of licenses:•

MXsecurity licenses: Determines the maximum number of nodes that can be managed by MXsecurity.

•

IPS licenses: The number of seats allowed in the license should be equal to or greater than the nodes
managed by MXsecurity, so that IPS functionality is enabled and can be managed via MXsecurity.

NOTE
Only one IPS license can be used at any given time. When more than one IPS license is applied to
MXsecurity, only the latest one will be kept.

Viewing Your Product License Information
Steps:
1.

Navigate to System > Licenses.
The Licenses screen will appear.

2.

Click the MXsecurity or IPS tab to view information for the respective license type.

The following table describes the license information.

MXsecurity User Manual125FieldName
Valid forTotal Nodes
Used Nodes
Start Date
End Date
StatusMXsecurity ID

Description
The name of the license.
The remaining duration the license is valid for.
The number of nodes that can be managed by this license.
The number of used nodes on the license.
The start date of the license.
The expiration date of the license.
The status of the license.
The unique ID of this MXsecurity instance.

The following table describes the license history.
MessageUpdate Date
Activation CodeLicense Type
License Duration
License Nodes

Description
The date of this license was entered.
The activation code of the license.
The type of license.
The duration of the license.
The number of nodes of the license.

Alert Messages
When a license is about to expire or has expired, alert messages will pop-up when the user logs in to the
web management console.
Message
The (category) license expires in (days) days. To
continue using all features, enter a new licensecode.
The (category) license has expired. To continue
using all features, enter a valid license code.

MXsecurity User Manual

Description
This message appears 30 days before the license
expiration date. The (days) represents the days
remaining before the license expires.
The license has expired, and you will be required topurchase a new license to continue using the product.

126

Adding a New License
You can activate a license using a valid license activation code.

Steps:
1.

2.

Navigate to System > Licenses.

Click thebutton.

The Add New License screen will appear.

3.

Follow the on-screen instructions for activating the license in the Moxa License Portal.

4.

Enter the activation code provided by the Moxa License Portal into MXsecurity.

5.

Click APPLY.

6.

Verify the license information is correct.

Binding a License to a Device
To enable specific functions on devices, you need to bind the appropriate license to the managed device
first.

Steps:
1.

Navigate to System > Licenses.

2.

Click the IPS tab.

3.

In the Device License Binding section, check the box of the device(s) you want to bind the license to.

4.

Click theMXsecurity User Manual

icon to bind the license to the selected device(s).

127

5.

When prompted to confirm, click APPLY.

Unbinding a License From a Device
You can unbind a license from a managed device in order to assign it to another device. Note that unbinding
a license will cause the relevant function to become unavailable on that device.

Steps:
1.

Navigate to System > Licenses.

2.

Click the IPS tab.

3.

Check the box of the device(s) you want to unbind the license from.

4.

Click the5.

When prompted to confirm, click REMOVE.

MXsecurity User Manual

icon to unbind the license from the selected device(s).

128

i.

Settings
From the Settings page, you can configure system preferences, time, and log purge settings.

Configuring Preferences
From the Preferences screen, you can confirm basic settings for the MXsecurity instance.

Steps:
1.

Navigate to System > Settings > Preferences.

2.

Select the duration and interval for the auto logout and dashboard auto refresh functions respectively.

3.

Click APPLY.

Configuring the System Time
From the Time tab, you can manually set the system time. MXsecurity will automatically synchronize thesystem time with all managed nodes.

Steps:
1.

Navigate to System > Settings > Time.

2.

Click theMXsecurity User Manual

icon to select the date.

129

3.

Click the4.

Click APPLY.

icon to select the time.

Editing Email Settings
From the Email tab, you can configure email server settings. These settings must be configured to use
certain functions, such as email notifications and scheduled report sending.

Refer to the table below for an overview of each setting.
Field
SMTP Domain Name or
IP address
SMTP Server Port
Sender Email Address
Secure Connection

Email Authentication
Account
Password

MXsecurity User Manual

Description
The SMTP server domain name or IP address.
The communication port of the SMTP server. The recommended port is 587.
The email address used to send notifications or reports.
Enable or disable SSL (port 587) to establish a connection to the SMTP server. Thisfunction depends on the settings of the SMTP server. In most cases, servers requirea secure connection.
Enable or disable email authentication. If enabled, MXsecurity requires an accountand password for email authentication with the SMTP server.
If email authentication is enabled, enter email account name.
If email authentication is enabled, enter the authentication account password.

130

NOTE
If you set a Gmail account as the sender address, we highly recommend enabling “2-step verification” andgetting a 16-bit application password. For details, refer “Gmail-Help center - Sign in with Passwords” formore information.
Click TEST EMAIL to test the configuration.
When finished, click APPLY.

Editing Syslog Settings
From the Syslog tab, you can configure the syslog server to which MXsecurity will send syslog messages to.

Refer to the table below for an overview of each setting.
Field
Send logs to Syslog
serverServer Address/
Domain NamePort
FormatDescription
Enable or disable sending syslog messages to the Syslog server.
The IP address or domain name of the syslog server.
The port number of the syslog server. The default port is 514.
The syslog event format used for the syslog server. The default format is LEEF.
Available options include: CEF.

Click SEND TEST SYSLOG to test the configuration.
When finished, click APPLY.

MXsecurity User Manual131