Network Security Manager SaaS Release Notes
Table of Contents
Version 4.3.0
July 2026
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.
- Refer to Network Security Manager for OnPrem and SAAS- System Requirements for the latest information on hardware requirements, operating systems, and browser levels.
What's New
- Support for the SonicOS 8.2.2 release.
- Support for new Virtual Firewall models NSv S, M, and L.
- Enhancement to the filtering capability on the firmware upgrade status page.
- URL Reputation data is now available in the analytics session log view, list view, graph view, and productivity report.
Resolved Issues
|
Issue ID |
Description |
|---|---|
|
NSM-34224 |
Source reports on the NSM SaaS Details screen showed traffic totals that were lower than expected. |
|
NSM-37290 |
Bandwidth management parameters under access rules displayed incorrect values when mixed units were configured. |
|
NSM-38177 |
Editing a VPN Topology gateway address object group containing 36 or more objects appeared to save successfully but failed to persist the change. |
|
NSM-38676 |
Scheduled daily reports failed with a No Report data found error despite the relevant data being available in NSM. |
|
NSM-38678 |
Devices became unselectable when creating a backup schedule after deselecting the Show only online devices option. |
|
NSM-38715 |
The NSM Migration App did not list SOHO 250 as a supported source model when migrating to TZ80. |
|
NSM-38755 |
Selecting a tenant from CSC for MPSS users redirected to the All Tenants view in NSM instead of the selected tenant. |
|
NSM-38764 |
Inventory Grid column settings reverted to the default configuration after every NSM SaaS upgrade. |
|
NSM-38776 |
Editing an IPsec VPN tunnel's secondary gateway address on the Firewall View in NSM On-Prem caused the primary gateway address to be overwritten with the secondary gateway address. |
|
NSM-38968 |
Scheduled report PDFs displayed the report graph timeline in UTC instead of the configured local time zone. |
|
NSM-39116 |
Some users could not access NSM from cloud.sonicwall.com or platform.sonicwall.com; the management app remained on the loading screen indefinitely. |
|
NSM-39154 |
Timeline data within PDF report sections did not match the selected date range of the report. |
|
NSM-39212 |
NSM SaaS reporting stopped working for some firewalls after a SonicOS Gen6 hotfix was applied, even after reconfiguring Reporting and Analytics. |
Known Issues
|
Issue ID |
Description |
|---|---|
|
NSM-33874 |
CTA reports generated from NSM may show incomplete or mislabeled application category data. |
|
NSM-34245 |
Live Monitor and report data in NSM may appear inconsistent when compared with the firewall real-time viewer for the same time period. |
|
NSM-38770 |
Firewall reports may continue to show missing data on some dates despite a valid Advanced Reporting and Analytics license. |
|
NSM-38936 |
Importing LDAP users through NSM may display the full name instead of the logon name, unlike importing directly on the firewall. |
|
NSM-39018 |
VPN Activity > Users reports may fail to load when filtering for a date range of 30 days or more. |
|
NSM-39239 |
Editing user permissions under Tenants & Devices may show no available devices, even when devices are assigned to the user. |
|
NSM-39338 |
Importing an LDAP group may fail to commit with the error "ldap-location" is not a reasonable value. |
Additional References
NSM-34285, NSM-36876, NSM-37050, NSM-37056, NSM-37658, NSM-38055, NSM-38680, NSM-38681, NSM-38690, NSM-38748, NSM-38763, NSM-38952
