Version 3.5.0 On-Premises

February 2026

Important

• Refer to the knowledge base article, How to Upgrade SonicCore and NSM in Closed Network for detailed instructions on upgrading NSM in closed network environment.
• Refer to the knowledge base article, Upgrade using management console for detailed instructions on a system upgrade. Prior to update, you need to create a system backup of the NSM on-premises system in case you need to roll back to the prior version. Refer to Backup and Restore an NSM On-Prem System for detailed instructions.

• Refer to knowledge base article, How to Upgrade On-Prem Network Security Manager firmware for detailed instructions on upgrading NSM firmware using SWI files.

Compatibility and Installation Notes

• Most popular browsers are supported, but Google Chrome is preferred for the real-time graphics display on the Dashboard.
• A MySonicWall account is required.

• Capacity Requirements: The capacity requirements for an NSM On-Premises deployment have changed:

  Supported Platforms

  Platform	Platform Details
  VMware	Supported versions: ESXi 7.0, 8.0
  Hyper-V	Windows 2019, 2022
  KVM	Linux Kernel 5.15 LTS
  Azure	Standard_D4_v2 Standard_D5_v2 Standard_D16as_v5 Standard_D8as_v5

  Management Only

  Number of Firewalls	CPU (Cores)
  100	4
  150	4
  250	8
  500	8
  750	8
  1000	8
  1000+	16

  Management Only

  Number of Firewalls	CPU (Cores)	RAM (GB)
  100	4	16
  150	4	16
  250	8	16
  500	8	16
  750	8	16
  1000	8	16
  1000+	16	32

  Management, Reporting and Analytics

  Number of Firewalls	CPU (Cores)	RAM (GB)
  100	4	24
  150	4	24
  250	8	24
  500	8	32
  750	8	32
  1000	8	32
  1000+	16	64

  Reporting Disk Space Requirements (Data Storage + Cache)/SSD

  Number of Firewalls	Data Retention 7 days	Data Retention 365 days
  50	600 GB	750 GB
  100	1.2 TB	1.5 TB
  150	1.7 TB	2.3 TB
  250	2.8 TB	4 TB

  Distributed Deployments Sizing Guideline

  Number of Firewalls	NSM Nodes
  ≤ 250	NSM Controller Node / Single Node Deployment
  > 250	Controller Node + 1 Reporting Agent per 250 firewall
  Reporting Agent resource requirements (CPU and RAM ) is the same as the controller node.

• Upgrade Instructions:

  • We strongly recommend using the system update method to upgrade NSM using steps captured in the Upgrade using management console.
  • Minimum 50% of the free disk space is required to upgrade.

  Current Build	Upgrade Path to 3.5.0 On-Prem
  NSM 3.2.0	NSM 3.2.0 > NSM 3.5.0
  NSM 3.2.1	NSM 3.2.1 > NSM 3.5.0

What's New

• NSM template enhancements

  • Support Firewall Auto Firmware upgrade settings in template view

  • Support for template variables in DDNS settings

• Improvements in firewall EXP and TSR backups

  • Alert user at EXP or TSR backup failure

  • Ability to specify the number of EXP and TSR backups per backup rule

  • Secure EXP and TSR files with user-defined passwords.

  • A new layout shows the status of each firewall’s EXP backup in the EXP backup rule.

  • The device list for EXP backups now supports advanced search and sort options during selection or editing.

• Alert and Notifications

  • Ability to specify non-SonicWall user IDs for email alert notification

  • Customize notifications for Interface and Firewall connectivity alerts using advanced settings.

  • Ability to configure notifications for use of a publicly known password secret used for firewall login. This feature requires turning on the credential Auditor feature on NSM.

• Usability Improvements

  • Granular details included for error reporting on the commit page.

  • Introduced a one-step migration of firewalls from one device group to another.

  • Commits are now grouped by their identifier across all commit types to enhance readability.

  • The variable resolution table at the All-Tenants level includes a Tenant Name column to improve usability.

  • Users can now cancel a pending commit in scenarios where the Don’t time out Pending Commits option is enabled.

  • Consistent time sliders across all reporting and analytics pages.

  • Ability to update the default NSM administrator username

  • Ability to delete multiple uploaded Firewall Firmware Files from the NSM inventory

• Migration App Improvement

  • Introduced an enhanced list of supported migration paths, along with the capability to migrate to TZ280W and TZ280P models.

• NSM supports automated remediation of local user passwords and resetting TOTP key bindings.

• Added support for the upcoming SonicOS 8.2.0 and SonicOS 7.3.2 releases. These versions are planned for release by the end of February 2026. For details on new features and enhancements, refer to the SonicOS release notes when available.

• Option to exclude uploaded firewall firmware image from NSM backups.

Resolved Issues

Issue ID	Description
NSM-34793	Firmware 7.3.1-7013 was reported as vulnerable to SSLVPN NULL Pointer Dereference DDoS.
NSM-34615	Login failure during 2FA, resulting in an internal server error.
NSM-31164	Received logs or connection failures in the event logs on NSM On-Premises.

Known Issues

Issue ID	Description
NSM-35659	Receiving error invalid file format while uploading bin.sig file. This is an intermittent issue.
NSM-34216	Customers will get error when upgrading from 3.2.0 to 3.5.0 or 3.2.1 to 3.5.0 but upgrade will still happen.

Additional References

NSM-36014, NSM-35664, NSM-35565, NSM-34252, NSM-34022