• NSM Closed Network 2.2
• Overview
  • About Network Security Manager
  • Closed Network Description
  • Conventions
    • Guide Conventions
    • UI Conventions
  • Related Documents
• System Requirements
  • Browser Levels
  • Minimum System Configuration
  • MySonicWall
  • Firewall Types and Firmware
• Deploying NSM
• NSM Licensing
  • MSW Configuration
  • Enabling Closed Network
  • Associating the Nodes
  • Generating the Encrypted Files
• Getting Started with the Closed Network NSM
  • Configuring Closed Network NSM
  • Adding Firewalls
• SonicWall Support
  • About This Document

Closed Network Description

Network administrators can use NSM in a management console role in an enterprise network containing SonicWall NSA, TZ, or SuperMassive appliances, and Email Security (ES) appliances.

On-premises NSM has been updated to work in a closed environment or closed network . In this scenario, NSM works with no direct access to back-end services. Typically, NSM automatically pulls all necessary files such as license key sets and signature files from the back-end server and pushes them to the firewalls. In a closed network case, NSM cannot reach the back-end servers so cannot access the key sets and signature files.

To maintain the closed environment, back-end files need to be manually delivered to the NSM system. MySonicWall first encrypts a package with all the necessary files. Then the encrypted package needs to be transferred to the NSM local file system so NSM can access the file.

Unencrypted files are encrypted before making it a part of the compressed file.